[Touch-packages] [Bug 1830531] Re: .local domain look ups do not trigger name publication

[Dan Kortschak]

I don't claim that the packets are not being sent, but rather that the
system does not work as expected out of the box when it did in a
previous LTR. I don't really care what package is the cause except to
help get the problem fixed. I have done as much debugging of this as I
am capable since networking is not my area. If additional specific
question need addressing, I can follow up.

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

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

Title:
  .local domain look ups do not trigger name publication

Status in avahi package in Ubuntu:
  New

Bug description:
  On my local network I find that with 18.04 network name lookups using
  .local domains no not work unless stimulated by a non-18.04 machine
  first. This is observed for ssh, http, https and ping, but probably
  not limited to those.

  To demonstrate this here is a ping example.

  ~ $ ping pi.local
  ping: pi.local: Name or service not known
  ~ $ ping pi.local
  ping: pi.local: Name or service not known

  # At this point head to another machine running 16.04.6 and execute ping 
pi.local.
  # This is immediately successful. Then head back to the 18.04 machine.

  ~ $ ping pi.local
  PING pi.local (192.168.108.28) 56(84) bytes of data.
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms
  ^C
  --- pi.local ping statistics ---
  4 packets transmitted, 4 received, 0% packet loss, time 7018ms
  rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms

  After a couple of minutes, the name resolution fails again, but can be
  brought back again by following the procedure above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 26 20:04:58 2019
  InstallationDate: Installed on 2019-05-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.

[Magesh Dhasayyan]

I had the exact same issue. In my case, I upgraded xubuntu 16.04 to 18.04 and 
this issue started showing up. Pulseaudio was also not working.
>From further investigation, I noticed that chrome-remote-desktop was starting 
>Xsession and this was causing issues. I removed that package and it fixed the 
>issue.

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

