[Touch-packages] [Bug 1899235] [NEW] Touchpad freeze after overnight sleep

2020-10-09 Thread Meir Levi
Public bug reported:

The real issue is touchpad freeze after wakeup from overnight sleep.
Mouse though does work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: X-Cinnamon
Date: Sat Oct 10 08:14:07 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: I don't know
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
   Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
InstallationDate: Installed on 2020-09-03 (36 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Inspiron 3180
MonitorsUser.xml:
 
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0918N8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.3.0
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3180
dmi.product.sku: 087E
dmi.product.version: 1.3.0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

Title:
  Touchpad freeze after overnight sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  The real issue is touchpad freeze after wakeup from overnight sleep.
  Mouse though does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Oct 10 08:14:07 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2020-09-03 (36 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3180
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: 

[Touch-packages] [Bug 1890827] Re: udev and udevadm documentation missing

2020-10-09 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  udev and udevadm documentation missing

Status in systemd package in Ubuntu:
  Expired

Bug description:
  The man page for udevadm neglects to mention options which seem to
  only be documented in stackexchange.  E.g.

  udevadm monitor --environment

  udevadm control --reload-rules

  From the man page, it's unclear what the difference is between
  /udevadm trigger/ and /udevadm test/.  The description should tell the
  user enough to work out which one they need to use for a certain
  situation.  E.g. I wrote a new rule and it's not triggering.  Is the
  trigger command or the test command suitable for diagnosing the
  problem?

  The documentation in /usr/share/doc/udev/ is strangely specific to
  some esoteric network interface naming.  There is no basic description
  of what udev's purpose is or what its capabilities are.  One of the
  most notable tasks is to react to the insertion of USB drives, and
  there is no mention of this.  The /etc/fstab table also has a role in
  mounting USB drives, but there is no mention as to how udev works with
  /etc/fstab.  I've found that if I remove a line in /etc/fstab and
  attach the drive pertaining to that line, it gets mounted anyway.  If
  the fstab file supercedes udev, then this should be mentioned in the
  documentation.

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

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


[Touch-packages] [Bug 1716205] Re: slovak keyboard does not work in kde

2020-10-09 Thread Launchpad Bug Tracker
[Expired for ibus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  slovak keyboard does not work in kde

Status in ibus package in Ubuntu:
  Expired

Bug description:
  KDE Plasma 5.9.5. I have the Slovak QWERTY keyboard as the secondary
  one. However when I switch to SK keyboard I am not able to input
  slovak-based keys. It is as if the keyboard was not switched at all
  and the layout stays at US-EN. For example pressing + c should yield č
  but it instead prints +c. Previously this randomly failed in some
  apps, e.g. it worked in Libre Office Writer but did not work in
  Konsole; now it doesn't work at all. Pressing 3 should yield š but
  instead types 3.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Sep 10 10:28:48 2017
  InstallationDate: Installed on 2014-03-07 (1282 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to zesty on 2017-03-29 (165 days ago)

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

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


[Touch-packages] [Bug 1890890] Re: more debugging verbosity for udev rules needed

2020-10-09 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  more debugging verbosity for udev rules needed

Status in systemd package in Ubuntu:
  Expired

Bug description:
  I wrote a udev rule that would not trigger when expected.  I spent 2
  days working on it, trying to understand what the problem was.  I
  finally figured it out -- it was a matching problem:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836

  The most verbose output possible is with the log level set to "debug".
  This level of logging does not show users what criteria is being
  checked and what the result is.  So users are working in the dark.  We
  have to guess what udev is doing.  And we're bad at it, because if we
  could guess correctly we probably would have written the rule
  correctly in the first place.

  Consider procmail.  This is an application where users write rules
  that contain matching criteria.  When Procmail doesn't work as
  expected, the logs show in detail what criteria matches and what does
  not.  This is what udev needs.

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

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


[Touch-packages] [Bug 1890892] Re: WSL openssh-server incorrect permissions .ssh

2020-10-09 Thread Launchpad Bug Tracker
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  WSL openssh-server incorrect permissions .ssh

Status in openssh package in Ubuntu:
  Expired

Bug description:
  Using Ubuntu Windows Subsystem for Linux (WSL) 
  $ uname -srvmpio
  Linux 4.4.0-19041-Microsoft #1-Microsoft Fri Dec 06 14:06:00 PST 2019 x86_64 
x86_64 x86_64 GNU/Linux

  (Prestep required to add port for access to windows firewall)
  .ssh directory was set as 777 when 755 (minimum) is required for operation of 
authentication keys when trying to ssh -i /path-to-key/key user@domain.

  Generally poor housekeeping. <3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.3
  ProcVersionSignature: Microsoft 4.4.0-19041.1-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Aug  8 08:44:02 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with 
exit code 127: Error getting authority: Error initializing authority: Could not 
connect: No such file or directory
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1899232] Re: ansible fails with systemd 245.4

2020-10-09 Thread Lightstar
** Bug watch added: github.com/ansible/ansible/issues #71528
   https://github.com/ansible/ansible/issues/71528

** Also affects: systemd via
   https://github.com/ansible/ansible/issues/71528
   Importance: Unknown
   Status: Unknown

** Project changed: systemd => ansible

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

Title:
  ansible fails with systemd 245.4

Status in ansible:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Ansible 2.10.2 fails when determining state of a service on systemd
  245.4 in Ubuntu 20.04. It's related to this bug
  [https://github.com/systemd/systemd/pull/16424]. This bug has been
  fixed in systemd 245.7. Is there plans to release a fix with this?
  Without this fix, ansible fails when attempting to manage services on
  Ubuntu 20.04.

  Ubuntu release: Ubuntu 20.04
  Package: 245.4-4ubuntu3.2 amd64

  What I expected to happen
  Service marked as started when it is stopped.

  What happened instead
  Got 'failed: [127.0.0.1] (item=ssh) => {"ansible_loop_var": "item", 
"changed": false, "item": "ssh", "msg": "Service is in unknown state", 
"status": {}}' 

  
  Thank you.

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

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


[Touch-packages] [Bug 1899232] [NEW] ansible fails with systemd 245.4

2020-10-09 Thread Lightstar
Public bug reported:

Ansible 2.10.2 fails when determining state of a service on systemd
245.4 in Ubuntu 20.04. It's related to this bug
[https://github.com/systemd/systemd/pull/16424]. This bug has been fixed
in systemd 245.7. Is there plans to release a fix with this? Without
this fix, ansible fails when attempting to manage services on Ubuntu
20.04.

Ubuntu release: Ubuntu 20.04
Package: 245.4-4ubuntu3.2 amd64

What I expected to happen
Service marked as started when it is stopped.

What happened instead
Got 'failed: [127.0.0.1] (item=ssh) => {"ansible_loop_var": "item", "changed": 
false, "item": "ssh", "msg": "Service is in unknown state", "status": {}}' 


Thank you.

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

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

Title:
  ansible fails with systemd 245.4

Status in systemd package in Ubuntu:
  New

Bug description:
  Ansible 2.10.2 fails when determining state of a service on systemd
  245.4 in Ubuntu 20.04. It's related to this bug
  [https://github.com/systemd/systemd/pull/16424]. This bug has been
  fixed in systemd 245.7. Is there plans to release a fix with this?
  Without this fix, ansible fails when attempting to manage services on
  Ubuntu 20.04.

  Ubuntu release: Ubuntu 20.04
  Package: 245.4-4ubuntu3.2 amd64

  What I expected to happen
  Service marked as started when it is stopped.

  What happened instead
  Got 'failed: [127.0.0.1] (item=ssh) => {"ansible_loop_var": "item", 
"changed": false, "item": "ssh", "msg": "Service is in unknown state", 
"status": {}}' 

  
  Thank you.

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

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


[Touch-packages] [Bug 1897847] Re: whoopsie assert failure: malloc_consolidate(): unaligned fastbin chunk detected

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1898831 ***
https://bugs.launchpad.net/bugs/1898831

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 #1898831, 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/1897847/+attachment/5415495/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1897847

Title:
  whoopsie assert failure: malloc_consolidate(): unaligned fastbin chunk
  detected

Status in whoopsie package in Ubuntu:
  New

Bug description:
  I was running rsync to copy files from a USB stick when suddenly the
  USB stick was unmounted.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected
  CasperMD5CheckResult: skip
  CrashReports:
   600:119:125:37:2020-09-29 21:29:25.455482641 -0700:2020-09-29 
21:29:25.455482641 -0700:/var/crash/_usr_libexec_tracker-extract.1000.uploaded
   664:1000:125:0:2020-09-29 21:29:38.159510816 -0700:2020-09-29 
21:29:38.159510816 -0700:/var/crash/_usr_libexec_tracker-extract.1000.upload
   640:119:125:4975123:2020-09-29 21:29:37.619511842 -0700:2020-09-29 
21:29:38.619511842 -0700:/var/crash/_usr_bin_whoopsie.119.crash
   640:1000:125:3482147:2020-09-29 21:29:37.067510604 -0700:2020-09-29 
21:29:38.167510833 -0700:/var/crash/_usr_libexec_tracker-extract.1000.crash
  Date: Tue Sep 29 21:29:38 2020
  ExecutablePath: /usr/bin/whoopsie
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  RebootRequiredPkgs:
   linux-image-5.8.0-20-generic
   linux-base
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fe41a1b8128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7fe41a1ba4b8 "malloc_consolidate(): 
unaligned fastbin chunk detected") at malloc.c:5389
   malloc_consolidate (av=av@entry=0x7fe41a1eaba0 ) at malloc.c:4509
   _int_free (av=0x7fe41a1eaba0 , p=0x562a1fc5cfa0, 
have_lock=) at malloc.c:4433
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: malloc_consolidate(): unaligned fastbin chunk 
detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1896706] Re: whoopsie assert failure: free(): double free detected in tcache 2

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1892713 ***
https://bugs.launchpad.net/bugs/1892713

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 #1892713, 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/1896706/+attachment/5413377/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1896706

Title:
  whoopsie assert failure: free(): double free detected in tcache 2

Status in whoopsie package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CasperMD5CheckResult: skip
  Date: Wed Sep 23 05:44:21 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2020-09-22 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  ProcCmdline: /usr/bin/whoopsie -f
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fb33892d128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7fb33892f580 "free(): double free detected 
in tcache 2") at malloc.c:5389
   _int_free (av=0x7fb33895fba0 , p=0x55950a81abe0, have_lock=0) at 
malloc.c:4232
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: whoopsie assert failure: free(): double free detected in tcache 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1896619] Re: whoopsie assert failure: malloc_consolidate(): unaligned fastbin chunk detected

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1898831 ***
https://bugs.launchpad.net/bugs/1898831

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 #1898831, 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/1896619/+attachment/5413162/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1896619

Title:
  whoopsie assert failure: malloc_consolidate(): unaligned fastbin chunk
  detected

Status in whoopsie package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CrashReports:
   640:119:125:4002017:2020-09-22 10:11:14.266442060 -0300:2020-09-22 
10:11:15.266442060 -0300:/var/crash/_usr_bin_whoopsie.119.crash
   664:1000:125:0:2020-09-21 11:06:18.165886148 -0300:2020-09-21 
11:06:18.165886148 -0300:/var/crash/_usr_libexec_tracker-extract.1000.upload
   600:119:125:37:2020-09-21 10:46:53.766066359 -0300:2020-09-21 
10:46:53.766066359 -0300:/var/crash/_usr_libexec_tracker-extract.1000.uploaded
   644:0:125:0:2020-09-21 11:36:40.359460528 -0300:2020-09-21 
11:36:40.359460528 -0300:/var/crash/_usr_bin_whoopsie.119.upload
   640:1000:125:3666047:2020-09-21 11:06:12.969496488 -0300:2020-09-22 
10:11:14.266443329 -0300:/var/crash/_usr_libexec_tracker-extract.1000.crash
  Date: Tue Sep 22 10:11:14 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2020-09-18 (4 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  ProcCmdline: /usr/bin/whoopsie -f
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f857bd61128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f857bd634b8 "malloc_consolidate(): 
unaligned fastbin chunk detected") at malloc.c:5389
   malloc_consolidate (av=av@entry=0x7f857bd93ba0 ) at malloc.c:4509
   _int_free (av=0x7f857bd93ba0 , p=0x55e1165bcb90, 
have_lock=) at malloc.c:4433
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: malloc_consolidate(): unaligned fastbin chunk 
detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1898320] Re: whoopsie assert failure: free(): double free detected in tcache 2

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1892713 ***
https://bugs.launchpad.net/bugs/1892713

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 #1892713, 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/1898320/+attachment/5416817/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1898320

Title:
  whoopsie assert failure: free(): double free detected in tcache 2

Status in whoopsie package in Ubuntu:
  New

Bug description:
  whoopsie assert failure: free(): double free detected in tcac

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Sat Oct  3 06:53:48 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2020-10-02 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1c252f0128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f1c252f2580 "free(): double free detected 
in tcache 2") at malloc.c:5389
   _int_free (av=0x7f1c25322ba0 , p=0x55c031930b30, have_lock=0) at 
malloc.c:4232
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: free(): double free detected in tcache 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1898460] Re: whoopsie assert failure: free(): double free detected in tcache 2

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1892713 ***
https://bugs.launchpad.net/bugs/1892713

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 #1892713, 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/1898460/+attachment/5417514/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1898460

