[Touch-packages] [Bug 1860199] [NEW] OpenCL programs give error messages

2020-01-17 Thread Timothy Krause
Public bug reported:

OpenCL programs print

ac_rtld error: !s->is_rx
LLVM failed to upload shader

when calling clEnqueueNDRangeKernel.

lsb_release -rd displays:

Description:Ubuntu 19.10
Release:19.10

apt-cache policy mesa-opencl-icd displays:

mesa-opencl-icd:
  Installed: 19.2.1-1ubuntu1
  Candidate: 19.2.1-1ubuntu1
  Version table:
 *** 19.2.1-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: mesa-opencl-icd 19.2.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperVersion: 1.427
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 17 23:09:17 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev e1) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:82fe]
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP Pavilion Desktop PC 570-p0xx
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed 
quiet splash ---
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2017
dmi.bios.vendor: AMI
dmi.bios.version: F.20
dmi.board.asset.tag: CNV7500FYH
dmi.board.name: 82FE
dmi.board.vendor: HP
dmi.board.version: 11
dmi.chassis.asset.tag: CNV7500FYH
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.20:bd10/30/2017:svnHP:pnHPPavilionDesktopPC570-p0xx:pvr:rvnHP:rn82FE:rvr11:cvnHP:ct3:cvr:
dmi.product.family: 103C_53311M HP Pavilion
dmi.product.name: HP Pavilion Desktop PC 570-p0xx
dmi.product.sku: Z5P18AA#ABL
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu

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

Title:
  OpenCL programs give error messages

Status in mesa package in Ubuntu:
  New

Bug description:
  OpenCL programs print

  ac_rtld error: !s->is_rx
  LLVM failed to upload shader

  when calling clEnqueueNDRangeKernel.

  lsb_release -rd displays:

  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy mesa-opencl-icd displays:

  mesa-opencl-icd:
Installed: 19.2.1-1ubuntu1
Candidate: 19.2.1-1ubuntu1
Version table:
   *** 19.2.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mesa-opencl-icd 19.2.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 17 23:09:17 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev e1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:82fe]
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Pavilion Desktop PC 570-p0xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed quiet splash ---
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: CNV7500FYH
  dmi.board.name: 82FE
  dmi.board

[Touch-packages] [Bug 1852885] Re: x11-common is dead

2020-01-17 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  x11-common is dead

Status in xorg package in Ubuntu:
  Expired

Bug description:
  x11-common is dead 
  i cant use xorg or default server.
  just work wayland only.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: x11-common 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 17 10:59:36 2019
  Dependencies: lsb-base 11.0.1ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
  InstallationDate: Installed on 2019-01-22 (298 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122)
  MachineType: LENOVO 20KH007UVA
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH007UVA
  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:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KH007UVA
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909260954.031752~oibaf~d
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909260954.031752~oibaf~d
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/1852885/+subscriptions

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


[Touch-packages] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)

2020-01-17 Thread Chad Smith
** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => New

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

Title:
  Please add ${distro_id}ESM:${distro_codename}-infra-security  and
  ${distro_id}ESMApps:${distro_codename}-apps-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Trusty:
  New
Status in unattended-upgrades source package in Xenial:
  New
Status in unattended-upgrades source package in Bionic:
  New

Bug description:
  ESM -infra-security and -apps-security will need to
  participate in unattended upgrades.

  Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}ESM:${distro_codename}";
  }

  Given that there have been ESM apt pocket renames over the last few
  months, the above ESM allowed-origin should not apply anymore and can
  be dropped or replaced.

  See RT #C122697 and #C121067 for the pocket/suite renames related to
  ESM

  What is needed after the ESM apt pocket/suite renames:

  Support for unattended upgrades for ESM for Infrastructure customers:

  Unattended-Upgrade::Allowed-Origins {
    // Extended Security Maintenance; doesn't necessarily exist for
    // every release and this system may not have it installed, but if
    // available, the policy for updates is such that unattended-upgrades
    // should also install from here by default.
    "${distro_id}ESM:${distro_codename}-infra-security";
    "${distro_id}ESMApps:${distro_codename}-apps-security";
  };

  === Confirmed proper origin on an attached Trusty instance with ESM-
  infra enabled:

   500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
   release 
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main

  === Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on 
an AWS Ubuntu PRO instance:
   500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64

   500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+subscriptions

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


[Touch-packages] [Bug 1858152] Re: fstrim.service no longer trims /home partition

2020-01-17 Thread Matt Vickers
I can confirm this bug. Viewing systemd logs on my system showed the
weekly TRIM of /home stopped around the end of October 2019 as reported
by Jeffery.

This bug was filed upstream (https://github.com/karelzak/util-
linux/issues/824) and will affect users with /home on a separate
partition.

It was patched with the following one-line commit 
c64d452b3eb85fe55e238144082247b05cc143ea:
-ProtectHome=yes
+ProtectHome=read-only


** Bug watch added: github.com/karelzak/util-linux/issues #824
   https://github.com/karelzak/util-linux/issues/824

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

Title:
  fstrim.service no longer trims /home partition

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  When I was running disco, fstrim.service would trim all of my
  partitions:

  Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) 
trimmed on /dev/mapper/ubuntu--vg-home
  Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) 
trimmed on /dev/sda5
  Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed 
on /dev/mapper/ubuntu--vg-root
  Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded.
  Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on 
filesystems from /etc/fstab.

  After upgrading to eoan, my /home partition is no longer trimmed:

  Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) 
trimmed on /dev/sda5
  Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed 
on /dev/mapper/ubuntu--vg-root
  Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded.
  Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on 
filesystems from /etc/fstab.

  Checking the unit file (/lib/systemd/system/fstrim.service), I noticed
  there is a "ProtectHome=yes" option. Removing this option caused my
  /home partition to be trimmed once again.

  I believe the "ProtectSystem=strict" option may also cause partitions
  in non-standard partition schemes to be skipped by fstrim.service
  (although I have not tested this).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858152/+subscriptions

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


[Touch-packages] [Bug 1858152] Re: fstrim.service no longer trims /home partition

2020-01-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  fstrim.service no longer trims /home partition

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  When I was running disco, fstrim.service would trim all of my
  partitions:

  Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) 
trimmed on /dev/mapper/ubuntu--vg-home
  Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) 
trimmed on /dev/sda5
  Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed 
on /dev/mapper/ubuntu--vg-root
  Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded.
  Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on 
filesystems from /etc/fstab.

  After upgrading to eoan, my /home partition is no longer trimmed:

  Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) 
trimmed on /dev/sda5
  Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed 
on /dev/mapper/ubuntu--vg-root
  Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded.
  Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on 
filesystems from /etc/fstab.

  Checking the unit file (/lib/systemd/system/fstrim.service), I noticed
  there is a "ProtectHome=yes" option. Removing this option caused my
  /home partition to be trimmed once again.

  I believe the "ProtectSystem=strict" option may also cause partitions
  in non-standard partition schemes to be skipped by fstrim.service
  (although I have not tested this).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858152/+subscriptions

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