Title:
  Unlocking existing session often requires several attempts.

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  # Context

  * Computer with several X sessions opened.
  * Users switching from one opened session to another.
  * Lightdm opens new greeter, wait for typing password.
  * User types password.
  * Password is accepted.
  * System closes the current greeter (screen gets black for an instant).

  # Expected

  * User gets back to their already opened session.

  # Observed

  * System immediately opens another greeter.
  * User has to type password again.

  # Reproducible

  * Not always. At times, often, at other times, rare.

  # Additional information

  Users switch session via 
  dm-tool switch-to-user $OTHERUSER
  but I guess bug appears with other means (like menu item like "lock screen", 
etc).

  # Information requested

  lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  LC_ALL=C apt-cache policy lightdm

  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:14:52 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2018-05-25 (18 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.lightdm: [modified]
  mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830

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

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

[Touch-packages] [Bug 1830796] Re: [Bionic][ARM64]Failure debugging linux kernel

[Mathew Hodson]

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

** Changed in: gdb (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gdb (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  [Bionic][ARM64]Failure debugging linux kernel

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  In Progress

Bug description:
  [Impact]
  GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For 
example it is unable to print values of variables like 'jiffies_64'.

  [Test]
  # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic  /proc/kcore
  [New process 1]
  Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=edb5e5a7-8272-4e13-aa25-37'.
  #0  0x in ?? ()
  (gdb) p jiffies_64
  Cannot access memory at address 0x09616980
  (gdb)

  [Fix]
  This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by 
the following patch:
  8727de56b0  Fix tagged pointer support

  [Regression Potential]
  The risk of regression after applying this patch could be to architectures 
other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I 
have tested the PPA package on a ppc64el system and found it does not introduce 
any regressions.

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

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

[Touch-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack

[Mathew Hodson]

** No longer affects: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu)

** No longer affects: xserver-xorg-video-ati-hwe-18.04 (Ubuntu)

** No longer affects: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu)

** No longer affects: xorg-server-hwe-18.04 (Ubuntu)

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-8 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+subscriptions

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

[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Mathew Hodson]

** No longer affects: udisks2 (Ubuntu)

** No longer affects: udisks2 (Ubuntu Bionic)

** No longer affects: udisks2 (Ubuntu Cosmic)

** No longer affects: udisks2 (Ubuntu Disco)

** No longer affects: udisks2 (Ubuntu Eoan)

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Touch-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

On 2019-06-02 01:08, Ping-Wu wrote:
> I might be able to personally force one or two Chinese Ubuntu forum
> participants to test your proposed changes. But that's about it for
> now.

That would be helpful. Not to mention your own observations.

Thanks!

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Bionic:
  Fix Committed
Status in libpinyin source package in Bionic:
  Fix Committed
Status in ibus-libpinyin source package in Cosmic:
  Fix Committed
Status in libpinyin source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.

  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:

  https://errors.ubuntu.com/?package=ibus-libpinyin=month

  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config

  version 1.10.92
  * fixes Enter handling

  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input

  version 1.10.0
  * bug fixes

  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue

  version 1.9.3
  * translate input method name in ibus menu

  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes

  version 2.2.1
  * fixes predicted candidates

  version 2.2.0
  * bug fixes

  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads
  are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

  [Test Case]

  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin

  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.

  (This is apparently not a confirmation that the upload really fixes
  the bug. To compensate for that, we will await testing of the
  -proposed packages by a few Chinese users before considering the
  uploads verified.)

  Reverse dependencies
  
  Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:

  * Install fcitx-libpinyin and ibus-libzhuyin.

  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.

  [Regression Potential]

  The changes are mostly bug fixes, so the regression risk should be
  limited. Also consider that the starting point is a rather unstable
  functionality.

  NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
  as much testing as possible. There do not seem to be too many risky
  changes carried, but such jumps in upstream versions always carry some
  regression-risk.

  [Original description]

  I have experienced random ibus-libpinyin crashes in bionic.  I cannot
  reproduce it, but it occurred at least a few times, even after the
  official bionic release.  Same crashes were also reported in the
  Ubuntu Chinese forum.

  Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
  folder.

  I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
  suggested that we update the version of ibus-libpinyin to 1.10.

  Can we give this update a trial?

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

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

[Touch-packages] [Bug 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

[Bug Watch Updater]

** Bug watch added: Mozilla Bugzilla #1552613
   https://bugzilla.mozilla.org/show_bug.cgi?id=1552613

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

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

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

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

[Touch-packages] [Bug 422511]

[Bug-husbandry-bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1552613

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

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

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

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

[Touch-packages] [Bug 1831351] [NEW] Please provide option to continue bug report from different computer

[Tom Reynolds]

Public bug reported:

There are some situations where it is desirable to gather debugging
information on a system affected by a bug, but to login (to
Launchpad/Ubuntu SSO) and complete editing this bug report from a
different system.

This is already implemented for situations where the affected system
runs headless, i.e. servers without a graphical display. However, this
should also be a user choice exposed as a command line option to ubuntu-
bug (which, at least according to --help it currently is not).

A common use case where this would be nice to have is testing software
in a VM, but not wanting to expose Ubuntu SSO credentials to this VM
(e.g. for security concerns). Another use case is a need to report a
serious bug in the default web browser where this web browser is unable
to access any websites.

There is a workaround:
  DISPLAY= ubuntu-bug somepackage
Unfortunately this means the debugging data collection phase will provide a 
text-only UI instead of the nicer / more user-friendly GTK one.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.6
ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  2 01:24:07 2019
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2019-01-17T11:47:59.939850

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


** Tags: amd64 apport-bug bionic

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

Title:
  Please provide option to continue bug report from different computer

Status in apport package in Ubuntu:
  New

Bug description:
  There are some situations where it is desirable to gather debugging
  information on a system affected by a bug, but to login (to
  Launchpad/Ubuntu SSO) and complete editing this bug report from a
  different system.

  This is already implemented for situations where the affected system
  runs headless, i.e. servers without a graphical display. However, this
  should also be a user choice exposed as a command line option to
  ubuntu-bug (which, at least according to --help it currently is not).

  A common use case where this would be nice to have is testing software
  in a VM, but not wanting to expose Ubuntu SSO credentials to this VM
  (e.g. for security concerns). Another use case is a need to report a
  serious bug in the default web browser where this web browser is
  unable to access any websites.

  There is a workaround:
DISPLAY= ubuntu-bug somepackage
  Unfortunately this means the debugging data collection phase will provide a 
text-only UI instead of the nicer / more user-friendly GTK one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.6
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  2 01:24:07 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2019-01-17T11:47:59.939850

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

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

[Touch-packages] [Bug 1831349] Re: apport-gtk crashes with SIGSEGV if invalid DISPLAY given

[Apport retracing service]

*** This bug is a duplicate of bug 1552577 ***
https://bugs.launchpad.net/bugs/1552577

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 #1552577, 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/1831349/+attachment/5268329/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV in 
_gtk_style_provider_private_get_settings(provider=0x0) 
[gtkstyleproviderprivate.c:123]

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

Title:
  apport-gtk crashes with SIGSEGV if invalid DISPLAY given

Status in apport package in Ubuntu:
  New

Bug description:
  Running 
DISPLAY=-1 ubuntu-bug somepackage
  prints
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Segmentation fault (core dumped)
  and apport stops working.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport-gtk 2.20.9-0ubuntu7.6
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportLog:
   ERROR: apport (pid 5603) Sun Jun  2 01:09:25 2019: called for pid 5601, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 5603) Sun Jun  2 01:09:25 2019: script: 
/usr/share/apport/apport-gtk, interpreted by /usr/bin/python3.6 (command line 
"/usr/bin/python3 /usr/share/apport/apport-gtk firefox")
   ERROR: apport (pid 5603) Sun Jun  2 01:09:25 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 5603) Sun Jun  2 01:09:28 2019: wrote report 
/var/crash/_usr_share_apport_apport-gtk.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CrashReports:
   640:1000:120:7086798:2019-06-02 01:09:27.912482976 +0200:2019-06-02 
01:09:28.912482976 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   664:1000:120:0:2019-06-01 08:56:03.472304200 +0200:2019-06-01 
08:56:03.472304200 
+0200:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.upload
   640:1000:120:39799435:2019-06-01 08:55:52.336284875 +0200:2019-06-01 
08:55:53.336284875 
+0200:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
   600:111:120:0:2019-06-01 08:56:59.784414481 +0200:2019-06-01 
08:56:59.784414481 
+0200:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  2 01:09:25 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk firefox
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SegvAnalysis:
   Segfault happened at: 0x7fd54c9acff9:mov(%rbx),%rdi
   PC (0x7fd54c9acff9) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo users vboxusers

To manage notifications about this bug go to:

Re: [Touch-packages] [Bug 1768166] Re: Random crashes

[Ping-Wu]

Duly noted.

I am hitting a brick wall in the Chinese Ubuntu forum.  It turns out that
nobody is using the ibus-libpinyin input method.

Would you be interested in using, as part of your daily routine, an input
tool that can suddenly crash and cannot be recovered until you delete all
the vocabulary that you have painstakingly built?  I won't blame them.

Switching to a different Chinese input method is much more involved than
you may think.  Even temporarily.  I might be able to personally force one
or two Chinese Ubuntu forum participants to test your proposed changes.
But that's about it for now.


On Sat, Jun 1, 2019 at 10:30 AM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:

> @Ping-Wu: Which tools for inputting Chinese should be available on
> Ubuntu going forward is indeed a valid discussion, but this bug report
> is not a proper place for it. I notice your strong interest in the
> topic, and if you want to start such a discussion, I would suggest that
> you start a thread at .
>
> For Ubuntu 18.04 we have the tools which are in the archive, and ibus-
> libpinyin ("Intelligent Pinyin") is the default method for Simplified
> Chinese. This bug (filed by yourself) is about upgrading the software
> for that method, and only that.
>
> So can we please focus here on testing the proposal to upgrade, and hold
> the wider discussion in e.g. the Ubuntu Community Hub?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
>   Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
>   Fix Released
> Status in libpinyin package in Ubuntu:
>   Fix Released
> Status in ibus-libpinyin source package in Bionic:
>   Fix Committed
> Status in libpinyin source package in Bionic:
>   Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
>   Fix Committed
> Status in libpinyin source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   ibus-libpinyin has proved to crash far too often. One or more files in
>   ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
>   directory allows the user to keep using ibus-libpinyin.
>
>   In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
>   present, and the number of crashes has been reduced significantly:
>
>   https://errors.ubuntu.com/?package=ibus-libpinyin=month
>
>   Upstream ChangeLog ibus-libpinyin:
>   --
>   version 1.11.0
>   * fixes keypad decimal
>   * fixes emoji candidates
>   * support configurable opencc config
>
>   version 1.10.92
>   * fixes Enter handling
>
>   version 1.10.91
>   * support ime.register_trigger in lua extension
>   * support predicted candidates
>   * support emoji input
>
>   version 1.10.0
>   * bug fixes
>
>   version 1.9.91
>   * migrate to use GSettings
>   * fixes lyx short cut issue
>
>   version 1.9.3
>   * translate input method name in ibus menu
>
>   Upstream ChangeLog libpinyin:
>   -
>   version 2.2.2
>   * minor fixes
>
>   version 2.2.1
>   * fixes predicted candidates
>
>   version 2.2.0
>   * bug fixes
>
>   The proposal is to backport the disco versions of those packages to
>   bionic and cosmic in an attempt to prevent crashes. Proposed uploads
>   are available in this PPA:
>
>   https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
>
>   [Test Case]
>
>   * Install from {bionic,cosmic}-proposed:
> - libpinyin13
> - libpinyin-data
> - ibus-libpinyin
>
>   * Use "Intelligent Pinyin" for typing and confirm that no new issues
> show up when doing so.
>
>   (This is apparently not a confirmation that the upload really fixes
>   the bug. To compensate for that, we will await testing of the
>   -proposed packages by a few Chinese users before considering the
>   uploads verified.)
>
>   Reverse dependencies
>   
>   Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend
> on packages belonging to the libpinyin source package. So additional test
> measures are:
>
>   * Install fcitx-libpinyin and ibus-libzhuyin.
>
>   * Use both those tools for typing Chinese, and confirm that you don't
> observe any adverse effects of the libpinyin upgrade.
>
>   [Regression Potential]
>
>   The changes are mostly bug fixes, so the regression risk should be
>   limited. Also consider that the starting point is a rather unstable
>   functionality.
>
>   NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
>   as much testing as possible. There do not seem to be too many risky
>   changes carried, but such jumps in upstream versions always carry some
>   regression-risk.
>
>   [Original description]
>
>   I have experienced random ibus-libpinyin crashes in bionic.  I cannot
>   reproduce it, but it occurred at least a few times, even after the
>   official bionic release.  Same crashes were also 

[Touch-packages] [Bug 1830635] Re: Regression: xenial: Uses apt_pkg.Error, which is only available in later versions

[Mathew Hodson]

** No longer affects: python-apt (Ubuntu)

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

Title:
  Regression: xenial: Uses apt_pkg.Error, which is only available in
  later versions

Status in python-apt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The last SRU introduced a regression in error handling, where apt_pkg.Error 
is being caught - but that class is not available in xenial - it still uses 
SystemError

  [Test case]

  Run python3 -c "import apt; apt.Cache().update()" while running apt
  update.

  You should see:

  # 
  Traceback (most recent call last):
    File "", line 1, in 
    File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 468, in update
  raise LockFailedException("Failed to lock %s" % lockfile)
  apt.cache.LockFailedException: Failed to lock /var/lib/apt/lists/lock

  Currently you see:
  # 
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 63, in __enter__
  return self._lock.__enter__()
  SystemError: E:Could not get lock /var/lib/apt/lists/lock - open (11: 
Resource temporarily unavailable)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "", line 1, in 
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 481, in update
  with _WrappedLock(apt_pkg.config.find_dir("Dir::State::Lists")):
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 64, in __enter__
  except apt_pkg.Error as e:
  AttributeError: module 'apt_pkg' has no attribute 'Error'

  [Regression potential]
  It really can't get worse than this. But FWIW: This only affects code paths 
where we could not lock the lists/ or archives/ directory - they currently 
throw the AttributeError, and will then throw LockFailedException again - as 
they did before the SRU.

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

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

[Touch-packages] [Bug 1831221] Re: do-release-upgrade fails due to package libpam0g:amd64 1.1.8-3.2ubuntu2.1

[Steve Langasek]

Thanks for following up. Closing this bug invalid then.

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

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

Title:
  do-release-upgrade fails due to package libpam0g:amd64
  1.1.8-3.2ubuntu2.1

Status in pam package in Ubuntu:
  Invalid

Bug description:
  While performing a release upgrade from 14.04 to 16.04, the do-
  release-upgrade process crashes, apparently due to a failure
  installing or upgrading the package libpam0g:amd64 1.1.8-3.2ubuntu2.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam0g:amd64 1.1.8-3.2ubuntu2.1
  ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-165-generic x86_64
  NonfreeKernelModules: rr232x
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Fri May 31 04:35:26 2019
  DuplicateSignature: package:libpam0g:amd64:1.1.8-3.2ubuntu2.1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: pam
  Title: package libpam0g:amd64 1.1.8-3.2ubuntu2.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-05-31 (0 days ago)

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

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

[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Mathew Hodson]

** Tags removed: removal-candidate verification-needed 
verification-needed-xenial
** Tags added: verification-failed-artful verification-failed-xenial

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  Won't Fix
Status in protobuf source package in Xenial:
  Won't Fix
Status in py-macaroon-bakery source package in Xenial:
  Won't Fix
Status in pymacaroons source package in Xenial:
  Won't Fix
Status in httmock source package in Artful:
  Fix Released
Status in protobuf source package in Artful:
  Fix Released
Status in py-macaroon-bakery source package in Artful:
  Won't Fix
Status in pymacaroons source package in Artful:
  Won't Fix

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

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

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

[Touch-packages] [Bug 1825212] Re: [SRU] openssl disco

[Mathew Hodson]

Fixed in Eoan
---

openssl (1.1.1b-2ubuntu1) devel; urgency=medium

  * Merge from Debian unstable, remaining changes:
- Replace duplicate files in the doc directory with symlinks.
- debian/libssl1.1.postinst:
  + Display a system restart required notification on libssl1.1
upgrade on servers.
  + Use a different priority for libssl1.1/restart-services depending
on whether a desktop, or server dist-upgrade is being performed.
- Revert "Enable system default config to enforce TLS1.2 as a
  minimum" & "Increase default security level from 1 to 2".
- Drop the NEWS entry, not applicable on Ubuntu.

openssl (1.1.1b-2) unstable; urgency=medium

  * Fix BUF_MEM regression (Closes: #923516)
  * Fix error when config can't be opened (Closes: #926315)
  * Ship an openssl.cnf in libssl1.1-udeb.dirs

 -- Dimitri John Ledkov   Wed, 17 Apr 2019 17:26:42
+0100

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

** Bug watch removed: gitlab.labs.nic.cz/datovka/datovka/issues #410
   https://gitlab.labs.nic.cz/datovka/datovka/issues/410

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

Title:
  [SRU] openssl disco

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * openssl has BUF_MEM regression that may affect packages at runtime.
   * openssl has a regression of failing to initialize SSL context without 
openssl.cnf file

  [Test Case]

   * Compile an old r-cran-openssl and run its autopkgtest against the
  current & fixed openssl, it should fail and pass respectively

   * remove openssl.cnf and try to use curl https://www.ubuntu.com it
  should succeed

  [Regression Potential]

   * These are regressions in the 1.1.1 series, witch patches cherrypicked from 
openssl stable branch and the same patches were uploaded into Debian.
   * The above two issues may continue to persist

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

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

[Touch-packages] [Bug 1831347] [NEW] Xorg freeze - update

[Peter]

Public bug reported:

Dear Ubuntu,

Thank you for taking the time to read this report. My last report stated
that nvidia-430 driver was the problem. I have since reinstalled ubuntu
18.4 and carefully followed the EGPU setup provided online using
gswitch. I should note that last install I forgot to add "systemctl
enable gswitch". I have noticed far fewer issues. Interestingly, I also
enabled autologin for my account. This appears to have helped the
problem significantly. I did try switching to regular password required
at login and the freezing / hanging did occur during some web browsing
but it was only for about 5 - 10 seconds. I then immediately switched
back to autologins and I have not noticed any freezing or hanging! I
believe the problem with regular password req logins is that it causes
my internal display (laptop screen) to be enabled first during the login
when I enter my password. After I enter my password the internal display
turns off and then I use my external display only as I have that
confiured in the ubuntu device settings. But with autologin, the
computer boots momentarily to internal screen when you see the ubuntu
dots sliding to the right and then into gnome.

So it appears using autologin is more stable when using an EGPU with
external display only! I am using nvidia-430 drivers.

So I think gdm3 needs an update or X11 needs an update so that it can
honor the external display better? Anyways! I will keep you posted.

Thanks for your dedication guys!!

Take care,

Peter

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.14  Wed May  8 01:10:53 
UTC 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  1 16:26:04 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.67, 4.18.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696]
InstallationDate: Installed on 2019-06-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. XPS 15 9570
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=96ec9aa4-d13a-4223-b15b-4284df054c79 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install 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/1831347

Title:
  Xorg freeze - update

Status in xorg package in Ubuntu:
  New

Bug description:
  Dear Ubuntu,

  Thank you for taking 

[Touch-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

@Ping-Wu: Which tools for inputting Chinese should be available on
Ubuntu going forward is indeed a valid discussion, but this bug report
is not a proper place for it. I notice your strong interest in the
topic, and if you want to start such a discussion, I would suggest that
you start a thread at .

For Ubuntu 18.04 we have the tools which are in the archive, and ibus-
libpinyin ("Intelligent Pinyin") is the default method for Simplified
Chinese. This bug (filed by yourself) is about upgrading the software
for that method, and only that.

So can we please focus here on testing the proposal to upgrade, and hold
the wider discussion in e.g. the Ubuntu Community Hub?

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Bionic:
  Fix Committed
Status in libpinyin source package in Bionic:
  Fix Committed
Status in ibus-libpinyin source package in Cosmic:
  Fix Committed
Status in libpinyin source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.

  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:

  https://errors.ubuntu.com/?package=ibus-libpinyin=month

  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config

  version 1.10.92
  * fixes Enter handling

  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input

  version 1.10.0
  * bug fixes

  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue

  version 1.9.3
  * translate input method name in ibus menu

  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes

  version 2.2.1
  * fixes predicted candidates

  version 2.2.0
  * bug fixes

  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads
  are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

  [Test Case]

  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin

  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.

  (This is apparently not a confirmation that the upload really fixes
  the bug. To compensate for that, we will await testing of the
  -proposed packages by a few Chinese users before considering the
  uploads verified.)

  Reverse dependencies
  
  Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:

  * Install fcitx-libpinyin and ibus-libzhuyin.

  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.

  [Regression Potential]

  The changes are mostly bug fixes, so the regression risk should be
  limited. Also consider that the starting point is a rather unstable
  functionality.

  NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
  as much testing as possible. There do not seem to be too many risky
  changes carried, but such jumps in upstream versions always carry some
  regression-risk.

  [Original description]

  I have experienced random ibus-libpinyin crashes in bionic.  I cannot
  reproduce it, but it occurred at least a few times, even after the
  official bionic release.  Same crashes were also reported in the
  Ubuntu Chinese forum.

  Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
  folder.

  I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
  suggested that we update the version of ibus-libpinyin to 1.10.

  Can we give this update a trial?

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

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

[Touch-packages] [Bug 1831339] [NEW] Backup Unbuntu ERROR undefined

[Louis Peutzen]

Public bug reported:

Backup Unbuntu ERROR undefined

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sat Jun  1 14:59:04 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
InstallationDate: Installed on 2019-03-27 (66 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
dmi.board.name: P5N-E SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr 24 21:29:22 2019

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


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

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

Title:
  Backup Unbuntu ERROR undefined

Status in xorg package in Ubuntu:
  New

Bug description:
  Backup Unbuntu ERROR undefined

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Jun  1 14:59:04 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
  InstallationDate: Installed on 2019-03-27 (66 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
  dmi.board.name: P5N-E SLI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1831335] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  Can not this be fixed?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
  Uname: Linux 4.4.0-148-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Sat Jun  1 12:03:59 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-18 (743 days ago)
  InstallationMedia: Custom 14.04 - Release i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 88: Bad configuration option: Y
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-10-11 (233 days ago)

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

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

[Touch-packages] [Bug 1831335] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[malangaman]

Public bug reported:

Can not this be fixed?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.8
ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
Uname: Linux 4.4.0-148-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Sat Jun  1 12:03:59 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-05-18 (743 days ago)
InstallationMedia: Custom 14.04 - Release i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SSHDConfig:
 Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 88: Bad configuration option: Y
 /etc/ssh/sshd_config: terminating, 1 bad configuration options
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-10-11 (233 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  Can not this be fixed?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
  Uname: Linux 4.4.0-148-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Sat Jun  1 12:03:59 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-18 (743 days ago)
  InstallationMedia: Custom 14.04 - Release i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 88: Bad configuration option: Y
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-10-11 (233 days ago)

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

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

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Dan Streetman]

> Is this going to be fixed in disco?

speaking for systemd only, the commit needed is 
a97a3b256cd6c56ab1d817440d3b8acb3272ee17:
https://github.com/systemd/systemd/commit/a97a3b256

that's included starting at v240, so is already in disco.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked

[crysman]

Another piece of information:
It seems to be broken only once - at the first time. When I do the workaround 
and let it go blank again, no need to repeat it - just once every fresh boot 
seems to be enough. Weird...

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

Title:
  [nouveau][XFCE] Do not see login screen after screen is blanked

Status in lightdm package in Ubuntu:
  New

Bug description:
  I've just upgraded to 18.10 from 18.04. Now when power manager (or
  whoever) puts the screen to blank, I cannot login, because I do not
  see anything. Befeore the upgrade, mouse move or keypress led to login
  screen. Now does not.

  Workaround:
  When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears.

  Where is the problem and how to fix it please?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri May 24 17:59:31 2019
  DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1682]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682]
  InstallationDate: Installed on 2018-09-03 (263 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK Computer Inc. U36SD
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic 
root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago)
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: U
  dmi.product.name: U36SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1769391

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

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

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

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

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

Title:
  18.04 Install, not detecting bluetooth

Status in Ubuntu MATE:
  Invalid
Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ lspci -knn | grep Net -A3; lsusb
  01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network 
Adapter [168c:0032] (rev 01)
Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter 
[103c:1785]
Kernel driver in use: ath9k
Kernel modules: ath9k
  02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 05)
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 004: ID 0cf3:311d Atheros Communications, Inc. 
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 003: ID 058f:a001 Alcor Micro Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 0e8f:00a7 GreenAsia Inc. 
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ 
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ sudo /etc/init.d/bluetooth start
  [ ok ] Starting bluetooth (via systemctl): bluetooth.service.

  tyoma@HP-Pavilion-g7-Notebook-PC:~$ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:6 acl:0 sco:0 events:1 errors:0