Title:
  whoopsie assert failure: free(): double free detected in tcache 2

Status in whoopsie package in Ubuntu:
  New

Bug description:
  whoopsie assert failure: free(): double free detected in tcac

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Sun Oct  4 16:59:36 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2020-10-02 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa3df31d128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7fa3df31f580 "free(): double free detected 
in tcache 2") at malloc.c:5389
   _int_free (av=0x7fa3df34fba0 , p=0x55f271d06d50, have_lock=0) at 
malloc.c:4232
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: free(): double free detected in tcache 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1898965] Re: whoopsie assert failure: free(): double free detected in tcache 2

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1892713 ***
https://bugs.launchpad.net/bugs/1892713

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 #1892713, 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/1898965/+attachment/5419251/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1898965

Title:
  whoopsie assert failure: free(): double free detected in tcache 2

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Using google chrome caused the issue.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 11:44:50 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2020-06-17 (112 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff4465d128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7eff4465f580 "free(): double free detected 
in tcache 2") at malloc.c:5389
   _int_free (av=0x7eff4468fba0 , p=0x561ff21fd860, have_lock=0) at 
malloc.c:4232
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: free(): double free detected in tcache 2
  UpgradeStatus: Upgraded to groovy on 2020-10-03 (4 days ago)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1898151] Re: whoopsie assert failure: free(): double free detected in tcache 2

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1892713 ***
https://bugs.launchpad.net/bugs/1892713

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 #1892713, 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/1898151/+attachment/5416411/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1898151