[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated

2020-01-17 Thread Colin Watson
** Description changed:

- 1024-bit RSA เลิกใช้แล้วเมื่อหลายปีก่อนโดย NIST [1], Microsoft [2]
- และอื่น ๆ เมื่อไม่นานมานี้ [3]
+ 1024-bit RSA was deprecated  years ago by NIST[1], Microsoft[2] and more
+ recently by others[3].
  
- คีย์การลงชื่อ 1024
- บิตไม่เพียงพอที่จะรับประกันความถูกต้องของซอฟต์แวร์ที่แจกจ่ายจาก
- Launchpad.net รวมถึง PPA
- ควรมีกลไกในการปฏิเสธการเซ็นชื่อคีย์ด้านล่างความยาวคีย์ต่ำสุดตามชนิดของคีย์
- คีย์การเซ็นชื่อ 1024 บิตควรเลิกใช้แล้วนำออกจาก Launchpad.net
- โดยเร็วที่สุด โครงการในอนาคตและ PPAs ควรถูกห้ามไม่ให้ใช้คีย์การลงชื่อ
- 1024 บิต
+ 1024-bit signing keys are insufficient to guarantee the authenticity of
+ software distributed from Launchpad.net including PPAs. There should be
+ a mechanism to refuse signing keys below a minimum key length based on
+ key type. 1024-bit signing keys should be deprecated and removed from
+ Launchpad.net itself ASAP.  Future projects and PPAs should be
+ disallowed from using 1024-bit signing keys.
  
  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

** Changed in: launchpad
 Assignee: wachirapranee tesprasit (tatar28) => (unassigned)

** Changed in: apt (Ubuntu)
 Assignee: wachirapranee tesprasit (tatar28) => (unassigned)

** Changed in: gnupg2 (Ubuntu)
 Assignee: wachirapranee tesprasit (tatar28) => (unassigned)

** Changed in: launchpad
   Status: Fix Released => New

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

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

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

Title:
  1024-bit signing keys should be deprecated

Status in Launchpad itself:
  New
Status in apt package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  1024-bit RSA was deprecated  years ago by NIST[1], Microsoft[2] and
  more recently by others[3].

  1024-bit signing keys are insufficient to guarantee the authenticity
  of software distributed from Launchpad.net including PPAs. There
  should be a mechanism to refuse signing keys below a minimum key
  length based on key type. 1024-bit signing keys should be deprecated
  and removed from Launchpad.net itself ASAP.  Future projects and PPAs
  should be disallowed from using 1024-bit signing keys.

  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

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

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


[Touch-packages] [Bug 1859353] Re: software-properties-gtk not working

2020-01-17 Thread Sarpreet
Ran the command :
sudo apt install --reinstall python3-six

It works fine after that.

Thank you

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

Title:
  software-properties-gtk not working

Status in software-properties package in Ubuntu:
  New

Bug description:
  Additional Drivers /Software & Update not working

  Hello,

  I am running :-
  Description: Ubuntu 19.10
  Release: 19.10

  software-properties-gtk:
  Installed: 0.98.5
  Candidate: 0.98.5
  Version table:
  *** 0.98.5 500
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status



  I am trying to run Additional Drivers /Software & Update . But it opened once 
and froze and never opened again.
  When I try running the command:-
  $ sudo software-properties-gtk

  Did a remove and reinstall of the same, but did not work.

  It returns:-

  
  ERROR:dbus.proxies:Introspect error on :1.2559:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 175, in __init__
  self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__
  **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 653, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.2559 was not provided by any .service files

  
  Also, the syslog says:-
  name='com.ubuntu.SoftwareProperties' requested by ':1.2455' (uid=1000 
pid=2267 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " 
label="unconfined") (using servicehelper)
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init 
server: Could not connect: Connection refused
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init 
server: Could not connect: Connection refused
  Jan 12 11:58:55 gillZ dbus-daemon[2192]: [system] Successfully activated 
service 'com.ubuntu.SoftwareProperties'
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Traceback (most 
recent call last):
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/usr/lib/software-properties/software-properties-dbus", line 68, in 
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: server = 
SoftwarePropertiesDBus(bus, datadir=datadir)
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py", 
line 66, in __init__
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: 
self._livepatch_service = LivepatchService()
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 93, 
in __init__
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: self._session = 
requests_unixsocket.Session()
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: NameError: name 
'requests_unixsocket' is not defined
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: 
ERROR:dbus.proxies:Introspect error on :1.2457:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: Traceback 
(most recent call last):
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/bin/software-properties-gtk", line 100, in 
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: app = 
SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file)
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 175, in __init__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: 
self.backend.Reload();
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: return 
self._proxy_method(*args, **keywords)
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: **keywords)
  Jan 12 11:5

[Touch-packages] [Bug 1859353] Re: software-properties-gtk not working

2020-01-17 Thread Sarpreet
After I reinstalled this package, software-properties-gtk worked again.

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

Title:
  software-properties-gtk not working

Status in software-properties package in Ubuntu:
  New

Bug description:
  Additional Drivers /Software & Update not working

  Hello,

  I am running :-
  Description: Ubuntu 19.10
  Release: 19.10

  software-properties-gtk:
  Installed: 0.98.5
  Candidate: 0.98.5
  Version table:
  *** 0.98.5 500
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status



  I am trying to run Additional Drivers /Software & Update . But it opened once 
and froze and never opened again.
  When I try running the command:-
  $ sudo software-properties-gtk

  Did a remove and reinstall of the same, but did not work.

  It returns:-

  
  ERROR:dbus.proxies:Introspect error on :1.2559:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 175, in __init__
  self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__
  **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 653, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.2559 was not provided by any .service files

  
  Also, the syslog says:-
  name='com.ubuntu.SoftwareProperties' requested by ':1.2455' (uid=1000 
pid=2267 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " 
label="unconfined") (using servicehelper)
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init 
server: Could not connect: Connection refused
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init 
server: Could not connect: Connection refused
  Jan 12 11:58:55 gillZ dbus-daemon[2192]: [system] Successfully activated 
service 'com.ubuntu.SoftwareProperties'
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Traceback (most 
recent call last):
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/usr/lib/software-properties/software-properties-dbus", line 68, in 
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: server = 
SoftwarePropertiesDBus(bus, datadir=datadir)
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py", 
line 66, in __init__
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: 
self._livepatch_service = LivepatchService()
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 93, 
in __init__
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: self._session = 
requests_unixsocket.Session()
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: NameError: name 
'requests_unixsocket' is not defined
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: 
ERROR:dbus.proxies:Introspect error on :1.2457:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: Traceback 
(most recent call last):
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/bin/software-properties-gtk", line 100, in 
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: app = 
SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file)
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 175, in __init__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: 
self.backend.Reload();
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: return 
self._proxy_method(*args, **keywords)
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: **keywords)
  Jan 12 11:58:55 gillZ software-prope