TX bytes:3 acl:0 sco:0 commands:6 errors:5
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1 
Link policy: 
Link mode: SLAVE ACCEPT 

  tyoma@HP-Pavilion-g7-Notebook-PC:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1769391/+subscriptions

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

[Touch-packages] [Bug 1660121] Re: LightDM can't use the user background on Mate

[Norbert]

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

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

Title:
  LightDM can't use the user background on Mate

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04
  alpha 2).

  On Mate, the LightDM Gtk Greeter can't use the user background. It
  works fine on other DEs like Xfce.

  From what I understand, LightDM and/or the Gkt greeter (not sure which
  one handles the background) gets the background path from Gsettings,
  so I assume it can't find the one from Mate, which stores it in
  "org.mate.background picture-filename".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1660121/+subscriptions

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

Re: [Touch-packages] [Bug 1768166] Re: Random crashes

[Ping-Wu]

I have been hearing this swan song for several years now that ibus-pinyin
is being or has been deprecated.  Actually it is a miracle that ibus-pinyin
still works in Ubuntu--*and only in Ubuntu*.  For unknown and very strange
reasons, I can never make ibus-pinyin work in Fedora, or even in Debian.
Indeed, this is the main reason that I am sticking with Ubuntu, even though
I was one of the very first supporters of the Fedora Linux when it was
being developed at the University of Hawaii.