Title:
  whoopsie assert failure: free(): double free detected in tcache 2

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Something crashed just after I updated my user picture in the settings

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Thu Oct  1 20:47:04 2020
  ExecutablePath: /usr/bin/whoopsie
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fec67639128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7fec6763b580 "free(): double free detected 
in tcache 2") at malloc.c:5389
   _int_free (av=0x7fec6766bba0 , p=0x55ed94f54310, have_lock=0) at 
malloc.c:4232
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: free(): double free detected in tcache 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1899218] Re: Incorrect warning from apparmor_parser on force complained profiles

2020-10-09 Thread John Johansen
This is addressed by upstream
https://gitlab.com/apparmor/apparmor/-/merge_requests/649

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

Title:
  Incorrect warning from apparmor_parser on force complained profiles

Status in apparmor package in Ubuntu:
  New

Bug description:
  apparmor_parser on a force complained profile produces an incorrect
  warning message:

  $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
  Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
  Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd 
line 54): Warning failed to create cache: usr.sbin.sssd

  Even though not generating the cache at all is expected, the warning
  should describe caching is disabled for force complained profiles
  instead of failure to create it.

  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  $ apt-cache policy apparmor
  apparmor:
    Installed: 3.0.0~beta1-0ubuntu6
    Candidate: 3.0.0~beta1-0ubuntu6
    Version table:
   *** 3.0.0~beta1-0ubuntu6 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1899218] [NEW] Incorrect warning from apparmor_parser on force complained profiles

2020-10-09 Thread Emilia Torino
Public bug reported:

apparmor_parser on a force complained profile produces an incorrect
warning message:

$ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd line 
54): Warning failed to create cache: usr.sbin.sssd

Even though not generating the cache at all is expected, the warning
should describe caching is disabled for force complained profiles
instead of failure to create it.

$ lsb_release -rd
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10

$ apt-cache policy apparmor
apparmor:
  Installed: 3.0.0~beta1-0ubuntu6
  Candidate: 3.0.0~beta1-0ubuntu6
  Version table:
 *** 3.0.0~beta1-0ubuntu6 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status

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

** Summary changed:

- Incorrect warning from sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
+ Incorrect warning from apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd

** Description changed:

  apparmor_parser on a force complained profile produces an incorrect
  warning message:
  
  $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
  Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
  Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd 
line 54): Warning failed to create cache: usr.sbin.sssd
  
- Even though not generating the cache at all is expected, it should
- describe caching is disabled for force complained profiles instead of
- failure to create it.
+ Even though not generating the cache at all is expected, the warning
+ should describe caching is disabled for force complained profiles
+ instead of failure to create it.
  
  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10
  