[Touch-packages] [Bug 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version

2020-01-17 Thread Dave Jones
> Do you have the new python3.7 installed from focal-proposed?

> note, i was running everything from proposed. Since libffi6 & 7 might
> be used by python3.7.

Ah, no I didn't. However, doesn't seem like it makes much difference:

ubuntu@ubuntu:~$ sudo apt install -t focal-proposed python3.7
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libpython3.7 libpython3.7-dbg libpython3.7-minimal libpython3.7-stdlib 
python3.7-dbg python3.7-minimal
Suggested packages:
  python3.7-venv python3.7-doc python3-gdbm-dbg python3-tk-dbg binfmt-support
The following packages will be upgraded:
  libpython3.7 libpython3.7-dbg libpython3.7-minimal libpython3.7-stdlib 
python3.7 python3.7-dbg
  python3.7-minimal
7 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
Need to get 32.9 MB of archives.
After this operation, 26.6 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
python3.7-dbg arm64 3.7.6-1ubuntu2 [15.9 MB]
Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 python3.7 
arm64 3.7.6-1ubuntu2 [304 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
libpython3.7 arm64 3.7.6-1ubuntu2 [1373 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
libpython3.7-dbg arm64 3.7.6-1ubuntu2 [11.4 MB]
Get:5 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
libpython3.7-stdlib arm64 3.7.6-1ubuntu2 [1717 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
python3.7-minimal arm64 3.7.6-1ubuntu2 [1723 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
libpython3.7-minimal arm64 3.7.6-1ubuntu2 [547 kB]
Fetched 32.9 MB in 25s (1316 kB/s)
(Reading database ... 80531 files and directories currently installed.)
Preparing to unpack .../0-python3.7-dbg_3.7.6-1ubuntu2_arm64.deb ...
Unpacking python3.7-dbg (3.7.6-1ubuntu2) over (3.7.6-1) ...
Preparing to unpack .../1-python3.7_3.7.6-1ubuntu2_arm64.deb ...
Unpacking python3.7 (3.7.6-1ubuntu2) over (3.7.6-1) ...
Preparing to unpack .../2-libpython3.7_3.7.6-1ubuntu2_arm64.deb ...
Unpacking libpython3.7:arm64 (3.7.6-1ubuntu2) over (3.7.6-1) ...
Preparing to unpack .../3-libpython3.7-dbg_3.7.6-1ubuntu2_arm64.deb ...
Unpacking libpython3.7-dbg:arm64 (3.7.6-1ubuntu2) over (3.7.6-1) ...
Preparing to unpack .../4-libpython3.7-stdlib_3.7.6-1ubuntu2_arm64.deb ...
Unpacking libpython3.7-stdlib:arm64 (3.7.6-1ubuntu2) over (3.7.6-1) ...
Preparing to unpack .../5-python3.7-minimal_3.7.6-1ubuntu2_arm64.deb ...
Unpacking python3.7-minimal (3.7.6-1ubuntu2) over (3.7.6-1) ...
Preparing to unpack .../6-libpython3.7-minimal_3.7.6-1ubuntu2_arm64.deb ...
Unpacking libpython3.7-minimal:arm64 (3.7.6-1ubuntu2) over (3.7.6-1) ...
Setting up libpython3.7-minimal:arm64 (3.7.6-1ubuntu2) ...
Setting up python3.7-minimal (3.7.6-1ubuntu2) ...
Setting up libpython3.7-stdlib:arm64 (3.7.6-1ubuntu2) ...
Setting up libpython3.7:arm64 (3.7.6-1ubuntu2) ...
Setting up libpython3.7-dbg:arm64 (3.7.6-1ubuntu2) ...
Setting up python3.7 (3.7.6-1ubuntu2) ...
Setting up python3.7-dbg (3.7.6-1ubuntu2) ...
Processing triggers for libc-bin (2.30-0ubuntu3) ...
Processing triggers for man-db (2.9.0-2) ...
Processing triggers for mime-support (3.64ubuntu1) ...
ubuntu@ubuntu:~$ python3 -c "import goocalendar; print(goocalendar.__version__)"
Segmentation fault (core dumped)

I'll keep the SD card around for a few days if you want me to dig into
this any further.

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

Title:
  python-gi/arm64 segfaults with the focal-proposed libffi version

Status in libffi package in Ubuntu:
  Incomplete
Status in libffi source package in Focal:
  Incomplete

Bug description:
  Testcase, on focal/arm64

  $ sudo apt install python3-goocalendar
  $ python3 -c "import goocalendar ; print(goocalendar.__version__)"

  -> works fine

  install the python3-gi package from focal-proposed it segfaults in
  libffi

  Program received signal SIGSEGV, Segmentation fault.
  0x in ?? ()
  (gdb) bt
  #0  0x in ?? ()
  #1  0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114
  #2  0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, 
  orig_rvalue=, avalue=0x0, closure=)

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

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


[Touch-packages] [Bug 1856574] Re: removal of various autopilot packages

2020-01-17 Thread Matthias Klose
still build-depends on python-evdev and python-gi, which are going to be
removed.


** Changed in: autopilot-gtk (Ubuntu)
   Importance: Medium => High

** Changed in: autopilot-gtk (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: autopilot-gtk (Ubuntu)
 Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)

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

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Triaged
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  Fix Released
Status in python-testtools package in Ubuntu:
  Fix Released

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions

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


[Touch-packages] [Bug 1860178] [NEW] Graphic environment bug

2020-01-17 Thread alain
Public bug reported:

Graphic environment unstable, desktop background degraded. Seems
consequently to last system upgrade (2020.jan.17)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CompositorRunning: None
Date: Fri Jan 17 21:55:59 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
InstallationDate: Installed on 2019-08-03 (167 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard 
reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: eMachines EL1358
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-B1
dmi.board.name: EL1358
dmi.board.vendor: eMachines
dmi.chassis.type: 3
dmi.chassis.vendor: eMachines
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
dmi.product.family: eMachines Desktop
dmi.product.name: EL1358
dmi.product.sku: To Be Filled By O.E.M.
dmi.sys.vendor: eMachines
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1860178

Title:
  Graphic environment bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Graphic environment unstable, desktop background degraded. Seems
  consequently to last system upgrade (2020.jan.17)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Jan 17 21:55:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
  InstallationDate: Installed on 2019-08-03 (167 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 
multicard reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser 
Printer
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: eMachines EL1358
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.name: EL1358
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
  dmi.product.family: eMachines Desktop
  dmi.product.name: EL1358
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: eMachines
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1

[Touch-packages] [Bug 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

2020-01-17 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.34-0.1ubuntu5

---
util-linux (2.34-0.1ubuntu5) focal; urgency=medium

  * d/p/libblkid-xfs-log-check-for-reg-xfs-on-more-sectors.patch:
fix ambivalent detection of bcache and xfs_external_log
due to regular xfs on bcache backing device. (LP: #1858802)

 -- Mauricio Faria de Oliveira   Wed, 08 Jan 2020
16:03:19 -0300

** Changed in: util-linux (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Disco:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+subscriptions

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


Re: [Touch-packages] [Bug 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version

2020-01-17 Thread Dimitri John Ledkov
On Fri, 17 Jan 2020 at 16:15, Dave Jones  wrote:
>
> Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
> python3-gi-cairo arm64 3.34.0-3build2 [8336 B]
> Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libffi7 
> arm64 3.3-2.3build1 [17.1 kB]
> Get:3 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
> python3-gi arm64 3.34.0-3build2 [195 kB]
> Fetched 220 kB in 2s (114 kB/s)

Do you have the new python3.7 installed from focal-proposed?

note, i was running everything from proposed. Since libffi6 & 7 might
be used by python3.7.

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

Title:
  python-gi/arm64 segfaults with the focal-proposed libffi version

Status in libffi package in Ubuntu:
  Incomplete
Status in libffi source package in Focal:
  Incomplete

Bug description:
  Testcase, on focal/arm64

  $ sudo apt install python3-goocalendar
  $ python3 -c "import goocalendar ; print(goocalendar.__version__)"

  -> works fine

  install the python3-gi package from focal-proposed it segfaults in
  libffi

  Program received signal SIGSEGV, Segmentation fault.
  0x in ?? ()
  (gdb) bt
  #0  0x in ?? ()
  #1  0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114
  #2  0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, 
  orig_rvalue=, avalue=0x0, closure=)

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

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


[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated

2020-01-17 Thread wachirapranee tesprasit
** Changed in: apt (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: launchpad
   Status: New => Confirmed

** Changed in: launchpad
 Assignee: (unassigned) => wachirapranee tesprasit (tatar28)

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => wachirapranee tesprasit (tatar28)

** Changed in: gnupg2 (Ubuntu)
 Assignee: (unassigned) => wachirapranee tesprasit (tatar28)

** Changed in: launchpad
   Status: Confirmed => Fix Released

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

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

** Description changed:

- 1024-bit RSA was deprecated  years ago by NIST[1], Microsoft[2] and more
- recently by others[3].
+ 1024-bit RSA เลิกใช้แล้วเมื่อหลายปีก่อนโดย NIST [1], Microsoft [2]
+ และอื่น ๆ เมื่อไม่นานมานี้ [3]
  
- 1024-bit signing keys are insufficient to guarantee the authenticity of
- software distributed from Launchpad.net including PPAs. There should be
- a mechanism to refuse signing keys below a minimum key length based on
- key type. 1024-bit signing keys should be deprecated and removed from
- Launchpad.net itself ASAP.  Future projects and PPAs should be
- disallowed from using 1024-bit signing keys.
+ คีย์การลงชื่อ 1024
+ บิตไม่เพียงพอที่จะรับประกันความถูกต้องของซอฟต์แวร์ที่แจกจ่ายจาก
+ Launchpad.net รวมถึง PPA
+ ควรมีกลไกในการปฏิเสธการเซ็นชื่อคีย์ด้านล่างความยาวคีย์ต่ำสุดตามชนิดของคีย์
+ คีย์การเซ็นชื่อ 1024 บิตควรเลิกใช้แล้วนำออกจาก Launchpad.net
+ โดยเร็วที่สุด โครงการในอนาคตและ PPAs ควรถูกห้ามไม่ให้ใช้คีย์การลงชื่อ
+ 1024 บิต
  
  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

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

Title:
  1024-bit signing keys should be deprecated

Status in Launchpad itself:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in gnupg2 package in Ubuntu:
  Fix Released

Bug description:
  1024-bit RSA เลิกใช้แล้วเมื่อหลายปีก่อนโดย NIST [1], Microsoft [2]
  และอื่น ๆ เมื่อไม่นานมานี้ [3]

  คีย์การลงชื่อ 1024
  บิตไม่เพียงพอที่จะรับประกันความถูกต้องของซอฟต์แวร์ที่แจกจ่ายจาก
  Launchpad.net รวมถึง PPA
  ควรมีกลไกในการปฏิเสธการเซ็นชื่อคีย์ด้านล่างความยาวคีย์ต่ำสุดตามชนิดของคีย์
  คีย์การเซ็นชื่อ 1024 บิตควรเลิกใช้แล้วนำออกจาก Launchpad.net
  โดยเร็วที่สุด โครงการในอนาคตและ PPAs ควรถูกห้ามไม่ให้ใช้คีย์การลงชื่อ
  1024 บิต

  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

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

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


[Touch-packages] [Bug 1859857] Re: network-manager keeps asking for wifi password can't connect to any wifi

2020-01-17 Thread Michael Moessner
After searching around I found the bug report #1849891 which suggested
to remove backport-iwlwifi-dkms, which I just tried. After rebooting my
wifi is working again.

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

Title:
  network-manager keeps asking for wifi password can't connect to any
  wifi

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  This bug is the same as reported by #1859289, however I was not able
  to find this when using the ubuntu-bug tool.

  Since the last update my network-manager keeps asking me for wifi
  passworts, but then never connects. Password is definitely correct.
  Everything worked before the update.

  lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Jan 15 19:12:42 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-05-27 (233 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000 
   192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.23 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (83 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1859857/+subscriptions

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


[Touch-packages] [Bug 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version

2020-01-17 Thread Dave Jones
Reproduced on a Pi4 running the current focal daily:

ubuntu@ubuntu:~$ python3 -c "import goocalendar; 
print(goocalendar.__version__)" 
  
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
0.5
ubuntu@ubuntu:~$ sudo apt install -t focal-proposed python3-gi
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libffi7 python3-gi-cairo
The following NEW packages will be installed:
  libffi7
The following packages will be upgraded:
  python3-gi python3-gi-cairo
2 upgraded, 1 newly installed, 0 to remove and 85 not upgraded.
Need to get 220 kB of archives.
After this operation, 60.4 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
python3-gi-cairo arm64 3.34.0-3build2 [8336 B]
Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libffi7 
arm64 3.3-2.3build1 [17.1 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 python3-gi 
arm64 3.34.0-3build2 [195 kB]
Fetched 220 kB in 2s (114 kB/s)  
(Reading database ... 79794 files and directories currently installed.)
Preparing to unpack .../python3-gi-cairo_3.34.0-3build2_arm64.deb ...
Unpacking python3-gi-cairo (3.34.0-3build2) over (3.34.0-3) ...
Selecting previously unselected package libffi7:arm64.
Preparing to unpack .../libffi7_3.3-2.3build1_arm64.deb ...
Unpacking libffi7:arm64 (3.3-2.3build1) ...
Preparing to unpack .../python3-gi_3.34.0-3build2_arm64.deb ...
Unpacking python3-gi (3.34.0-3build2) over (3.34.0-3) ...
Setting up libffi7:arm64 (3.3-2.3build1) ...
Setting up python3-gi (3.34.0-3build2) ...
Setting up python3-gi-cairo (3.34.0-3build2) ...
Processing triggers for libc-bin (2.30-0ubuntu3) ...
ubuntu@ubuntu:~$ python3 -c "import goocalendar; print(goocalendar.__version__)"
Segmentation fault (core dumped)

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

Title:
  python-gi/arm64 segfaults with the focal-proposed libffi version

Status in libffi package in Ubuntu:
  Incomplete
Status in libffi source package in Focal:
  Incomplete

Bug description:
  Testcase, on focal/arm64

  $ sudo apt install python3-goocalendar
  $ python3 -c "import goocalendar ; print(goocalendar.__version__)"

  -> works fine

  install the python3-gi package from focal-proposed it segfaults in
  libffi

  Program received signal SIGSEGV, Segmentation fault.
  0x in ?? ()
  (gdb) bt
  #0  0x in ?? ()
  #1  0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114
  #2  0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, 
  orig_rvalue=, avalue=0x0, closure=)

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

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


[Touch-packages] [Bug 1860133] Re: Memory leak on set_default_locale

2020-01-17 Thread Laurent Stacul
This has been reported in the past to the maintainer.

https://lists.gnu.org/archive/html/bug-bash/2015-07/msg00073.html
https://lists.gnu.org/archive/html/bug-bash/2017-04/msg00063.html
https://lists.gnu.org/archive/html/bug-bash/2017-06/msg00052.html

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

Title:
  Memory leak on set_default_locale

Status in bash package in Ubuntu:
  New

Bug description:
  Hello,

  I heavily use ubuntu as a build platform to build and package C/C++ 
components.
  Some components are checked in a valgrind environment. On some of them, I am
  reported with the described memory leak due to bash.

  It seems this bug has been fixed in other distros but not in Debian nor 
Ubuntu.
  There is an old bug from bash 4.3 which can be reproduce easily that way:

  ```
  $ valgrind --leak-check=full /bin/bash -c 'exit 0'
  ...
  ==565== 2 bytes in 1 blocks are definitely lost in loss record 14 of 269
  ==565==at 0x483577F: malloc (vg_replace_malloc.c:299)
  ==565==by 0x195E8D: xmalloc (in /bin/bash)
  ==565==by 0x18F51A: set_default_locale (in /bin/bash)
  ==565==by 0x135EE6: main (in /bin/bash)
  ...
  ```

  This has been fixed in fedora that way (and the patch is still here in the
  latest RPMs):

  ```
  >cat bash-4.3-memleak-lc_all.patch
  diff -up bash-4.3/locale.c.old bash-4.3/locale.c
  --- bash-4.3/locale.c.old   2015-07-15 11:55:00.002857301 +0200
  +++ bash-4.3/locale.c   2015-07-15 11:48:36.698086257 +0200
  @@ -77,8 +77,6 @@ set_default_locale ()
   {
   #if defined (HAVE_SETLOCALE)
 default_locale = setlocale (LC_ALL, "");
  -  if (default_locale)
  -default_locale = savestring (default_locale);
   #endif /* HAVE_SETLOCALE */
 bindtextdomain (PACKAGE, LOCALEDIR);
 textdomain (PACKAGE);
  ```

  Do you think it is worth integrating that kind of patch in your package ?
  Regards,
  Stac

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

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


[Touch-packages] [Bug 1860143] Re: /usr/bin/software-properties-gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin/software-properties-gtk@101:run

2020-01-17 Thread Olivier Tilloy
** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin
  /software-properties-gtk@101:run

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.6, the problem page at 
https://errors.ubuntu.com/problem/7f35e34c316c48e756a0d4a38dd302dbcd8ebfae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860143/+subscriptions

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


[Touch-packages] [Bug 1860143] Re: /usr/bin/software-properties-gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin/software-properties-gtk@101:run

2020-01-17 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~osomon/software-properties/+git/software-properties/+merge/30

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin
  /software-properties-gtk@101:run

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.6, the problem page at 
https://errors.ubuntu.com/problem/7f35e34c316c48e756a0d4a38dd302dbcd8ebfae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860143/+subscriptions

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


[Touch-packages] [Bug 1860143] Re: /usr/bin/software-properties-gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin/software-properties-gtk@101:run

2020-01-17 Thread Olivier Tilloy
** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin
  /software-properties-gtk@101:run

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.6, the problem page at 
https://errors.ubuntu.com/problem/7f35e34c316c48e756a0d4a38dd302dbcd8ebfae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860143/+subscriptions

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


[Touch-packages] [Bug 1860143] Re: /usr/bin/software-properties-gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin/software-properties-gtk@101:run

2020-01-17 Thread Olivier Tilloy
In disco and focal, I can reliably reproduce by running software-
properties-gtk in a terminal, then focusing back the terminal window and
pressing Ctrl+C to interrupt the program.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin
  /software-properties-gtk@101:run

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.6, the problem page at 
https://errors.ubuntu.com/problem/7f35e34c316c48e756a0d4a38dd302dbcd8ebfae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860143/+subscriptions

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


[Touch-packages] [Bug 1860143] [NEW] /usr/bin/software-properties-gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin/software-properties-gtk@101:run

2020-01-17 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.6, the problem page at 
https://errors.ubuntu.com/problem/7f35e34c316c48e756a0d4a38dd302dbcd8ebfae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress


** Tags: 19.04-19.04 19.04-2019.4 bionic cosmic disco eoan focal

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin
  /software-properties-gtk@101:run

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.6, the problem page at 
https://errors.ubuntu.com/problem/7f35e34c316c48e756a0d4a38dd302dbcd8ebfae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860143/+subscriptions

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


[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2020-01-17 Thread Dariusz Gadomski
SRU proposal for eoan.

** Patch added: "eoan_systemd_242-7ubuntu3.3.debdiff"
   
https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5321139/+files/eoan_systemd_242-7ubuntu3.3.debdiff

** Description changed:

  [Impact]
  
- pam_setcred call was missing in systemd making it's implementation of the PAM 
protocol problematic. It could manifest in different ways, but one particularly 
problematic for enterprise environments was the fact that
+ pam_setcred call was missing in systemd making its implementation of the PAM 
protocol incomplete. It could manifest in different ways, but one particularly 
problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via 
pam_group module.
  
  [Test Case]
  
-  * Add a /etc/security/group.conf entry, e.g.
-*;*;*;Al-2400;dialout,users
-  * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
-  * Login to the system and launch gnome-terminal (it will be launched via 
gnome-terminal-server launched by systemd --user + dbus).
+  * Add a /etc/security/group.conf entry, e.g.
+    *;*;*;Al-2400;dialout,users
+  * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
+  * Login to the system and launch gnome-terminal (it will be launched via 
gnome-terminal-server launched by systemd --user + dbus).
  
  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.
  
  Actual result:
  no group membership gained from pam_group.
  
  [Regression Potential]
  
-  * It introduces a new PAM warning message in some scenarios (e.g. for
+  * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).
  
-  * In certain systems user group membership may be extended by
+  * In certain systems user group membership may be extended by
  pam_group.
  
  [Other Info]
  Original bug description:
  
  We are using Ubuntu in a university network with lots of ldap users. To
  automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.
  
  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user. Xterm,
  ssh, su, and tty* however do work as expected. Only the default gnome-
  terminal behaves different.
  
  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this might
  not be a bug, but a feature.
  
  Nevertheless this behavior is very unexpected when upgrading from Xenial
  to Bionic and therefore should at least added to the changelog.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM 
protocol incomplete. It could manifest in different ways, but one particularly 
problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via 
pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via 
gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2020-01-17 Thread Dariusz Gadomski
SRU proposal for bionic.

** Patch added: "bionic_systemd_237-3ubuntu10.34.debdiff"
   
https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5321138/+files/bionic_systemd_237-3ubuntu10.34.debdiff

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM 
protocol incomplete. It could manifest in different ways, but one particularly 
problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via 
pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via 
gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1860133] Re: Memory leak on set_default_locale

2020-01-17 Thread Laurent Stacul
Bug reported upstream too.

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

Title:
  Memory leak on set_default_locale

Status in bash package in Ubuntu:
  New

Bug description:
  Hello,

  I heavily use ubuntu as a build platform to build and package C/C++ 
components.
  Some components are checked in a valgrind environment. On some of them, I am
  reported with the described memory leak due to bash.

  It seems this bug has been fixed in other distros but not in Debian nor 
Ubuntu.
  There is an old bug from bash 4.3 which can be reproduce easily that way:

  ```
  $ valgrind --leak-check=full /bin/bash -c 'exit 0'
  ...
  ==565== 2 bytes in 1 blocks are definitely lost in loss record 14 of 269
  ==565==at 0x483577F: malloc (vg_replace_malloc.c:299)
  ==565==by 0x195E8D: xmalloc (in /bin/bash)
  ==565==by 0x18F51A: set_default_locale (in /bin/bash)
  ==565==by 0x135EE6: main (in /bin/bash)
  ...
  ```

  This has been fixed in fedora that way (and the patch is still here in the
  latest RPMs):

  ```
  >cat bash-4.3-memleak-lc_all.patch
  diff -up bash-4.3/locale.c.old bash-4.3/locale.c
  --- bash-4.3/locale.c.old   2015-07-15 11:55:00.002857301 +0200
  +++ bash-4.3/locale.c   2015-07-15 11:48:36.698086257 +0200
  @@ -77,8 +77,6 @@ set_default_locale ()
   {
   #if defined (HAVE_SETLOCALE)
 default_locale = setlocale (LC_ALL, "");
  -  if (default_locale)
  -default_locale = savestring (default_locale);
   #endif /* HAVE_SETLOCALE */
 bindtextdomain (PACKAGE, LOCALEDIR);
 textdomain (PACKAGE);
  ```

  Do you think it is worth integrating that kind of patch in your package ?
  Regards,
  Stac

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

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


[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2020-01-17 Thread Dariusz Gadomski
** Description changed:

+ [Impact]
+ 
+ pam_setcred call was missing in systemd making it's implementation of the PAM 
protocol problematic. It could manifest in different ways, but one particularly 
problematic for enterprise environments was the fact that
+ processes were never getting group membership they were expected to get via 
pam_group module.
+ 
+ [Test Case]
+ 
+  * Add a /etc/security/group.conf entry, e.g.
+*;*;*;Al-2400;dialout,users
+  * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
+  * Login to the system and launch gnome-terminal (it will be launched via 
gnome-terminal-server launched by systemd --user + dbus).
+ 
+ Expected result:
+ Logged in user is a member of 'dialout' and 'users' groups.
+ 
+ Actual result:
+ no group membership gained from pam_group.
+ 
+ [Regression Potential]
+ 
+  * It introduces a new PAM warning message in some scenarios (e.g. for
+ systemd DynamicUser=1 units) for users that can't authenticate
+ (pam_setcred fails in such case).
+ 
+  * In certain systems user group membership may be extended by
+ pam_group.
+ 
+ [Other Info]
+ Original bug description:
+ 
  We are using Ubuntu in a university network with lots of ldap users. To
  automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.
  
  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user. Xterm,
  ssh, su, and tty* however do work as expected. Only the default gnome-
  terminal behaves different.
  
  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this might
  not be a bug, but a feature.
  
  Nevertheless this behavior is very unexpected when upgrading from Xenial
  to Bionic and therefore should at least added to the changelog.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making it's implementation of the PAM 
protocol problematic. It could manifest in different ways, but one particularly 
problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via 
pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
 *;*;*;Al-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via 
gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelea

[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2020-01-17 Thread Dan Streetman
** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
 Assignee: Dariusz Gadomski (dgadomski)
   Status: In Progress

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

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

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

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module

2020-01-17 Thread Dan Streetman
** Description changed:

  [impact]
  
  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module is included in the new 'linux-modules-extra-*' deb
  which isn't installed by default, so the test always fails when doing a
  reverse-dep autopkgtest using such a kernel's meta pkg.
+ 
+ Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
+ disabled entirely; for those kernels, it will never be possible to load
+ the scsi_debug module and the test should be skipped.
  
  [test case]
  
  run the 'storage' autopkgtest with a custom kernel that doesn't provide
  the scsi_debug module in the standard linux-modules deb, or check the
  autopkgtest.u.c history, for example:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
  
  [regression potential]
  
  as this modifies one of the autopkgtest --setup-commands, and assumes
  that all custom 'linux-meta-FLAVOR' kernels have a corresponding 'linux-
  modules-extra-FLAVOR' deb (or will match the alternate 'linux-image-
  generic-FLAVOR' naming), a regression would most likely cause immediate
  test failure due to failing to install the proper linux-* debs.
+ 
+ For the systemd 'storage' test change, this only skips the test if the
+ scsi_debug module can't be loaded (and isn't already present, i.e.
+ loaded or built-in).  Any regression potential from that is low, but
+ likely would involve incorrect test skips and/or missing valid problems
+ due to skipping the test.

** Changed in: systemd (Ubuntu Focal)
   Status: Invalid => In Progress

** Changed in: systemd (Ubuntu Disco)
   Status: Invalid => Won't Fix

** Changed in: systemd (Ubuntu Eoan)
   Status: Invalid => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Status: Invalid => In Progress

** Changed in: systemd (Ubuntu Xenial)
   Status: Invalid => In Progress

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Disco)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
  that don't include scsi_debug module

Status in autopkgtest-cloud:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module is included in the new 'linux-modules-extra-*'
  deb which isn't installed by default, so the test always fails when
  doing a reverse-dep autopkgtest using such a kernel's meta pkg.

  Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
  disabled entirely; for those kernels, it will never be possible to
  load the scsi_debug module and the test should be skipped.

  [test case]

  run the 'storage' autopkgtest with a custom kernel that doesn't
  provide the scsi_debug module in the standard linux-modules deb, or
  check the autopkgtest.u.c history, for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz

  [regression potential]

  as this modifies one of the autopkgtest --setup-commands, and assumes
  that all custom 'linux-meta-FLAVOR' kernels have a corresponding
  'linux-modules-extra-FLAVOR' deb (or will match the alternate 'linux-
  image-generic-FLAVOR' naming), a regression would most likely cause
  immediate test failure due to failing to install the proper linux-*
  debs.

  For the systemd 'storage' test change, this only skips the test if the
  scsi_debug module can't be loaded (and isn't already present, i.e.
  loaded or built-in).  Any regression potential from that is low, but
  likely would involve incorrect test skips and/or missing valid
  problems due to skipping the test.

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

-- 
Mailing list: https:

[Touch-packages] [Bug 1860133] Re: Memory leak on set_default_locale

2020-01-17 Thread Laurent Stacul
Note: The version embeded in 16.04 does not have the bug (although it is
bash 4.3) but the next releases has it (tested on 18.04 and 19.10). Also
tested on Debian Buster.

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

Title:
  Memory leak on set_default_locale

Status in bash package in Ubuntu:
  New

Bug description:
  Hello,

  I heavily use ubuntu as a build platform to build and package C/C++ 
components.
  Some components are checked in a valgrind environment. On some of them, I am
  reported with the described memory leak due to bash.

  It seems this bug has been fixed in other distros but not in Debian nor 
Ubuntu.
  There is an old bug from bash 4.3 which can be reproduce easily that way:

  ```
  $ valgrind --leak-check=full /bin/bash -c 'exit 0'
  ...
  ==565== 2 bytes in 1 blocks are definitely lost in loss record 14 of 269
  ==565==at 0x483577F: malloc (vg_replace_malloc.c:299)
  ==565==by 0x195E8D: xmalloc (in /bin/bash)
  ==565==by 0x18F51A: set_default_locale (in /bin/bash)
  ==565==by 0x135EE6: main (in /bin/bash)
  ...
  ```

  This has been fixed in fedora that way (and the patch is still here in the
  latest RPMs):

  ```
  >cat bash-4.3-memleak-lc_all.patch
  diff -up bash-4.3/locale.c.old bash-4.3/locale.c
  --- bash-4.3/locale.c.old   2015-07-15 11:55:00.002857301 +0200
  +++ bash-4.3/locale.c   2015-07-15 11:48:36.698086257 +0200
  @@ -77,8 +77,6 @@ set_default_locale ()
   {
   #if defined (HAVE_SETLOCALE)
 default_locale = setlocale (LC_ALL, "");
  -  if (default_locale)
  -default_locale = savestring (default_locale);
   #endif /* HAVE_SETLOCALE */
 bindtextdomain (PACKAGE, LOCALEDIR);
 textdomain (PACKAGE);
  ```

  Do you think it is worth integrating that kind of patch in your package ?
  Regards,
  Stac

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

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


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

2020-01-17 Thread Jean Claveau
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1859996/+attachment/5321133/+files/Dependencies.txt

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean   1301 F pulseaudio
   /dev/snd/pcmC0D0p:   jean   1301 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-07 (131 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags: eoan third-party-packages
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-28 (50 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty 
uucp www-data
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KG004JFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KG004JFR:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KG004JFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KG004JFR
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-17 Thread Jean Claveau
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1859996/+attachment/5321135/+files/ProcEnviron.txt

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean   1301 F pulseaudio
   /dev/snd/pcmC0D0p:   jean   1301 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-07 (131 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags: eoan third-party-packages
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-28 (50 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty 
uucp www-data
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KG004JFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KG004JFR:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KG004JFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KG004JFR
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-17 Thread Jean Claveau
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1859996/+attachment/5321134/+files/ProcCpuinfoMinimal.txt

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean   1301 F pulseaudio
   /dev/snd/pcmC0D0p:   jean   1301 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-07 (131 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags: eoan third-party-packages
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-28 (50 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty 
uucp www-data
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KG004JFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KG004JFR:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KG004JFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KG004JFR
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1859996] PulseList.txt

2020-01-17 Thread Jean Claveau
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1859996/+attachment/5321136/+files/PulseList.txt

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean   1301 F pulseaudio
   /dev/snd/pcmC0D0p:   jean   1301 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-07 (131 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags: eoan third-party-packages
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-28 (50 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty 
uucp www-data
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KG004JFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KG004JFR:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KG004JFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KG004JFR
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


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

2020-01-17 Thread Jean Claveau
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1859996/+attachment/5321132/+files/CurrentDmesg.txt

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean   1301 F pulseaudio
   /dev/snd/pcmC0D0p:   jean   1301 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-07 (131 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags: eoan third-party-packages
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-28 (50 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty 
uucp www-data
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KG004JFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KG004JFR:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KG004JFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KG004JFR
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1859996] Re: pulseaudio-equalizer make pulseaudio's start fail

2020-01-17 Thread Jean Claveau
apport information

** Tags added: apport-collected eoan third-party-packages

** Description changed:

  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound
  
  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.
  
  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it continues
  to fail at start afterwards.
  
  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".
  
  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jean   1301 F pulseaudio
+  /dev/snd/pcmC0D0p:   jean   1301 F...m pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-09-07 (131 days ago)
+ InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: pulseaudio 1:13.0-1ubuntu1.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
+ Tags: eoan third-party-packages
+ Uname: Linux 5.3.0-26-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-11-28 (50 days ago)
+ UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty 
uucp www-data
+ _MarkForUpload: True
+ dmi.bios.date: 11/08/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N23ET59W (1.34 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20KG004JFR
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KG004JFR:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KG004JFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad X1 Carbon 6th
+ dmi.product.name: 20KG004JFR
+ dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
+ dmi.product.version: ThinkPad X1 Carbon 6th
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1859996/+attachment/5321131/+files/AlsaInfo.txt

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  puls

[Touch-packages] [Bug 1860133] [NEW] Memory leak on set_default_locale

2020-01-17 Thread Laurent Stacul
Public bug reported:

Hello,

I heavily use ubuntu as a build platform to build and package C/C++ components.
Some components are checked in a valgrind environment. On some of them, I am
reported with the described memory leak due to bash.

It seems this bug has been fixed in other distros but not in Debian nor Ubuntu.
There is an old bug from bash 4.3 which can be reproduce easily that way:

```
$ valgrind --leak-check=full /bin/bash -c 'exit 0'
...
==565== 2 bytes in 1 blocks are definitely lost in loss record 14 of 269
==565==at 0x483577F: malloc (vg_replace_malloc.c:299)
==565==by 0x195E8D: xmalloc (in /bin/bash)
==565==by 0x18F51A: set_default_locale (in /bin/bash)
==565==by 0x135EE6: main (in /bin/bash)
...
```

This has been fixed in fedora that way (and the patch is still here in the
latest RPMs):

```
>cat bash-4.3-memleak-lc_all.patch
diff -up bash-4.3/locale.c.old bash-4.3/locale.c
--- bash-4.3/locale.c.old   2015-07-15 11:55:00.002857301 +0200
+++ bash-4.3/locale.c   2015-07-15 11:48:36.698086257 +0200
@@ -77,8 +77,6 @@ set_default_locale ()
 {
 #if defined (HAVE_SETLOCALE)
   default_locale = setlocale (LC_ALL, "");
-  if (default_locale)
-default_locale = savestring (default_locale);
 #endif /* HAVE_SETLOCALE */
   bindtextdomain (PACKAGE, LOCALEDIR);
   textdomain (PACKAGE);
```

Do you think it is worth integrating that kind of patch in your package ?
Regards,
Stac

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

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

Title:
  Memory leak on set_default_locale

Status in bash package in Ubuntu:
  New

Bug description:
  Hello,

  I heavily use ubuntu as a build platform to build and package C/C++ 
components.
  Some components are checked in a valgrind environment. On some of them, I am
  reported with the described memory leak due to bash.

  It seems this bug has been fixed in other distros but not in Debian nor 
Ubuntu.
  There is an old bug from bash 4.3 which can be reproduce easily that way:

  ```
  $ valgrind --leak-check=full /bin/bash -c 'exit 0'
  ...
  ==565== 2 bytes in 1 blocks are definitely lost in loss record 14 of 269
  ==565==at 0x483577F: malloc (vg_replace_malloc.c:299)
  ==565==by 0x195E8D: xmalloc (in /bin/bash)
  ==565==by 0x18F51A: set_default_locale (in /bin/bash)
  ==565==by 0x135EE6: main (in /bin/bash)
  ...
  ```

  This has been fixed in fedora that way (and the patch is still here in the
  latest RPMs):

  ```
  >cat bash-4.3-memleak-lc_all.patch
  diff -up bash-4.3/locale.c.old bash-4.3/locale.c
  --- bash-4.3/locale.c.old   2015-07-15 11:55:00.002857301 +0200
  +++ bash-4.3/locale.c   2015-07-15 11:48:36.698086257 +0200
  @@ -77,8 +77,6 @@ set_default_locale ()
   {
   #if defined (HAVE_SETLOCALE)
 default_locale = setlocale (LC_ALL, "");
  -  if (default_locale)
  -default_locale = savestring (default_locale);
   #endif /* HAVE_SETLOCALE */
 bindtextdomain (PACKAGE, LOCALEDIR);
 textdomain (PACKAGE);
  ```

  Do you think it is worth integrating that kind of patch in your package ?
  Regards,
  Stac

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

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


[Touch-packages] [Bug 1860116] Re: evolution-addressbook-factory crashed with signal 5 in g_thread_new()

2020-01-17 Thread Apport retracing service
*** This bug is a duplicate of bug 1858320 ***
https://bugs.launchpad.net/bugs/1858320

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-addressbook-factory crashed with signal 5 in g_thread_new()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  it crashed itself in the background

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.5-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 15 10:41:30 2020
  ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory
  InstallationDate: Installed on 2017-10-13 (825 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_thread_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_data_factory_spawn_subprocess_backend () at 
/usr/lib/x86_64-linux-gnu/libebackend-1.2.so.10
   () at /usr/lib/x86_64-linux-gnu/libedata-book-1.2.so.25
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new()
  UpgradeStatus: Upgraded to bionic on 2018-06-25 (570 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1860116/+subscriptions

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


[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-01-17 Thread Nivedita Singhvi
(active interface)

> cat ethtool-S-enp94s0f1d1 | grep abort
 [0]: tpa_aborts: 19775497
 [1]: tpa_aborts: 26758635
 [2]: tpa_aborts: 12008147
 [3]: tpa_aborts: 15829167
 [4]: tpa_aborts: 25099500
 [5]: tpa_aborts: 3292554
 [6]: tpa_aborts: 2863692
 [7]: tpa_aborts: 20224692


(backup interface)
> cat ethtool-S-enp94s0f0 | grep abort
 [0]: tpa_aborts: 3158584
 [1]: tpa_aborts: 1670319
 [2]: tpa_aborts: 1749371
 [3]: tpa_aborts: 1454301
 [4]: tpa_aborts: 123020
 [5]: tpa_aborts: 1403509
 [6]: tpa_aborts: 1298383
 [7]: tpa_aborts: 1858753

Netted out from previous capture, there were

*f0 = 2014 tpa_aborts
*d1 = 1118473 tpa_aborts


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

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

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0

[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-01-17 Thread Nivedita Singhvi
We suspect this is a device (hw/fw) issue, however, not NetworkManager 
or kernel (driver bnxt_en). I've added the kernel for the driver impact 
(just in case, for now). This is really to eliminate all other causes
and confirm whether it's the device at root cause). 

NIC

Product Name: Broadcom Adv. Dual 10G SFP+ Ethernet
5e:00.1 Ethernet controller: Broadcom Inc. and subsidiaries 
BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01)

NIC Driver/FW
---
driver: bnxt_en
version: 1.10.0
firmware-version: 214.0.253.1/pkg 21.40.25.31
expansion-rom-version:
bus-info: :5e:00.1
supports-statistics: yes

Kernel
-
5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019

(appears to be an issue on all kernel versions)

Environment Configuration
-
active-backup bonding mode

(having the active backup up *might* potentially be the problem, 
 but it might just be the device itself).


The exact same distro, kernel, applications and configuration
works fine with a different NIC (Broadcom 10g bnx2x).

There were quite a few total tpa_abort stats counts (1118473)
during the duration of a 2 minute iperf test. 

Hoping to get more information from other users seeing the
same issue.

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] 

[Touch-packages] [Bug 1853638] Missing required logs.

2020-01-17 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1853638

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0
  Done!

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$

  
  In this particular case description, the nodes are USRP x310s. However, we 
have the same issue with N210 nodes dropping samples connected to the BCM57416 
NetXtreme-E

[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-01-17 Thread Nivedita Singhvi
I have reports of the same device appearing to drop packets and incur
greater number of retransmissions under certain circumstances which
we're still trying to nail down.

I'm using this bug for now until proven to be a different problem.

This is causing issues in a production environment.


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

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Critical

** Tags added: sts

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

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0
  Done!

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$

  
  In this particular case description, the nodes are USRP x310s. However, we 
have the same issue with N210 nodes dropping samples connected to the BCM57416 
NetXtreme-E Dual-Media 10G RDMA Ethernet device.

  There is no problem with the U

[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-01-17 Thread Hui Wang
Thanks Seb.

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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


[Touch-packages] [Bug 1860099] Re: Xorg freeze randomly

2020-01-17 Thread Sondre Kjellmann
Attached command "journalctl -b-1"

** Attachment added: "previousboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1860099/+attachment/5321089/+files/previousboot.txt

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

Title:
  Xorg freeze randomly

Status in xorg package in Ubuntu:
  New

Bug description:
  I've had issues with ubuntu for a couple of days now where the system
  suddenly freezes. I've tried to use the command ALT + Sys Req + REISUB
  with no feedback. The only way (to my knowledge) to get it back is to
  to a hard reboot.

  The freezes can occur when using PhpStorm (when indexing I get it to
  freeze every time) and/or just randomly when browsing, using terminal
  or other programs.

  If you require more logs I can be helpful providing these.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 17 10:43:55 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
  InstallationDate: Installed on 2019-06-05 (226 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=9ac23602-df5d-4612-89a8-5b1cfef4b5bd ro quiet splash 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-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.:bvrF22:bd03/15/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350N-Gaming WIFI
  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.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1860099] Re: Xorg freeze randomly

2020-01-17 Thread Sondre Kjellmann
Here is also a crash file for gnome shell.

** Attachment added: "_usr_bin_gnome-shell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1860099/+attachment/5321088/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  Xorg freeze randomly

Status in xorg package in Ubuntu:
  New

Bug description:
  I've had issues with ubuntu for a couple of days now where the system
  suddenly freezes. I've tried to use the command ALT + Sys Req + REISUB
  with no feedback. The only way (to my knowledge) to get it back is to
  to a hard reboot.

  The freezes can occur when using PhpStorm (when indexing I get it to
  freeze every time) and/or just randomly when browsing, using terminal
  or other programs.

  If you require more logs I can be helpful providing these.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 17 10:43:55 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
  InstallationDate: Installed on 2019-06-05 (226 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=9ac23602-df5d-4612-89a8-5b1cfef4b5bd ro quiet splash 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-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.:bvrF22:bd03/15/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350N-Gaming WIFI
  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.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1860099] [NEW] Xorg freeze randomly

2020-01-17 Thread Sondre Kjellmann
Public bug reported:

I've had issues with ubuntu for a couple of days now where the system
suddenly freezes. I've tried to use the command ALT + Sys Req + REISUB
with no feedback. The only way (to my knowledge) to get it back is to to
a hard reboot.

The freezes can occur when using PhpStorm (when indexing I get it to
freeze every time) and/or just randomly when browsing, using terminal or
other programs.

If you require more logs I can be helpful providing these.

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 17 10:43:55 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
InstallationDate: Installed on 2019-06-05 (226 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=9ac23602-df5d-4612-89a8-5b1cfef4b5bd ro quiet splash 
crashkernel=512M-:192M vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-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.:bvrF22:bd03/15/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
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.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic freeze 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/1860099

Title:
  Xorg freeze randomly

Status in xorg package in Ubuntu:
  New

Bug description:
  I've had issues with ubuntu for a couple of days now where the system
  suddenly freezes. I've tried to use the command ALT + Sys Req + REISUB
  with no feedback. The only way (to my knowledge) to get it back is to
  to a hard reboot.

  The freezes can occur when using PhpStorm (when indexing I get it to
  freeze every time) and/or just randomly when browsing, using terminal
  or other programs.

  If you require more logs I can be helpful providing these.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 17 10:43:55 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
  InstallationDate: Installed on 2019-06-05 (226 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technolo

[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-01-17 Thread Sebastien Bacher
Thanks, I'm going to sponsor that, including to focal since by SRU rules
we need to get the fix there first. That's going to be replaced by the
alsa update at some point but that one is not ready yet

** Changed in: alsa-lib (Ubuntu)
   Status: New => Fix Committed

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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