Most Linux users in the Chinese Ubuntu forum actually use Sogou pinyin
(搜狗拼音）, this is a proprietary program running on the fcitx input
framework.  Sogou pinyin is definitely better than ibus-libpinyin (very few
people actually use ibus-libpinyin), but is inferior to ibus-pinyin in
terms of speed and stability.  We have a pro bono project in Honolulu
teaching seniors to be proficient in computers. Since many of our students
are of Chinese descent, our program also includes teaching them how to
input Chinese characters.  Ibus-pinyin has been our choice of Chinese input
tool because of its snappiness and being trouble-free.  You would think
that these two characters should also make ibus-pinyin a favorable Chinese
input engine?  But since so few people in China are using Linux desktops,
logic doesn't make sense.  It is the so-called upstream developers (mainly
Peng Wu of Red Hat), or the lack thereof (ibus-pinyin developers), that
prevails.

Based on my interactions with many Chinese Ubuntu forum elders, I am NOT
surprised that the upstream developers do not think highly of ibus-pinyin.
The reasons are three-fold: first, they are not using the right distro
(i.e., not using Ubuntu); second, they did not install a Ubuntu-specific
ibus-pinyin database (i.e., system-wide vocabulary); and third, they have
not used ibus-pinyin long enough (i.e., they do not have their own user
vocabulary).