- 
  $ apt-cache policy apparmor
  apparmor:
-   Installed: 3.0.0~beta1-0ubuntu6
-   Candidate: 3.0.0~beta1-0ubuntu6
-   Version table:
-  *** 3.0.0~beta1-0ubuntu6 500
- 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.0.0~beta1-0ubuntu6
+   Candidate: 3.0.0~beta1-0ubuntu6
+   Version table:
+  *** 3.0.0~beta1-0ubuntu6 500
+ 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
+ 100 /var/lib/dpkg/status

** Summary changed:

- Incorrect warning from apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
+ Incorrect warning from apparmor_parser on force complained profiles

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

Title:
  Incorrect warning from apparmor_parser on force complained profiles

Status in apparmor package in Ubuntu:
  New

Bug description:
  apparmor_parser on a force complained profile produces an incorrect
  warning message:

  $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
  Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
  Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd 
line 54): Warning failed to create cache: usr.sbin.sssd

  Even though not generating the cache at all is expected, the warning
  should describe caching is disabled for force complained profiles
  instead of failure to create it.

  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  $ apt-cache policy apparmor
  apparmor:
    Installed: 3.0.0~beta1-0ubuntu6
    Candidate: 3.0.0~beta1-0ubuntu6
    Version table:
   *** 3.0.0~beta1-0ubuntu6 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1898558] Re: whoopsie assert failure: free(): double free detected in tcache 2

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1892713 ***
https://bugs.launchpad.net/bugs/1892713

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 #1892713, 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/1898558/+attachment/5417841/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1898558

Title:
  whoopsie assert failure: free(): double free detected in tcache 2

Status in whoopsie package in Ubuntu:
  New

Bug description:
  This seems to come up when whoopsie is invoked by another bug.  I
  don't have any other information at this point.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CasperMD5CheckResult: skip
  CrashReports:
   640:1000:125:44301625:2020-10-05 08:26:41.601701021 -0500:2020-10-05 
08:26:42.601701021 -0500:/var/crash/_usr_bin_gnome-shell.1000.crash
   600:119:125:37:2020-10-05 08:42:23.607123280 -0500:2020-10-05 
08:42:23.607123280 -0500:/var/crash/_usr_libexec_tracker-extract.1000.uploaded
   640:1000:125:3580625:2020-10-05 08:42:38.207279443 -0500:2020-10-05 
08:42:40.743294853 -0500:/var/crash/_usr_libexec_tracker-extract.1000.crash
   640:119:125:4561331:2020-10-05 08:42:40.25923 -0500:2020-10-05 
08:42:41.25923 -0500:/var/crash/_usr_bin_whoopsie.119.crash
   664:1000:125:0:2020-10-05 08:42:40.743294853 -0500:2020-10-05 
08:42:40.743294853 -0500:/var/crash/_usr_libexec_tracker-extract.1000.upload
  Date: Mon Oct  5 08:42:40 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2020-10-05 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fd77fb74128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7fd77fb76580 "free(): double free detected 
in tcache 2") at malloc.c:5389
   _int_free (av=0x7fd77fba6ba0 , p=0x558dd306de90, have_lock=0) at 
malloc.c:4232
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: free(): double free detected in tcache 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

2020-10-09 Thread Guilherme G. Piccoli
Thanks for releasing the packages in -proposed Lukasz. I was able to
complete the validation for the Focal version, following the procedure
in the description. An user reported internally to me that the
verification of Bionic version was also successful, hence I'm hereby
marking this LP as verified for both releases.

Bionic version tested: 2:2.0.2-1ubuntu1.2
Focal version tested: 2:2.2.2-3ubuntu2.3

Cheers,


Guilherme

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal
** Tags added: verification-done verification-done-bionic 
verification-done-focal

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  Fix Committed
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, 

[Touch-packages] [Bug 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost

2020-10-09 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg - 1:7.7+19ubuntu15

---
xorg (1:7.7+19ubuntu15) groovy; urgency=medium

  * debian/local/Xsession.d/60x11-common_localhost: Dropped, it's
provided by 35x11-common_xhost-local now. (LP: #1576454)

 -- Timo Aaltonen   Fri, 09 Oct 2020 11:17:12 +0300

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

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

Title:
  Superfluous Xsession.d script: 60x11-common_localhost

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Both of these scripts do the same thing, and both are installed by
  x11-common:

  /etc/X11/Xsession.d/35x11-common_xhost-local
  /etc/X11/Xsession.d/60x11-common_localhost

  35x11-common_xhost-local is present in debian, while
  60x11-common_localhost is not. I suspect the latter should be removed.

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

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


[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-10-09 Thread Dan Streetman
ok, very sorry for my delay in looking at this.

a quick scan of the results for x/b/f show:

ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r xenial -cv 
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:53:00.893145-04:00'
88: boot-smoke   FAIL non-zero exit status 1
(amd64:87 arm64:1)
39: systemd-fsckdFAIL non-zero exit status 1
(amd64:39)
47: boot-and-servicesFAIL non-zero exit status 1
(amd64:41 arm64:6)
ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r bionic -cv 
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:53:18.194358-04:00'
132: systemd-fsckdFAIL non-zero exit status 1
 (i386:14 amd64:117 ppc64el:1)
15: upstream FAIL non-zero exit status 1
(i386:3 amd64:10 ppc64el:1 arm64:1)
29: boot-smoke   FAIL non-zero exit status 1
(i386:2 amd64:27)
ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r focal -cv 
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:56:04.065710-04:00'
96: systemd-fsckdFAIL non-zero exit status 137
(amd64:68 ppc64el:20 s390x:8)
21: systemd-fsckdFAIL non-zero exit status 1
(amd64:1 ppc64el:4 s390x:16)


I think the systemd-fsckd failures are issues with how the test is
trying to detect 'good' and 'bad' service status, but in any case i
rewrote some of the details of how the test works to be simpler and
(hopefully) more accurate/reliable, I'm running it through tests from my
ppa now, before I upload the test change.

I'll take a look at the other test failures; the boot-and-services test
has typically had a lot of trouble with services randomly not starting
ok, but i'll check on the details.

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 

[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

2020-10-09 Thread Matthieu Clemenceau
** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with package
  version 2.20.11-0ubuntu27.10, the problem page at
  https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
  contains more details, including versions of packages affected,
  stacktrace or traceback, and individual crash reports.
  
  Traceback (most recent call last):
-   File "/usr/share/apport/apport", line 451, in 
- options = parse_arguments()
-   File "/usr/share/apport/apport", line 396, in parse_arguments
- parser.print_usage()
-   File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
- self._print_message(self.format_usage(), file)
-   File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
- file.write(message)
+   File "/usr/share/apport/apport", line 451, in 
+ options = parse_arguments()
+   File "/usr/share/apport/apport", line 396, in parse_arguments
+ parser.print_usage()
+   File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
+ self._print_message(self.format_usage(), file)
+   File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
+ file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'
+ 
+ After working on https://bugs.launchpad.net/apport/+bug/1732962, the error 
tracker started throwing the error above.
+ it appears that print_usage is called and throwing an error because in this 
context (called with core_pattern) apport doesn't have an stdout or stderr. 
after looking at traces it seems the kernel is adding 'deleted' to the name of 
the process which cause argument parsing to fail.
+ 
+ The fix below from bdmurray seems to fix it.
+ https://paste.ubuntu.com/p/pVKNP9kWP4/
+ 
+ There is report of this issue in Focal, Bionic and xenial

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

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with package
  version 2.20.11-0ubuntu27.10, the problem page at
  https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
  contains more details, including versions of packages affected,
  stacktrace or traceback, and individual crash reports.

  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 451, in 
  options = parse_arguments()
    File "/usr/share/apport/apport", line 396, in parse_arguments
  parser.print_usage()
    File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
  self._print_message(self.format_usage(), file)
    File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'

  After working on https://bugs.launchpad.net/apport/+bug/1732962, the error 
tracker started throwing the error above.
  it appears that print_usage is called and throwing an error because in this 
context (called with core_pattern) apport doesn't have an stdout or stderr. 
after looking at traces it seems the kernel is adding 'deleted' to the name of 
the process which cause argument parsing to fail.

  The fix below from bdmurray seems to fix it.
  https://paste.ubuntu.com/p/pVKNP9kWP4/

  There is report of this issue in Focal, Bionic and xenial

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

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


[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-10-09 Thread Joshua Powers
** Changed in: cloud-images
   Status: New => Fix Released

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed
   * It should contain pthread, and libgcc_s libraries

  [Regression Potential]

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

  [Other Info]

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

   * Original bug report

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

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

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

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

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

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

  ### With focal 20200522 AMI

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

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

  2. Try: sudo update-initramfs -u

  ## Note

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

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

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

  the following is an apport report on 20200423 AMI:

  

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

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

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


[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

2020-10-09 Thread Matthieu Clemenceau
** Tags added: fr-818

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with package
  version 2.20.11-0ubuntu27.10, the problem page at
  https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
  contains more details, including versions of packages affected,
  stacktrace or traceback, and individual crash reports.

  Traceback (most recent call last):
File "/usr/share/apport/apport", line 451, in 
  options = parse_arguments()
File "/usr/share/apport/apport", line 396, in parse_arguments
  parser.print_usage()
File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
  self._print_message(self.format_usage(), file)
File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'

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

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


[Touch-packages] [Bug 1899194] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@450:parse_arguments:print_usage:_print_message

2020-10-09 Thread Matthieu Clemenceau
*** This bug is a duplicate of bug 1899195 ***
https://bugs.launchpad.net/bugs/1899195

** This bug has been marked a duplicate of bug 1899195
   
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@450:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.10, the problem page at 
https://errors.ubuntu.com/problem/730cdbbb826890cf266891a72ccdc35da0d1abe2 
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/apport/+bug/1899194/+subscriptions

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


[Touch-packages] [Bug 1898879] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@442:parse_arguments:print_usage:_print_message

2020-10-09 Thread Matthieu Clemenceau
*** This bug is a duplicate of bug 1899195 ***
https://bugs.launchpad.net/bugs/1899195

** This bug has been marked a duplicate of bug 1899195
   
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@442:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.1-0ubuntu2.25, the problem page at 
https://errors.ubuntu.com/problem/2b6a1637e787b93e9c46b3b2e981d83c6b571e06 
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/apport/+bug/1898879/+subscriptions

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


[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

2020-10-09 Thread Matthieu Clemenceau
** Tags added: xenial

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with package
  version 2.20.11-0ubuntu27.10, the problem page at
  https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
  contains more details, including versions of packages affected,
  stacktrace or traceback, and individual crash reports.

  Traceback (most recent call last):
File "/usr/share/apport/apport", line 451, in 
  options = parse_arguments()
File "/usr/share/apport/apport", line 396, in parse_arguments
  parser.print_usage()
File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
  self._print_message(self.format_usage(), file)
File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'

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

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


[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

2020-10-09 Thread Matthieu Clemenceau
** Description changed:

- The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.10, the problem page at 
https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e 
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/.
+ The Ubuntu Error Tracker has been receiving reports about a problem
+ regarding apport.  This problem was most recently seen with package
+ version 2.20.11-0ubuntu27.10, the problem page at
+ https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
+ contains more details, including versions of packages affected,
+ stacktrace or traceback, and individual crash reports.
+ 
+ Traceback (most recent call last):
+   File "/usr/share/apport/apport", line 451, in 
+ options = parse_arguments()
+   File "/usr/share/apport/apport", line 396, in parse_arguments
+ parser.print_usage()
+   File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
+ self._print_message(self.format_usage(), file)
+   File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
+ file.write(message)
+ AttributeError: 'NoneType' object has no attribute 'write'

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with package
  version 2.20.11-0ubuntu27.10, the problem page at
  https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
  contains more details, including versions of packages affected,
  stacktrace or traceback, and individual crash reports.

  Traceback (most recent call last):
File "/usr/share/apport/apport", line 451, in 
  options = parse_arguments()
File "/usr/share/apport/apport", line 396, in parse_arguments
  parser.print_usage()
File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
  self._print_message(self.format_usage(), file)
File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'

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

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


[Touch-packages] [Bug 1899195] [NEW] /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

2020-10-09 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding apport.  This problem was most recently seen with package
version 2.20.11-0ubuntu27.10, the problem page at
https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
contains more details, including versions of packages affected,
stacktrace or traceback, and individual crash reports.

Traceback (most recent call last):
  File "/usr/share/apport/apport", line 451, in 
options = parse_arguments()
  File "/usr/share/apport/apport", line 396, in parse_arguments
parser.print_usage()
  File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
self._print_message(self.format_usage(), file)
  File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
file.write(message)
AttributeError: 'NoneType' object has no attribute 'write'

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


** Tags: bionic focal kylin-20.04

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with package
  version 2.20.11-0ubuntu27.10, the problem page at
  https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
  contains more details, including versions of packages affected,
  stacktrace or traceback, and individual crash reports.

  Traceback (most recent call last):
File "/usr/share/apport/apport", line 451, in 
  options = parse_arguments()
File "/usr/share/apport/apport", line 396, in parse_arguments
  parser.print_usage()
File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
  self._print_message(self.format_usage(), file)
File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'

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

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


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

2020-10-09 Thread Shatakhtsyan Artem
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

This is also happening with my JBL TUNE120TWS on Ubuntu 20.04.1
Can not switch to HFP/HSP profile in a GUI-settings menu.
Sound works fine, but have nothing to pick up from in the list of inputs.
Hope this could help.

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Touch-packages] [Bug 1899194] [NEW] /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@450:parse_arguments:print_usage:_print_message

2020-10-09 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.10, the problem page at 
https://errors.ubuntu.com/problem/730cdbbb826890cf266891a72ccdc35da0d1abe2 
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: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic focal

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@450:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.10, the problem page at 
https://errors.ubuntu.com/problem/730cdbbb826890cf266891a72ccdc35da0d1abe2 
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/apport/+bug/1899194/+subscriptions

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


[Touch-packages] [Bug 1876219] Re: iris driver for old cpu

2020-10-09 Thread Sebastian Ramacher
Broken driver or invalid driver selection is nothing we can fix in vlc.

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

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

Title:
  iris driver for old cpu

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in ring package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

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

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


[Touch-packages] [Bug 1876219] Re: iris driver for old cpu

2020-10-09 Thread Adrien Béraud
** Bug watch added: git.jami.net/savoirfairelinux/ring-daemon/issues #264
   https://git.jami.net/savoirfairelinux/ring-daemon/issues/264

** Also affects: mesa via
   https://git.jami.net/savoirfairelinux/ring-daemon/issues/264
   Importance: Unknown
   Status: Unknown

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

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

** Changed in: mesa
   Importance: Unknown => Undecided

** Changed in: mesa
   Status: Unknown => New

** Changed in: mesa
 Remote watch: git.jami.net/savoirfairelinux/ring-daemon/issues #264 => None

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

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

Title:
  iris driver for old cpu

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in ring package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  New

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

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

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


[Touch-packages] [Bug 1898590] Re: Verify DNS fingerprints not working

2020-10-09 Thread Andreas Tauscher
The DNS queries captured with wireshark ssh to unbound and unbound to
world looking correct and allways the AD flag in the responses is set.

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

Title:
  Verify DNS fingerprints not working

Status in openssh package in Ubuntu:
  New

Bug description:
  When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints 
are fetched, but the result is always:
  debug1: found n insecure fingerprints in DNS
  With dig +dnssec -tsshfp hostname the result is ok: ad flg is set.

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

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


[Touch-packages] [Bug 1898590] Re: Verify DNS fingerprints not working

2020-10-09 Thread Andreas Tauscher
With @localhost as parameter it will use the local resolver.
Local resolver is unbound. The cr** systemd resolver is disabled.
Configuration is exactly same like on another machine where it is working like 
expected.
Only difference: Ubuntu 18.04 instead of 20.04.
On 18.04
debug1: found 3 secure fingerprints in DNS
With 20.04
debug1: found 3 insecure fingerprints in DNS
Also when I change the resolver this does not change. So the resolver seems not 
to be the problem.

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

Title:
  Verify DNS fingerprints not working

Status in openssh package in Ubuntu:
  New

Bug description:
  When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints 
are fetched, but the result is always:
  debug1: found n insecure fingerprints in DNS
  With dig +dnssec -tsshfp hostname the result is ok: ad flg is set.

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

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


[Touch-packages] [Bug 1899156] Re: VPN through Network Manager GUI with Pulse Connect Secure host name problem

2020-10-09 Thread Brian Murray
** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  VPN through Network Manager GUI with Pulse Connect Secure host name
  problem

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release version: Ubuntu 20.04.1 LTS
  Version of network-manager-openconnect: 1.2.6-1
  Version of openconnect: 8.05-1

  VPN connection created through Network Manager GUI with VPN Protocol: Pulse 
Connect Secure converts gateway host name to IP when making a connection. It 
results in getting HTTP 404 error in NetworkManager.service logs because of 
failed SSL certificate validation. Screenshot attached.
  Gateway in Network Manager GUI is in URL format: https://xxx

  When using openconnect command: sudo openconnect --protocol=pulse
  https://xxx all works fine.

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

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


[Touch-packages] [Bug 1899156] [NEW] VPN through Network Manager GUI with Pulse Connect Secure host name problem

2020-10-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Release version: Ubuntu 20.04.1 LTS
Version of network-manager-openconnect: 1.2.6-1
Version of openconnect: 8.05-1

VPN connection created through Network Manager GUI with VPN Protocol: Pulse 
Connect Secure converts gateway host name to IP when making a connection. It 
results in getting HTTP 404 error in NetworkManager.service logs because of 
failed SSL certificate validation. Screenshot attached.
Gateway in Network Manager GUI is in URL format: https://xxx

When using openconnect command: sudo openconnect --protocol=pulse
https://xxx all works fine.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
VPN through Network Manager GUI with Pulse Connect Secure host name problem
https://bugs.launchpad.net/bugs/1899156
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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


[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-09 Thread Balint Reczey
The update of the gcc-10 packages have made APT take a different
installation path avoiding hitting this bug. The APT bug is still not
resolved, but it does not affect any installation methods in 20.04
anymore.


** Description changed:

- Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
- http://www.cdimage.ubuntu.com/focal/daily-live/current/
- 
- [Original Bug Text]
- 
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation
  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: apt (Ubuntu Focal)
   Importance: High => Medium

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  In Progress
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: 

[Touch-packages] [Bug 1873678] Re: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name

2020-10-09 Thread Gunnar Hjalmarsson
Thanks for your report!

I could reproduce the problem and have uploaded a fix.

** Information type changed from Private to Public

** Package changed: language-selector (Ubuntu) => accountsservice
(Ubuntu)

** Changed in: accountsservice (Ubuntu)
   Status: New => Fix Committed

** Changed in: accountsservice (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  gnome-language-selector crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is
  not a valid locale name

Status in accountsservice package in Ubuntu:
  Fix Committed

Bug description:
  USB live disk (20.04 beta)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: MATE
  Date: Sun Apr 19 17:07:26 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonArgs: ['/usr/bin/gnome-language-selector']
  PythonDetails: N/A
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a 
valid locale name
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1873678] [NEW] gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name

2020-10-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

USB live disk (20.04 beta)

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: language-selector-gnome 0.203
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CasperVersion: 1.442
CurrentDesktop: MATE
Date: Sun Apr 19 17:07:26 2020
ExecutablePath: /usr/bin/gnome-language-selector
InterpreterPath: /usr/bin/python3.8
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonArgs: ['/usr/bin/gnome-language-selector']
PythonDetails: N/A
SourcePackage: language-selector
Title: gnome-language-selector crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a 
valid locale name
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

** Affects: accountsservice (Ubuntu)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: Fix Committed


** Tags: amd64 apport-crash focal
-- 
gnome-language-selector crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a 
valid locale name
https://bugs.launchpad.net/bugs/1873678
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to accountsservice in Ubuntu.

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


[Touch-packages] [Bug 1899168] [NEW] SRU: update python2.7 to the 2.7.18 release

2020-10-09 Thread Matthias Klose
Public bug reported:

This is a proposal to backport the Python 2.7.18 release to bionic, like
it was done for 2.7.17 in LP: #1855133.

** Affects: python-stdlib-extensions (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python-stdlib-extensions (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: python2.7 (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: python2.7 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python-stdlib-extensions (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: python2.7 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  SRU: update python2.7 to the 2.7.18 release

Status in python-stdlib-extensions package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New
Status in python-stdlib-extensions source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New

Bug description:
  This is a proposal to backport the Python 2.7.18 release to bionic,
  like it was done for 2.7.17 in LP: #1855133.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1899168/+subscriptions

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


[Touch-packages] [Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag

2020-10-09 Thread Sebastien Bacher
Thank you for your bug report, that's the sort of requests that would
probably make more sense to be reported directly upstream

https://github.com/systemd/systemd/issues

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

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

Title:
  systemd-resolve has no --verbose or --debug flag

Status in systemd package in Ubuntu:
  New

Bug description:
  I understand that systemd-resolve is the tool to test queries through
  systemd-resolved.

  When investigation resolution issues (if it resolves fine with dig
  @server domain.to.test but not with systemd-resolved), you can use
  systemd-resolve --status to view the active configuration with the
  link related parameters, OR use systemd-resolve domain.to.test to test
  the resolution (but you have no details, just either a result, or a
  simple "not found").

  It would really help a lot to have either a --verbose or a --debug
  flag, to see which server is queried, why, which domains are actually
  sent in the query (based on the search domains), was the cache used
  (something like the dig output would already be better).

  Thanks!

  Ubuntu version: Ubuntu 18.04.5 LTS
  Systemd version: 237-3ubuntu10.42

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

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


[Touch-packages] [Bug 1899157] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2020-10-09 Thread Neil Carstairs
*** This bug is a duplicate of bug 1897747 ***
https://bugs.launchpad.net/bugs/1897747

Public bug reported:

Upgrading 18.04 to 20.04 failed

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: hostname 4.15.0-111.112-generic 4.15.18
Uname: Linux 4.15.0-111-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_111_112_generic_71
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Oct  9 11:42:12 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2015-12-11 (1763 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-10-09 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading 18.04 to 20.04 failed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: hostname 4.15.0-111.112-generic 4.15.18
  Uname: Linux 4.15.0-111-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_111_112_generic_71
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  9 11:42:12 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-12-11 (1763 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899157/+subscriptions

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


[Touch-packages] [Bug 1899157] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2020-10-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1897747 ***
https://bugs.launchpad.net/bugs/1897747

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 #1897747, 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.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1897747
   package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed 
initramfs-tools package post-installation script subprocess returned error exit 
status 1

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading 18.04 to 20.04 failed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: hostname 4.15.0-111.112-generic 4.15.18
  Uname: Linux 4.15.0-111-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_111_112_generic_71
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  9 11:42:12 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-12-11 (1763 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899157/+subscriptions

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


[Touch-packages] [Bug 1899152] [NEW] Resolution not set or inappropriate

2020-10-09 Thread SatishVSS
Public bug reported:

Defaultly it is set to 1024x768. But my screen resolution is 1440x400.

I tried using terminal to add newmode and saved with the desired
resolution. When I aplied the new one, the system gets hanged everytime.

Previuosly I used 14.04 version. Then there was no issue. I added
newmode using terminal. And next it was fine.

But now it is not allowing me to set.

Please make this issue clear.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  9 16:03:45 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics 
Controller [8086:29c2]
InstallationDate: Installed on 2020-10-02 (6 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: OEM OEM
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=948d3ae0-06d2-4522-8970-f6183d8b94fa ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2018
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.version: OEM
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM:
dmi.product.name: OEM
dmi.product.version: OEM
dmi.sys.vendor: OEM
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution 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/1899152

Title:
  Resolution not set or inappropriate

Status in xorg package in Ubuntu:
  New

Bug description:
  Defaultly it is set to 1024x768. But my screen resolution is 1440x400.

  I tried using terminal to add newmode and saved with the desired
  resolution. When I aplied the new one, the system gets hanged
  everytime.

  Previuosly I used 14.04 version. Then there was no issue. I added
  newmode using terminal. And next it was fine.

  But now it is not allowing me to set.

  Please make this issue clear.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 16:03:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics 
Controller [8086:29c2]
  InstallationDate: Installed on 2020-10-02 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: OEM OEM
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=948d3ae0-06d2-4522-8970-f6183d8b94fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2018
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM:
  dmi.product.name: 

[Touch-packages] [Bug 1899146] [NEW] systemd-resolve has no --verbose or --debug flag

2020-10-09 Thread Olivier Godart
Public bug reported:

I understand that systemd-resolve is the tool to test queries through
systemd-resolved.

When investigation resolution issues (if it resolves fine with dig
@server domain.to.test but not with systemd-resolved), you can use
systemd-resolve --status to view the active configuration with the link
related parameters, OR use systemd-resolve domain.to.test to test the
resolution (but you have no details, just either a result, or a simple
"not found").

It would really help a lot to have either a --verbose or a --debug flag,
to see which server is queried, why, which domains are actually sent in
the query (based on the search domains), was the cache used (something
like the dig output would already be better).

Thanks!

Ubuntu version: Ubuntu 18.04.5 LTS
Systemd version: 237-3ubuntu10.42

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

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

Title:
  systemd-resolve has no --verbose or --debug flag

Status in systemd package in Ubuntu:
  New

Bug description:
  I understand that systemd-resolve is the tool to test queries through
  systemd-resolved.

  When investigation resolution issues (if it resolves fine with dig
  @server domain.to.test but not with systemd-resolved), you can use
  systemd-resolve --status to view the active configuration with the
  link related parameters, OR use systemd-resolve domain.to.test to test
  the resolution (but you have no details, just either a result, or a
  simple "not found").

  It would really help a lot to have either a --verbose or a --debug
  flag, to see which server is queried, why, which domains are actually
  sent in the query (based on the search domains), was the cache used
  (something like the dig output would already be better).

  Thanks!

  Ubuntu version: Ubuntu 18.04.5 LTS
  Systemd version: 237-3ubuntu10.42

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

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


[Touch-packages] [Bug 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost

2020-10-09 Thread Timo Aaltonen
fixed in git now

** Changed in: xorg (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Superfluous Xsession.d script: 60x11-common_localhost

Status in xorg package in Ubuntu:
  In Progress

Bug description:
  Both of these scripts do the same thing, and both are installed by
  x11-common:

  /etc/X11/Xsession.d/35x11-common_xhost-local
  /etc/X11/Xsession.d/60x11-common_localhost

  35x11-common_xhost-local is present in debian, while
  60x11-common_localhost is not. I suspect the latter should be removed.

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

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


[Touch-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

2020-10-09 Thread Sebastien Bacher
> `ubuntu-bug` requires a PID. '

it doesn't, see the manpage, you can also specify a package name as
argument

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

Status in GLib:
  Expired
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as
  well, I haven't tested) causes fstab binds to appear as mounts in
  Nautilus (and in Deepin Dock - Deepin is based on Gnome).

  Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour.

  I first noted this bug behaviour here:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049

  Details of my particular system and issue with what I tried to resolve
  it can be found here:
  https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030

  1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux.

   OS: Arch Linux 
   Kernel: x86_64 Linux 4.10.13-1-ARCH
   Shell: bash 4.4.12
   Resolution: 1920x1200
   DE: Deepin 15.4
   WM: Deepin WM
   WM Theme: Arc-Darker
   GTK Theme: Arc-Darker [GTK2/3]
   Icon Theme: deepin
   Font: Noto Sans 11
   CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C]
   GPU: GeForce GTX 950
   RAM: 2598MiB / 15990MiB

  2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the
  problem).

  3. Nautilus to list internal physical drives (my SSD and 1TB HDD)
  only.

  4. Nautilus listed my system disk (as expected) but also listed all of
  my fstab binds as removable drives (Downloads, Music, Pictures, Videos
  and Documents although this was not listed as "Documents" but instead
  listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide
  those drives.

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

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


[Touch-packages] [Bug 1899041] Re: Gnome-Network-Displays chrashes with Intel Wireless AC due to wpasupplicant - patch available

2020-10-09 Thread Sebastien Bacher
** Changed in: wpa (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Gnome-Network-Displays chrashes with Intel Wireless AC due to
  wpasupplicant - patch available

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  When using Gnome-Network-Displays on a laptop with an Intel Wireless
  AC 9462/9560 card, wpasupplicant crashes. This reproducible bug can be
  fixed with this patch:

  
https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/

  A further description can be found here:

  https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/157

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

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