I think upstream developers do not like ibus-pinyin also because it does
not have many bells and whistles (e.g., inputting emojis which I absolutely
could care less).  But ibus-pinyin also has some of the critical features
that are lacking in ibus-libpinyin.  For example, the latter cannot
conveniently input special symbols (many in the Chinese Ubuntu forum think
this a main reason not to use ibus-libpinyin).  Also, ibus-libpinyin will
treat a decimal point as a Chinese period, such as 19。04 (which should be
19.04）.   But most important AFAIC, ibus-pinyin uses a simple,
straightforward sqlite database structure that is very easy to comprehend.
How the table-lookup database is structured in ibus-libpinyin is
complicated and undocumented.

Many members of the Chinese Ubuntu forum have a very negative attitude
towards ibus-libpinyin partly because of the personality of its principal
developer Peng Wu.  They have always complained about being contemptuously
snobbed when they visited the ibus-libpinyin GitHub forum (many were told
to switch to Fedora).  I myself also could never get a straight answer from
Peng Wu.

I sincerely hope that your effort to make ibus-libpinyin stable ("stable"
in an absolute sense) will help attracting more users--ibus-libpinyin in
specific and Ubuntu in general.  I will definitely use it at least
occasionally to make sure that everything is OK.  Should Ubuntu
powers-that-be make an unfortunate decision and drop ibus-pinyin from its
archive, I will simply freeze my version of Ubuntu at 18.04, which is now
turning out to be exceptionally good.

On Fri, May 31, 2019 at 9:20 PM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:

> @Ping-Wu: ibus-pinyin will soon be removed from the archive.
>
> $ zcat /usr/share/doc/ibus-pinyin/NEWS.Debian.gz
> ibus-pinyin (1.5.0-5) unstable; urgency=medium
>
> Package ibus-pinyin is now deprecated; its upstream has stopped
> development
> for years in favour of new ibus-libpinyin. New ibus users should
> install
> ibus-libpinyin instead of this package. This package (ibus-pinyin)
> will be
> removed after Debian Buster (Debian 10) release.
>
>  -- Boyuan Yang   Tue, 18 Sep 2018 16:53:42 -0400
>
> Seems like it won't be present in the Ubuntu 20.04 archive.
>
> So let's focus 100% on ibus-libpinyin at this bug report.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
>   Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
>   Fix Released
> Status in libpinyin package in Ubuntu:
>   Fix Released
> Status in ibus-libpinyin source package in Bionic:
>   Fix Committed
> Status in libpinyin source package in Bionic:
>   Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
>   Fix Committed
> Status in libpinyin source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   ibus-libpinyin has proved to crash far too often. One or more files in
>   ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
>   directory allows the 

[Touch-packages] [Bug 1769391] Re: 18.04 Install, not detecting bluetooth

[Ubuntu Kernel Bot]

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  18.04 Install, not detecting bluetooth

Status in Ubuntu MATE:
  Invalid
Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ lspci -knn | grep Net -A3; lsusb
  01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network 
Adapter [168c:0032] (rev 01)
Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter 
[103c:1785]
Kernel driver in use: ath9k
Kernel modules: ath9k
  02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 05)
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 004: ID 0cf3:311d Atheros Communications, Inc. 
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 003: ID 058f:a001 Alcor Micro Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 0e8f:00a7 GreenAsia Inc. 
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ 
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ sudo /etc/init.d/bluetooth start
  [ ok ] Starting bluetooth (via systemctl): bluetooth.service.

  tyoma@HP-Pavilion-g7-Notebook-PC:~$ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:6 acl:0 sco:0 events:1 errors:0
TX bytes:3 acl:0 sco:0 commands:6 errors:5
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1 
Link policy: 
Link mode: SLAVE ACCEPT 

  tyoma@HP-Pavilion-g7-Notebook-PC:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1769391/+subscriptions

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1812310

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

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

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

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

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

Title:
  No more sound on lenovo R61i booting MATE 16.04

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I
  was able to listen to a YouTube video from the laptop when booting
  Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04

  Thanks for your consideration,
  Abu Billy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1812310/+subscriptions

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

[Touch-packages] [Bug 1769391] Re: 18.04 Install, not detecting bluetooth

[Norbert]

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

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  18.04 Install, not detecting bluetooth

Status in Ubuntu MATE:
  Invalid
Status in bluez package in Ubuntu:
  New
Status in linux-meta package in Ubuntu:
  New

Bug description:
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ lspci -knn | grep Net -A3; lsusb
  01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network 
Adapter [168c:0032] (rev 01)
Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter 
[103c:1785]
Kernel driver in use: ath9k
Kernel modules: ath9k
  02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 05)
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 004: ID 0cf3:311d Atheros Communications, Inc. 
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 003: ID 058f:a001 Alcor Micro Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 0e8f:00a7 GreenAsia Inc. 
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ 
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ sudo /etc/init.d/bluetooth start
  [ ok ] Starting bluetooth (via systemctl): bluetooth.service.

  tyoma@HP-Pavilion-g7-Notebook-PC:~$ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:6 acl:0 sco:0 events:1 errors:0
TX bytes:3 acl:0 sco:0 commands:6 errors:5
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1 
Link policy: 
Link mode: SLAVE ACCEPT 

  tyoma@HP-Pavilion-g7-Notebook-PC:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1769391/+subscriptions

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

[Touch-packages] [Bug 1812310] Re: No more sound on lenovo R61i booting MATE 16.04

[Norbert]

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

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  No more sound on lenovo R61i booting MATE 16.04

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I
  was able to listen to a YouTube video from the laptop when booting
  Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04

  Thanks for your consideration,
  Abu Billy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1812310/+subscriptions

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

[Touch-packages] [Bug 1812310] Re: No more sound on lenovo R61i booting MATE 16.04

[Ubuntu Kernel Bot]

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  No more sound on lenovo R61i booting MATE 16.04

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I
  was able to listen to a YouTube video from the laptop when booting
  Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04

  Thanks for your consideration,
  Abu Billy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1812310/+subscriptions

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

[Touch-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Norbert]

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  Invalid
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions

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

[Touch-packages] [Bug 1820666] Re: wifi disconnects when a device connects with bluetooth to the computer

[Norbert]

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  wifi disconnects when a device connects with bluetooth to the computer

Status in Ubuntu MATE:
  Invalid
Status in bluez package in Ubuntu:
  New

Bug description:
  When a device connects to the computer using Bluetooth the Wi-Fi
  disconnects for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1820666/+subscriptions

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

[Touch-packages] [Bug 1824281] Re: Printer Won't Work...almost...got closer this time

[Norbert]

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  Printer Won't Work...almost...got closer this time

Status in Ubuntu MATE:
  Invalid
Status in cups package in Ubuntu:
  New

Bug description:
  Page 1 ():
  {'cups_connection_failure': False}
  Page 2 ():
  {'local_server_exporting_printers': False}
  Page 3 ():
  {'cups_dest': ,
   'cups_instance': None,
   'cups_queue': 'Brother-MFC-8860DN',
   'cups_queue_listed': True}
  Page 4 ():
  {'cups_device_uri_scheme': 'usb',
   'cups_printer_dict': {'device-uri': 
'usb://Brother/MFC-8860DN?serial=000C8J645496',
 'printer-info': 'Brother MFC-8860DN',
 'printer-is-shared': True,
 'printer-location': 'ubuntu-mate',
 'printer-make-and-model': 'Brother MFC-8840D for CUPS',
 'printer-state': 3,
 'printer-state-message': '',
 'printer-state-reasons': ['none'],
 'printer-type': 8523796,
 'printer-uri-supported': 
'ipp://localhost/printers/Brother-MFC-8860DN'},
   'cups_printer_remote': False,
   'is_cups_class': False,
   'local_cups_queue_attributes': {'charset-configured': 'utf-8',
   'charset-supported': ['us-ascii', 'utf-8'],
   'color-supported': False,
   'compression-supported': ['none', 'gzip'],
   'copies-default': 1,
   'copies-supported': (1, ),
   'cups-version': '2.2.7',
   'device-uri': 
'usb://Brother/MFC-8860DN?serial=000C8J645496',
   'document-format-default': 
'application/octet-stream',
   'document-format-supported': 
['application/octet-stream',
 
'application/pdf',
 
'application/postscript',
 
'application/vnd.adobe-reader-postscript',
 
'application/vnd.cups-command',
 
'application/vnd.cups-pdf',
 
'application/vnd.cups-pdf-banner',
 
'application/vnd.cups-postscript',
 
'application/vnd.cups-raster',
 
'application/vnd.cups-raw',
 
'application/x-cshell',
 
'application/x-csource',
 
'application/x-perl',
 
'application/x-shell',
 'image/gif',
 'image/jpeg',
 'image/png',
 
'image/pwg-raster',
 'image/tiff',
 'image/urf',
 
'image/x-bitmap',
 
'image/x-photocd',
 
'image/x-portable-anymap',
 
'image/x-portable-bitmap',
 
'image/x-portable-graymap',
 
'image/x-portable-pixmap',
 
'image/x-sgi-rgb',
 
'image/x-sun-raster',
 
'image/x-xbitmap',
 
'image/x-xpixmap',
 
'image/x-xwindowdump',
 'text/css',
  

[Touch-packages] [Bug 1830121] Re: rsync --rsync-path="sudo rsync" over ssh via pki fails due to protocol mismatch

[Norbert]

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  rsync --rsync-path="sudo rsync" over ssh via pki fails due to protocol
  mismatch

Status in Ubuntu MATE:
  Invalid
Status in rsync package in Ubuntu:
  New

Bug description:
  rsync with remote sudo fails over ssh on Ubuntu Mate 18.04.2

  rsync  version 3.1.2  protocol version 31 - same on local and remote
  OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017 - same on local 
and remote

  
  I have checked for spurious output from .bashrc using

  $ ssh user@host /bin/true > out.dat

  which results in

  $ ls -l *.dat
  -rw-rw-r-- 1 user user 0 May 22 23:33 out.dat

  
  -- The [redacted] command is

  rsync -AEavvvogt --rsync-path="sudo rsync" --debug=CONNECT -e "ssh -i
  /home/xxx/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o
  UserKnownHostsFile=/dev/null" --exclude-from=/home/xxx/backup.exclude
  --delete --link-dest=../$lastdt /etc $dest/$dt;

  
  -- The [redacted] output is

  opening connection using: ssh -i /home/user/.ssh/id_rsa -tt -v -o 
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l user xxx "sudo 
rsync" --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . 
/home/backups/xxx/20190522_232738  (20 args)
  OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to xxx [192.168.1.120] port 22.
  debug1: Connection established.
  debug1: permanently_set_uid: 0/0
  debug1: identity file /home/user/.ssh/id_rsa type 0
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug1: Authenticating to xxx:22 as 'user'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha256
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: xxx
  Warning: Permanently added 'xxx,192.168.1.120' (ECDSA) to the list of known 
hosts.
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey,password
  debug1: Next authentication method: publickey
  debug1: Offering public key: RSA SHA256:xxx /home/user/.ssh/id_rsa
  debug1: Server accepts key: xxx
  debug1: Authentication succeeded (publickey).
  Authenticated to xxx ([192.168.1.120]:22).
  debug1: channel 0: new [client-session]
  debug1: Requesting no-more-sessi...@openssh.com
  debug1: Entering interactive session.
  debug1: pledge: network
  debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0
  debug1: tty_make_modes: no fd or tio
  debug1: Sending environment.
  debug1: Sending env LANG = en_GB.UTF-8
  debug1: Sending command: sudo rsync --server -vvvlogDtpAre.iLsfxC --delete 
--link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738
  protocol version mismatch -- is your shell clean?
  (see the rsync man page for an explanation)
  rsync error: protocol incompatibility (code 2) at compat.c(178) [sender=3.1.2]
  [sender] _exit_cleanup(code=2, file=compat.c, line=178): about to call exit(2)

  
  /etc/sudoers contains
  userALL= NOPASSWD:/usr/bin/rsync

  ...which I have tried placing above (as is the default) and below lines 
beginning %admin and %sudo
  and the space in "ALL= NOPASSWD..." doesn't seem to make any difference

  I followed the instructions at
  
https://www.digitalocean.com/community/tutorials/how-to-copy-files-with-rsync-over-ssh
  
https://askubuntu.com/questions/719439/using-rsync-with-sudo-on-the-destination-machine

  - which worked on 16.04, so I wonder if there may be a bug, although
  grateful for any other suggestions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1830121/+subscriptions

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

[Touch-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

@Ping-Wu: ibus-pinyin will soon be removed from the archive.

$ zcat /usr/share/doc/ibus-pinyin/NEWS.Debian.gz
ibus-pinyin (1.5.0-5) unstable; urgency=medium

Package ibus-pinyin is now deprecated; its upstream has stopped development
for years in favour of new ibus-libpinyin. New ibus users should install
ibus-libpinyin instead of this package. This package (ibus-pinyin) will be
removed after Debian Buster (Debian 10) release.

 -- Boyuan Yang   Tue, 18 Sep 2018 16:53:42 -0400

Seems like it won't be present in the Ubuntu 20.04 archive.

So let's focus 100% on ibus-libpinyin at this bug report.

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Bionic:
  Fix Committed
Status in libpinyin source package in Bionic:
  Fix Committed
Status in ibus-libpinyin source package in Cosmic:
  Fix Committed
Status in libpinyin source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.

  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:

  https://errors.ubuntu.com/?package=ibus-libpinyin=month

  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config

  version 1.10.92
  * fixes Enter handling

  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input

  version 1.10.0
  * bug fixes

  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue

  version 1.9.3
  * translate input method name in ibus menu

  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes

  version 2.2.1
  * fixes predicted candidates

  version 2.2.0
  * bug fixes

  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads
  are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

  [Test Case]

  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin

  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.

  (This is apparently not a confirmation that the upload really fixes
  the bug. To compensate for that, we will await testing of the
  -proposed packages by a few Chinese users before considering the
  uploads verified.)

  Reverse dependencies
  
  Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:

  * Install fcitx-libpinyin and ibus-libzhuyin.

  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.

  [Regression Potential]

  The changes are mostly bug fixes, so the regression risk should be
  limited. Also consider that the starting point is a rather unstable
  functionality.

  NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
  as much testing as possible. There do not seem to be too many risky
  changes carried, but such jumps in upstream versions always carry some
  regression-risk.

  [Original description]

  I have experienced random ibus-libpinyin crashes in bionic.  I cannot
  reproduce it, but it occurred at least a few times, even after the
  official bionic release.  Same crashes were also reported in the
  Ubuntu Chinese forum.

  Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
  folder.

  I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
  suggested that we update the version of ibus-libpinyin to 1.10.

  Can we give this update a trial?

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

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

[Touch-packages] [Bug 645404] Re: Support Private PPAs

[Julian Andres Klode]

So multiple ssh subprocesses should not be a huge issue, you could after
all use ControlMaster and stuff to reuse the connection.

That said, it seems reasonable to create a shell script, or a Python
script and execute that on the remote from stdin.

python3 and python3-apt should be available on all systems I think to do
config lookups, and the content of files can be embedded into a
generated script in base64.

That said, it would be an entirely different code path which I think
might be worse than it maybe not working if the remote is at an older
version.

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

Title:
  Support Private PPAs

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Bionic:
  In Progress
Status in software-properties source package in Cosmic:
  In Progress
Status in software-properties source package in Disco:
  In Progress
Status in software-properties source package in Eoan:
  In Progress

Bug description:
  Software properties add-apt-repository currently does not support
  adding private PPAs.

  software-properties should connect to the API and observe that it gets
  permission denied trying to read the ppa. Then it can reconnect to the
  API asking for authentication, which will open a browser window where
  you can do the openid ritual. Then using that token it ought to be
  possible for it to get the password etc.

  
  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.4

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

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

[Touch-packages] [Bug 1831221] Re: do-release-upgrade fails due to package libpam0g:amd64 1.1.8-3.2ubuntu2.1

[Drew Peterson]

Ah, that was the piece I was missing. Somehow after adding the debian-
installer repo in order to play with d-i creation, either I accidentally
installed cdebconf-udeb, or some other package took it on as a
dependency and I didn't even notice it (for a few years I might add).

I'm honestly surprised this hadn't caused issues before. It certainly
wreaked havoc on my system during this attempted upgrade. I was
eventually able to brute-force the removal of cdebconf and reconfigure
debconf and fix my broken system.

This is resolved, and was not an issue with libpam but rather my own
misfortune and cdebconf being _almost good enough_ to fool me.

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

Title:
  do-release-upgrade fails due to package libpam0g:amd64
  1.1.8-3.2ubuntu2.1

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  While performing a release upgrade from 14.04 to 16.04, the do-
  release-upgrade process crashes, apparently due to a failure
  installing or upgrading the package libpam0g:amd64 1.1.8-3.2ubuntu2.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam0g:amd64 1.1.8-3.2ubuntu2.1
  ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-165-generic x86_64
  NonfreeKernelModules: rr232x
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Fri May 31 04:35:26 2019
  DuplicateSignature: package:libpam0g:amd64:1.1.8-3.2ubuntu2.1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: pam
  Title: package libpam0g:amd64 1.1.8-3.2ubuntu2.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-05-31 (0 days ago)

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

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