[Touch-packages] [Bug 1853412] [NEW] Xorg freeze

2019-11-20 Thread Yanike
Public bug reported:

This happens when I use fractional scaling. At 100%, my HP 840 G3 runs
smooth and fast. With fractional scaling at 125%, there is the
following: visual tears when moving videos while playing; Ubuntu
operates slow with system apps and 3rd party apps; system hangs and
crashes; and more.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 21 01:03:54 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
InstallationDate: Installed on 2019-08-22 (90 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: HP HP EliteBook 840 G3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=63069e05-3459-49f5-9de1-e6594c7cce44 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2016
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.13
dmi.board.name: 8079
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.74
dmi.chassis.asset.tag: 5CG7065GM1
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.74:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 840 G3
dmi.product.sku: V1H24UT#ABA
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan false-gpu-hang freeze third-party-packages ubuntu

** Description changed:

  This happens when I use fractional scaling. At 100%, my HP 840 G3 runs
- smooth and fast. With fractional scaling, there is the following: visual
- tears when moving videos while playing; Ubuntu operates slow with system
- apps and 3rd party apps; system hangs and crashes; and more.
+ smooth and fast. With fractional scaling at 125%, there is the
+ following: visual tears when moving videos while playing; Ubuntu
+ operates slow with system apps and 3rd party apps; system hangs and
+ crashes; and more.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 21 01:03:54 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
+  Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
  InstallationDate: Installed on 2019-08-22 (90 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=63069e05-3459-49f5-9de1-e6594c7cce44 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1848784] Re: Crash in Qt 5.12.2

2019-11-20 Thread Alex Murray
Removing the bionic task since the version in bionic is not affected (it
doesn't contain the original vulnerability).

** No longer affects: qtbase-opensource-src (Ubuntu Bionic)

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Disco:
  New
Status in qtbase-opensource-src source package in Eoan:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5

2019-11-20 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted python3.7 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/python3.7/3.7.5-2~19.10 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-eoan
** Tags added: verification-needed verification-needed-eoan

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

Title:
  SRU: Update Python interpreter to 3.6.9 and 3.7.5

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Fix Released
Status in python3-defaults source package in Bionic:
  New
Status in python3-stdlib-extensions source package in Bionic:
  Fix Released
Status in python3.6 source package in Bionic:
  Fix Committed
Status in python3.7 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Disco:
  New
Status in python3-stdlib-extensions source package in Disco:
  Fix Released
Status in python3.7 source package in Disco:
  New
Status in python3-defaults source package in Eoan:
  New
Status in python3-stdlib-extensions source package in Eoan:
  Fix Released
Status in python3.7 source package in Eoan:
  Fix Committed

Bug description:
  Update Python interpreter to 3.6.9 and 3.7.5.  As done with earlier
  subminor upstream releases (LP: #1822993).

  SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the
  3.6.9 release.

  python3-stdlib-extensions also updates the modules to the 3.6.9
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions. The test suite passes in the autopkg tests. The new
  packages don't cause regressions in a test rebuild of the main
  component.

  
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-bionic.html
  
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-tst-bionic.html

  The test rebuilds are finished, and don't show any regressions for the
  main component.

  Regression Potential: Python 3.7 isn't used by default, so we don't have many 
default users.
  Regression Potential: Python 3.6 could see some regressions, although we are 
trying to minimize the risk by doing the test rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+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 1853242] Re: Regression in Eoan: cannot print to smb connected printer

2019-11-20 Thread Sergio Callegari
Actually not a bug, for sure not the one indicated for Fedora.
Just a very poor interaction of the Kyocera DEB package with the Disco->Eoan 
upgrade.

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

** Changed in: samba (Ubuntu)
   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/1853242

Title:
  Regression in Eoan: cannot print to smb connected printer

Status in cups package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Invalid

Bug description:
  After upgrade from disco to eoan, notwithstanding the fact that 
/etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb 
connected printer provided by my Institution.
  The connection uses authentication and username, password are present in the 
smb url in the printers.conf file.

  May be the same regression as in Fedora 30
  https://bugzilla.redhat.com/show_bug.cgi?id=1706090

  Issue prevents upgrading to eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853242/+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 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report

2019-11-20 Thread El jinete sin cabeza
** Tags added: focal

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@168:collect_info:process_report

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Eoan:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848064/+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 1852772] Re: test_updates_interval fails on focal

2019-11-20 Thread Corey Bryant
My proposed fix for this is:

diff --git a/softwareproperties/dbus/SoftwarePropertiesDBus.py 
b/softwareproperties/dbus/SoftwarePropertiesDBus.py
index c22f43b..7683a1a 100644
--- a/softwareproperties/dbus/SoftwarePropertiesDBus.py
+++ b/softwareproperties/dbus/SoftwarePropertiesDBus.py
@@ -266,7 +266,7 @@ class SoftwarePropertiesDBus(dbus.service.Object, 
SoftwareProperties):
 def SetUpdateInterval(self, days, sender=None, conn=None):
 self._check_policykit_privilege(
 sender, conn, "com.ubuntu.softwareproperties.applychanges")
-self.set_update_interval(days)
+self.set_update_interval(int(days))

I'd like to get a +1 before uploading that though.

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

Title:
  test_updates_interval fails on focal

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  ==

  FAIL: test_updates_interval (tests.test_dbus.TestDBus)

  --

  Traceback (most recent call last):

File "/build/software-properties-0.98.6/tests/test_dbus.py", line 332, in 
test_updates_interval 
  self.assertTrue('APT::Periodic::Update-Package-Lists "1";' in config) 

  
  AssertionError: False is not true   

  Looking closer, while in the SetUpdateInterval() method in
  softwareproperties/dbus/SoftwarePropertiesDBus.py, days is of
  dbus.Int32 type. A simple print output shows:

  days=dbus.Int32(1)

  D-Bus is statically typed, unlike python. More details at:
  https://dbus.freedesktop.org/doc/dbus-python/tutorial.html#data-types

  I think once we're in the dbus method (SetUpdateInterval() method in
  softwareproperties/dbus/SoftwarePropertiesDBus.py) we can convert the
  dbus.Int32 to an int.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+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 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

2019-11-20 Thread Marcin P
Guys, maybe I can somehow help you with this issue?

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc.
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852071/+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 1853242] Re: Regression in Eoan: cannot print to smb connected printer

2019-11-20 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

apport-collect 1853242

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


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

** Tags added: eoan

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

Title:
  Regression in Eoan: cannot print to smb connected printer

Status in cups package in Ubuntu:
  New

Bug description:
  After upgrade from disco to eoan, notwithstanding the fact that 
/etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb 
connected printer provided by my Institution.
  The connection uses authentication and username, password are present in the 
smb url in the printers.conf file.

  May be the same regression as in Fedora 30
  https://bugzilla.redhat.com/show_bug.cgi?id=1706090

  Issue prevents upgrading to eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853242/+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 1853242] Re: Regression in Eoan: cannot print to smb connected printer

2019-11-20 Thread Sergio Callegari
Running cups in debug mode (cupsctl --debug-logging) in the logs I see a
couple of interesting lines:

[Job 1008] PID 2888 (/usr/lib/cups/backend/smb) stopped with status 2.
...
[Job 1008] Unable to connect to CIFS host: NT_STATUS_INVALID_ACCOUNT_NAME
...
[Job 1008] Backend returned status 2 (authentication required)

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

Title:
  Regression in Eoan: cannot print to smb connected printer

Status in cups package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New

Bug description:
  After upgrade from disco to eoan, notwithstanding the fact that 
/etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb 
connected printer provided by my Institution.
  The connection uses authentication and username, password are present in the 
smb url in the printers.conf file.

  May be the same regression as in Fedora 30
  https://bugzilla.redhat.com/show_bug.cgi?id=1706090

  Issue prevents upgrading to eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853242/+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 1853266] [NEW] xserver segfaults on GL_OUT_OF_MEMORY in libglamoregl

2019-11-20 Thread Michael Freitag
Public bug reported:

Recently, my the xserver on my system has started randomly crashing due
to a segmentation fault. As far as I can tell, this segmentation fault
occurs as a result of libglamoregl encountering a GL_OUT_OF_MEMORY error
(see attached Xorg.log). I have had a hard time reproducing this bug
reliably, but it mostly happens when I have been using Inkscape for a
while.

This appears to be the same bug that has been reported here

https://bugs.freedesktop.org/show_bug.cgi?id=110500
https://bugs.freedesktop.org/show_bug.cgi?id=110714

In those bug reports, the usual recommendation is to switch from the
-modesetting video driver to the -nouveau video driver. By default,
Ubuntu is not configured in this way, so this bug probably needs to be
addressed in some other way.

My graphics card is listed as follows:

 *-display 
   description: VGA compatible controller
   product: GK208B [GeForce GT 710]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:65:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
   configuration: driver=nouveau latency=0
   resources: irq:69 memory:d700-d7ff memory:c800-cfff 
memory:d000-d1ff ioport:b000(size=128) memory:d800-d807

Please let me know if you need any additional information.

More information:

Release of Ubuntu: 19.04

Installed package versions:
xserver-xorg-video-nouveau/disco,now 1:1.0.16-1 amd64 [installed]
xserver-xorg-core/disco,now 2:1.20.4-1ubuntu3 amd64 [installed]
xserver-xorg/disco,now 1:7.7+19ubuntu12 amd64 [installed]
inkscape/disco,now 0.92.4-3 amd64 [installed]

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

** Attachment added: "Xorg log"
   
https://bugs.launchpad.net/bugs/1853266/+attachment/5306607/+files/Xorg.0.log.old

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

Title:
  xserver segfaults on GL_OUT_OF_MEMORY in libglamoregl

Status in xorg package in Ubuntu:
  New

Bug description:
  Recently, my the xserver on my system has started randomly crashing
  due to a segmentation fault. As far as I can tell, this segmentation
  fault occurs as a result of libglamoregl encountering a
  GL_OUT_OF_MEMORY error (see attached Xorg.log). I have had a hard time
  reproducing this bug reliably, but it mostly happens when I have been
  using Inkscape for a while.

  This appears to be the same bug that has been reported here

  https://bugs.freedesktop.org/show_bug.cgi?id=110500
  https://bugs.freedesktop.org/show_bug.cgi?id=110714

  In those bug reports, the usual recommendation is to switch from the
  -modesetting video driver to the -nouveau video driver. By default,
  Ubuntu is not configured in this way, so this bug probably needs to be
  addressed in some other way.

  My graphics card is listed as follows:

   *-display 
 description: VGA compatible controller
 product: GK208B [GeForce GT 710]
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:65:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
 configuration: driver=nouveau latency=0
 resources: irq:69 memory:d700-d7ff memory:c800-cfff 
memory:d000-d1ff ioport:b000(size=128) memory:d800-d807

  Please let me know if you need any additional information.

  More information:

  Release of Ubuntu: 19.04

  Installed package versions:
  xserver-xorg-video-nouveau/disco,now 1:1.0.16-1 amd64 [installed]
  xserver-xorg-core/disco,now 2:1.20.4-1ubuntu3 amd64 [installed]
  xserver-xorg/disco,now 1:7.7+19ubuntu12 amd64 [installed]
  inkscape/disco,now 0.92.4-3 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853266/+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 1853242] [NEW] Regression in Eoan: cannot print to smb connected printer

2019-11-20 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After upgrade from disco to eoan, notwithstanding the fact that 
/etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb 
connected printer provided by my Institution.
The connection uses authentication and username, password are present in the 
smb url in the printers.conf file.

May be the same regression as in Fedora 30
https://bugzilla.redhat.com/show_bug.cgi?id=1706090

Issue prevents upgrading to eoan.

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


** Tags: bot-comment
-- 
Regression in Eoan: cannot print to smb connected printer
https://bugs.launchpad.net/bugs/1853242
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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


[Touch-packages] [Bug 1853242] Re: Regression in Eoan: cannot print to smb connected printer

2019-11-20 Thread Sergio Callegari
Sorry, could not report the issue from the machine where I have first
experienced the bug. Also marked samba as a possible source for the
issue (from the fedora report). If the issue is the same, it seems fixed
in Fedora.

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

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

Title:
  Regression in Eoan: cannot print to smb connected printer

Status in cups package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New

Bug description:
  After upgrade from disco to eoan, notwithstanding the fact that 
/etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb 
connected printer provided by my Institution.
  The connection uses authentication and username, password are present in the 
smb url in the printers.conf file.

  May be the same regression as in Fedora 30
  https://bugzilla.redhat.com/show_bug.cgi?id=1706090

  Issue prevents upgrading to eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853242/+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 1853289] [NEW] recoll GUI crashes when search is invoked

2019-11-20 Thread Rosika Schreck
Public bug reported:

installed package: libqt5widgets5:amd64 5.9.5+dfsg-0ubuntu2.3
on: Linux/Lubuntu 18.04.3 LTS, 64 bit

Recoll GUI crashes when typing in search-word, but not always.

Example from log:

kernel: [ 5684.473141] recoll[7859]: segfault at 8 ip 7f1959d89174
sp 7fffee4fe000 error 4 in
libQt5Widgets.so.5.9.5[7f19598e6000+616000]

Any help appreciated.

Geetings.
Rosika

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

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

Title:
  recoll GUI crashes when search is invoked

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  installed package: libqt5widgets5:amd64 5.9.5+dfsg-0ubuntu2.3
  on: Linux/Lubuntu 18.04.3 LTS, 64 bit

  Recoll GUI crashes when typing in search-word, but not always.

  Example from log:

  kernel: [ 5684.473141] recoll[7859]: segfault at 8 ip 7f1959d89174
  sp 7fffee4fe000 error 4 in
  libQt5Widgets.so.5.9.5[7f19598e6000+616000]

  Any help appreciated.

  Geetings.
  Rosika

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1853289/+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 1779767] Re: Default cron PATH does not include /snap/bin

2019-11-20 Thread Brian Murray
*** This bug is a duplicate of bug 1771858 ***
https://bugs.launchpad.net/bugs/1771858

** This bug has been marked a duplicate of bug 1771858
   /snap/bin not in default PATH for units, snapd should ship 
system-environment-generators to inject /snap/bin into $PATH

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

Title:
  Default cron PATH does not include /snap/bin

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  I recently changed from a .deb install of LXD to a snap, and was
  surprised that one of my crontab scripts stopped working.

  I see that $PATH in a cron script only contains "/usr/bin:/bin",
  whereas my default shell also includes "/snap/bin".

  It seems to me that for the best user experience with snaps,
  "/snap/bin" should be part of the default $PATH in cron.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  2 14:30:06 2018
  InstallationDate: Installed on 2017-12-20 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779767/+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 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor

2019-11-20 Thread Paul Mundt
I'm also in a similar situation - cursor disappeared after upgrade, and
doesn't show up in any Xorg sessions (whether invoked directly, or
through different DMs), and regardless of cursor theme. I'm also using a
basic graphics card - the on-board Matrox G200 on a Dell server machine.
Mouse continues to work fine otherwise, both in X and in the console
(via GPM).

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 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: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340/+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 1851056] Re: "Proceeding WITHOUT firewalling in effect!" warning

2019-11-20 Thread klogg
That's interesting. With secure boot and lockdown in place there is no
bpf, and without bpf systemd services' acls dont work. Not critical but
essentially totally broken :D

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

Title:
  "Proceeding WITHOUT firewalling in effect!" warning

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  Hello everyone,

  I noticed a strange systemd warning in my kernel log about "Proceeding
  WITHOUT firewalling in effect!" There is an older Debian bug mention
  about this same issue and it is said there that it was fixed last
  year: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872560

  Release: Ubuntu 19.10, fresh install, latest updates with updates-testing 
repository enabled
  Systemd-package version: 242-7ubuntu3
  Kernel: Linux 5.3.0-21-generic

  Here is the relevant warning information via running sudo dmesg after
  boot:

  [2.096064] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man 
kernel_lockdown.7
  [2.101034] Lockdown: systemd: BPF is restricted; see man kernel_lockdown.7
  [2.136885] systemd[1]: File 
/lib/systemd/system/systemd-journald.service:12 configures an IP firewall 
(IPAddressDeny=any), but the local system does not support BPF/cgroup based 
firewalling.
  [2.142209] systemd[1]: Proceeding WITHOUT firewalling in effect! (This 
warning is only shown for the first loaded unit using IP firewalling.)
  [2.158190] systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= 
references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update 
the unit file accordingly.
  [2.197029] systemd[1]: Listening on Journal Socket.
  [2.203708] systemd[1]: Starting Create list of required static device 
nodes for the current kernel...
  [2.243900] bpfilter: Loaded bpfilter_umh pid 420
  #Continues normally from here without anything that seems odd

  The included attachment .txt has more information. From what I've read
  online from various bug trackers from other distributions this should
  be related to a missing kernel option (CONFIG_BPF_SYSCALL=y), but this
  option seems to be enabled:

  # Output after running in commandline: grep BPF /boot/config-`uname -r`
  # Kernel settings seem to be correct?
  CONFIG_CGROUP_BPF=y
  CONFIG_BPF=y
  CONFIG_BPF_SYSCALL=y
  CONFIG_BPF_JIT_ALWAYS_ON=y
  CONFIG_IPV6_SEG6_BPF=y
  CONFIG_NETFILTER_XT_MATCH_BPF=m
  CONFIG_BPFILTER=y
  CONFIG_BPFILTER_UMH=m
  CONFIG_NET_CLS_BPF=m
  CONFIG_NET_ACT_BPF=m
  CONFIG_BPF_JIT=y
  CONFIG_BPF_STREAM_PARSER=y
  CONFIG_LWTUNNEL_BPF=y
  CONFIG_HAVE_EBPF_JIT=y
  CONFIG_BPF_EVENTS=y
  CONFIG_BPF_KPROBE_OVERRIDE=y
  CONFIG_TEST_BPF=m

  Also my friend just installed 19.10 on his machine and is seeing the
  same warning, but I haven't found anyone else mentioning this issue at
  least on the latest Ubuntu 19.10. The same warning message is
  appearing if I run Ubuntu 19.10 in live mode from the USB stick.

  What I expected to happen: no such error (it doesn't appear on Fedora
  or openSUSE Tumbleweed that I've recently had installed on my other
  SSD)

  What happened instead: error appears during every boot sequence

  It's also worth stressing that the firewall is functioning just fine
  (using standard ufw) despite the error, so I'm guessing this is a
  harmless warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1851056/+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 1851542] Re: autopkgtest fails due to aspell SRU

2019-11-20 Thread dann frazier
While the autopkgtest for eoan still fails, it now fails with 2 errors
instead of 3. I confirmed from the logs[*] that the no-longer-failing
test is the one this upload addressed.

[*] Compare the "2019-11-14 11:09:47 UTC" vs. "2019-11-19 19:32:01 UTC" logs at:
https://autopkgtest.ubuntu.com/packages/apport/eoan/amd64



** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  autopkgtest fails due to aspell SRU

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Disco:
  Fix Committed
Status in apport source package in Eoan:
  Fix Committed
Status in apport source package in Focal:
  Fix Released

Bug description:
  [Impact]
  A new autopkgtest test regression began appearing after (and due to) an 
aspell SRU.

  ==
  FAIL: test_install_packages_versioned (__main__.T)
  install_packages() with versions and with cache
  --
  Traceback (most recent call last):
File "./test_backend_apt_dpkg.py", line 557, in 
test_install_packages_versioned
  self.assertIn(result, 'aspell-doc version 1.1 required, but 
0.60.7~20110707-3build1 is available\n')
  AssertionError: 'aspell-doc version 1.1 required, but 
0.60.7~20110707-3ubuntu0.1 is available\n' not found in 'aspell-doc version 1.1 
required, but 0.60.7~20110707-3build1 is available\n'

  --
  Ran 37 tests in 191.123s

  FAILED (failures=1)

  [Test Case]
  ## From within autopkgtest source package, with autopkgtest deps installed
  ## This is a slightly modified version if debian/tests/upstream-system

  # do not run in the source tree, as we want to check the system-installed
  # apport
  TESTDIR=${ADTTMP:-/tmp}/apport-tests
  mkdir -p $TESTDIR
  cp test/test_* test/run "$TESTDIR"
  cd "$TESTDIR"

  # clean up old crash reports
  rm -rf /var/crash/*

  export GNUPGHOME=$TESTDIR/gnupg
  mkdir -m 700 $GNUPGHOME

  ./run backend_apt_dpkg

  [Fix]
  
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717

  [Regression Risk]
  Code is restricted to a test that is only ran via autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851542/+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 932133] Re: upowerd crash when plugging in iPhone

2019-11-20 Thread Erik Auerswald
The problem has not occured for me on Ubuntu 18.04 yet, it might be
fixed in the latest LTS release.

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

Title:
  upowerd crash when plugging in iPhone

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  upowerd crashed when I plugged in my iPhone 3GS. This is reproducible
  in 12.04 on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: upower 0.9.15-1
  ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
  Uname: Linux 3.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Tue Feb 14 10:43:29 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to precise on 2012-02-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/932133/+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 1850608] Re: Segfaults trying to send crash report

2019-11-20 Thread Tiago Stürmer Daitx
** Information type changed from Private Security to Public

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

Title:
  Segfaults trying to send crash report

Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  After this morning's upgrade to "whoopsie 0.2.62ubuntu0.2"
  plus "libwhoopsie0 0.2.62ubuntu0.2"(fix to bug #1830865),
  whoopsie repeatedly crashes with a segfault (in what seems to be libc?).
  An excerpt from /var/log/syslog (slightly redacted):

  Oct 30 08:33:06 [REDACTED] systemd[1]: Started crash report submission daemon.
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Using lock path: 
/var/lock/whoopsie/lock
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] The default IPv4 route 
is: /org/freedesktop/NetworkManager/ActiveConnection/1
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Found usable 
connection: /org/freedesktop/NetworkManager/ActiveConnection/1
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Parsing 
/var/crash/_usr_bin_kdeinit5.1000.crash.
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Uploading 
/var/crash/_usr_bin_kdeinit5.1000.crash.
  Oct 30 08:33:10 [REDACTED] kernel: [ 2129.099314] whoopsie[22414]: segfault 
at 7f4f878a4000 ip 7f4f866fe5e1 sp 7ffe348bed78 error 4 in 
libc-2.27.so[7f4f86591000+1e7000]
  Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Main process exited, 
code=dumped, status=11/SEGV
  Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Failed with result 
'core-dump'.
  Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Service hold-off 
time over, scheduling restart.
  Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Scheduled restart 
job, restart counter is at 133.
  Oct 30 08:33:11 [REDACTED] systemd[1]: Stopped crash report submission daemon.

  The above sequence of logged events repeats endlessly,
  with only(?) the times and whoospie PID changing.

  The problem can be (temporarily) stopped by `service whoopsie stop';
  using `service whoopsie start' resumes the above behaviour.
  Rebooting does not "fix".

  Manually running whoopsie shows the same behaviour:

  $ sudo /bin/sh -c 'export CRASH_DB_URL=https://daisy.ubuntu.com; exec 
whoopsie -f'
  [09:45:14] Using lock path: /var/lock/whoopsie/lock
  [09:45:14] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
  [09:45:14] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
  [09:45:14] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
  [09:45:14] Parsing /var/crash/_usr_bin_kdeinit5.1000.crash.
  [09:45:14] Uploading /var/crash/_usr_bin_kdeinit5.1000.crash.
  Segmentation fault
  $ 
  $ ls -la /var/crash/
  total 33340
  drwxrwsrwt  2 root whoopsie 4096 Oct 30 08:52 .
  drwxr-xr-x 16 root root 4096 Sep 14  2018 ..
  -rw-r--r--  1 root whoopsie  281 Oct 30 08:55 kexec_cmd
  -rwxrwxrwx  1 root whoopsie0 Oct 30 08:22 .lock
  -rw-r-  1 blf  whoopsie 17624101 Oct 30 08:53 
_usr_bin_kdeinit5.1000.crash
  -rw-rw-r--  1 blf  whoopsie0 Oct 30 08:22 
_usr_bin_kdeinit5.1000.upload
  -rw-r-  1 root whoopsie   398157 Oct 24 11:49 _usr_bin_sddm.0.crash
  -rw-r-  1 whoopsie whoopsie 15996866 Oct 30 08:22 
_usr_bin_whoopsie.108.crash
  -rw-r-  1 root whoopsie99379 Oct 22 15:07 _usr_sbin_inetd.0.crash
  $ 

  Because (as far as I know) the various `.crash' files MAY contain sensitive 
information,
  I have not attached them to this (public) bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: whoopsie 0.2.62ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  Date: Wed Oct 30 09:28:01 2019
  InstallationDate: Installed on 2016-10-07 (1118 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (438 days ago)

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

2019-11-20 Thread pfpschneider
I have the same problem.
If someone tells me how to elicit the correct settings under Windows I can get 
them and try them out in Linux.
If someone tells me what possible settings might work under Linux (or tells me 
how to figure out what settings might work) I can try to find the right 
settings.

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1845797/+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 1853378] [NEW] Xorg freeze

2019-11-20 Thread njklim
Public bug reported:

Currently using a Dell Inspiron 3835 with a ryzen 2500u with 8gb of ram
on a pcie nvme ssd. PC randomly freezes at times. This actually occurs
on asus x505za also running 2500u.

I checked the log files and there was this error.
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654

I think it may be a problem with gnome since I was running lubuntu
before and there's no hang whatsoever when using that.

Ubuntu 18.04.3 LTS
Release 18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.3.12-050312-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 21 07:04:57 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
   Subsystem: Dell Vega [Radeon Vega 8 Mobile] [1028:08d7]
InstallationDate: Installed on 2019-11-19 (1 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Dell Inc. Inspiron 3585
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.12-050312-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash idle=nomwait iommu=soft 
pci=nomsi vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.asset.tag: not specified
dmi.board.name: 0TY9XW
dmi.board.vendor: Dell Inc.
dmi.board.version: X01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.4.0
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/29/2019:svnDellInc.:pnInspiron3585:pvr1.4.0:rvnDellInc.:rn0TY9XW:rvrX01:cvnDellInc.:ct10:cvr1.4.0:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3585
dmi.product.sku: 08D7
dmi.product.version: 1.4.0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100+git1911150630.a39c34~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0~git1911201930.bcfc9c~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0~git1911201930.bcfc9c~oibaf~b
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Currently using a Dell Inspiron 3835 with a ryzen 2500u with 8gb of
  ram on a pcie nvme ssd. PC randomly freezes at times. This actually
  occurs on asus x505za also running 2500u.

  I checked the log files and there was this error.
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654

  I think it may be a problem with gnome since I was running lubuntu
  before and there's no hang whatsoever when using that.

  Ubuntu 18.04.3 LTS
  Release 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 21 07:04:57 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] 

[Touch-packages] [Bug 1853383] [NEW] autopkgtest regression in test_add_proc_info

2019-11-20 Thread dann frazier
Public bug reported:

The security uploads for apport (2.20.11-0ubuntu8.2 for eoan,
2.20.10-0ubuntu27.2 for disco, and 2.20.9-0ubuntu7.8 for bionic - and
maybe those for older releases as well) have caused the
test_add_proc_info test to start failing[1]. The pattern changed after
the subsequent uploads to fix a regression, but it still fails[2].

[1]
==
ERROR: test_add_proc_info (__main__.T)
add_proc_info().
--
Traceback (most recent call last):
  File "./test_report.py", line 100, in test_add_proc_info
pr.add_proc_info(extraenv=['PWD'])
  File "/usr/lib/python3/dist-packages/apport/report.py", line 550, in 
add_proc_info
self.add_proc_environ(pid, extraenv)
  File "/usr/lib/python3/dist-packages/apport/report.py", line 619, in 
add_proc_environ
env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
  File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in _read_file
with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
TypeError: argument should be integer or None, not list

[2]
==
ERROR: test_add_proc_info (__main__.T)
add_proc_info().
--
Traceback (most recent call last):
  File "./test_report.py", line 210, in test_add_proc_info
self.assertRaises(ValueError, pr.add_proc_info, p.pid)
  File "/usr/lib/python3.7/unittest/case.py", line 743, in assertRaises
return context.handle('assertRaises', args, kwargs)
  File "/usr/lib/python3.7/unittest/case.py", line 178, in handle
callable_obj(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/apport/report.py", line 544, in 
add_proc_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH | 
os.O_DIRECTORY)
FileNotFoundError: [Errno 2] No such file or directory: '/proc/1899'

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

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

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

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

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

** Also affects: apport (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

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

** Also affects: apport (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Description changed:

  The security uploads for apport (2.20.11-0ubuntu8.2 for eoan,
  2.20.10-0ubuntu27.2 for disco, and 2.20.9-0ubuntu7.8 for bionic - and
  maybe those for older releases as well) have caused the
  test_add_proc_info test to start failing:
  
  ==
  ERROR: test_add_proc_info (__main__.T)
  add_proc_info().
  --
  Traceback (most recent call last):
-   File "./test_report.py", line 100, in test_add_proc_info
- pr.add_proc_info(extraenv=['PWD'])
-   File "/usr/lib/python3/dist-packages/apport/report.py", line 550, in 
add_proc_info
- self.add_proc_environ(pid, extraenv)
-   File "/usr/lib/python3/dist-packages/apport/report.py", line 619, in 
add_proc_environ
- env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
-   File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
- with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
-   File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
- with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
+   File "./test_report.py", line 100, in test_add_proc_info
+ pr.add_proc_info(extraenv=['PWD'])
+   File "/usr/lib/python3/dist-packages/apport/report.py", line 550, in 
add_proc_info
+ self.add_proc_environ(pid, extraenv)
+   File "/usr/lib/python3/dist-packages/apport/report.py", line 619, in 
add_proc_environ
+ env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
+   File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
+ with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
+   File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
+ with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  TypeError: argument should be 

[Touch-packages] [Bug 1806263] Re: MariaDB 10.1 server won't start when MySQL 5.7 server has been previously installed

2019-11-20 Thread F. Alejandro Osso
Just to thank you all.  I just hit this problem, solved it and in the
process learned something about apparmor.

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

Title:
  MariaDB 10.1 server won't start when MySQL 5.7 server has been
  previously installed

Status in apparmor package in Ubuntu:
  Won't Fix
Status in mariadb-10.1 package in Ubuntu:
  Confirmed
Status in mysql-5.7 package in Ubuntu:
  Won't Fix

Bug description:
  If you purge MySQL 5.7 server, then install MariaDB 10.1, that last
  won't start due to wrong AppArmor profile.

  CURRENT RESULT ON mariadb-server-10.1 package installation

  ...
  Job for mariadb.service failed because a timeout was exceeded.
  See "systemctl status mariadb.service" and "journalctl -xe" for details.
  ...

  # LANG=C systemctl status mariadb

  * mariadb.service - MariaDB 10.1.34 database server
 Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Sun 2018-12-02 17:26:09 UTC; 59s ago
   Docs: man:mysqld(8)
 https://mariadb.com/kb/en/library/systemd/
   Main PID: 23245 (code=exited, status=0/SUCCESS)

  Dec 02 17:24:37 bionic systemd[1]: Starting MariaDB 10.1.34 database server...
  Dec 02 17:24:37 bionic mysqld[23245]: 2018-12-02 17:24:37 139820621216896 
[Note] /usr/sbin/mysqld (mysqld 10.1.34-MariaDB-0ubuntu0.18.04.1) starting as 
process 23245 ...
  Dec 02 17:26:07 bionic systemd[1]: mariadb.service: Start operation timed 
out. Terminating.
  Dec 02 17:26:09 bionic systemd[1]: mariadb.service: Failed with result 
'timeout'.
  Dec 02 17:26:09 bionic systemd[1]: Failed to start MariaDB 10.1.34 database 
server.

  
  EXPECTED RESULT

  MariaDB 10.1 server starting as expected.

  HOWTO REPRODUCE

  apt-get install mysql-server-5.7 mysql-client-5.7
  apt-get purge mysql-server-5.7 mysql-client-5.7
  apt-get install mariadb-server-10.1 mariadb-client-10.1

  DISCUSSION

  The mysql-server-5.7 package install an
  /etc/apparmor.d/usr.sbin.mysqld APPARMOR(7) profile:

  # dpkg -S /etc/apparmor.d/usr.sbin.mysqld 
  mysql-server-5.7: /etc/apparmor.d/usr.sbin.mysqld

  When purging the mysql-server-5.7 server package get purged, the
  /etc/apparmor.d/usr.sbin.mysqld profile is also removed but, it is
  still loaded:

  # aa-status | grep 'mysqld'
 /usr/sbin/mysqld

  This lead to MariaDB 1.0 server not being able to start due to MySQL
  5.7 APPARMOR(7) profile that is still loaded.

  Furthermore, the mariadb-server-10.1 also comes with an APPARMOR(7)
  profile which as per it header comments is "intensionally empty to
  disable apparmor by default for newer versions of MariaDB".

  This is a big mistake as such a profile is simply wrong in regard of
  APPARMOR_PARSER(8) and as such, won't be unloaded:

  # apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
  # aa-status | grep 'mysqld'
 /usr/sbin/mysqld

  while:

  # echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
  # apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
  Removal succeeded for "/usr/sbin/mysqld".
  # aa-status | grep 'mysqld'

  FIX PROPOSAL

  1. When mysql-server-5.7 package is being removed/purged, the APPARMOR(7) 
profile should be unloaded and removed ranther than be simply removed.
  2. The profile provided by the mariadb-server-10.1 package should have 
correct syntax in regard of APPARMOR_PARSER(8)
  3. The mariadb-server-10.1 package postinst/postrm maintainer scripts should 
handle apparmor profile (load/unload)

  Env Ubuntu Bionic Beaver (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1806263/+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 1853378] Re: Xorg freeze

2019-11-20 Thread njklim
Here's a log file for the Asus X505ZA.

This is the error
7:55:52 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process chrome pid 2660 thread chrome:cs0 pid 2723
 7:55:52 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process chrome pid 2660 thread chrome:cs0 pid 2723
 7:55:52 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 
timeout, signaled seq=242891, emitted seq=242894
 7:55:42 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process chrome pid 2660 thread chrome:cs0 pid 2723
 7:55:42 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 
timeout, signaled seq=242891, emitted seq=242894
 7:55:32 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process chrome pid 2660 thread chrome:cs0 pid 2723
 7:55:32 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 
timeout, signaled seq=242891, emitted seq=242894
 7:55:22 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process chrome pid 2660 thread chrome:cs0 pid 2723
 7:55:22 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 
timeout, signaled seq=242891, emitted seq=242894
 7:55:11 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process chrome pid 2660 thread chrome:cs0 pid 2723
 7:55:11 AM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 
timeout, signaled seq=242891, emitted seq=242894

** Attachment added: "log messages"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853378/+attachment/5306740/+files/log%20messages

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Currently using a Dell Inspiron 3835 with a ryzen 2500u with 8gb of
  ram on a pcie nvme ssd. PC randomly freezes at times. This actually
  occurs on asus x505za also running 2500u.

  I checked the log files and there was this error.
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654

  I think it may be a problem with gnome since I was running lubuntu
  before and there's no hang whatsoever when using that.

  Ubuntu 18.04.3 LTS
  Release 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 21 07:04:57 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Dell Vega [Radeon Vega 8 Mobile] [1028:08d7]
  InstallationDate: Installed on 2019-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3585
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.12-050312-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash idle=nomwait iommu=soft 
pci=nomsi vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.asset.tag: not specified
  dmi.board.name: 0TY9XW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.4.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/29/2019:svnDellInc.:pnInspiron3585:pvr1.4.0:rvnDellInc.:rn0TY9XW:rvrX01:cvnDellInc.:ct10:cvr1.4.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3585
  dmi.product.sku: 08D7
  dmi.product.version: 1.4.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100+git1911150630.a39c34~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0~git1911201930.bcfc9c~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0~git1911201930.bcfc9c~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Touch-packages] [Bug 1851542] Re: autopkgtest fails due to aspell SRU

2019-11-20 Thread dann frazier
The autopkgtests for bionic and disco also continue to fail w/ the
upload in -proposed. However, as was the case for eoan, the failure that
the uploads for this bug targeted has gone away. The remaining failures
appear to be a regression(s) introduced by previous security uploads.
I've reported bug 1853383 for the one I can readily reproduce.

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

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

Title:
  autopkgtest fails due to aspell SRU

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Disco:
  Fix Committed
Status in apport source package in Eoan:
  Fix Committed
Status in apport source package in Focal:
  Fix Released

Bug description:
  [Impact]
  A new autopkgtest test regression began appearing after (and due to) an 
aspell SRU.

  ==
  FAIL: test_install_packages_versioned (__main__.T)
  install_packages() with versions and with cache
  --
  Traceback (most recent call last):
File "./test_backend_apt_dpkg.py", line 557, in 
test_install_packages_versioned
  self.assertIn(result, 'aspell-doc version 1.1 required, but 
0.60.7~20110707-3build1 is available\n')
  AssertionError: 'aspell-doc version 1.1 required, but 
0.60.7~20110707-3ubuntu0.1 is available\n' not found in 'aspell-doc version 1.1 
required, but 0.60.7~20110707-3build1 is available\n'

  --
  Ran 37 tests in 191.123s

  FAILED (failures=1)

  [Test Case]
  ## From within autopkgtest source package, with autopkgtest deps installed
  ## This is a slightly modified version if debian/tests/upstream-system

  # do not run in the source tree, as we want to check the system-installed
  # apport
  TESTDIR=${ADTTMP:-/tmp}/apport-tests
  mkdir -p $TESTDIR
  cp test/test_* test/run "$TESTDIR"
  cd "$TESTDIR"

  # clean up old crash reports
  rm -rf /var/crash/*

  export GNUPGHOME=$TESTDIR/gnupg
  mkdir -m 700 $GNUPGHOME

  ./run backend_apt_dpkg

  [Fix]
  
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717

  [Regression Risk]
  Code is restricted to a test that is only ran via autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851542/+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 1841654] Re: Consider replacing mawk with gawk in main

2019-11-20 Thread Erik Auerswald
I would prefer to have a current mawk in Ubuntu, but if that does not
happen, replacing mawk with gawk would be appreciated.

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

Title:
  Consider replacing mawk with gawk in main

Status in mawk package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
  mawk) in main. There is an awk-symlink to mawk, thus mawk is the
  official awk implementation in Ubuntu.

  == Reasons against keeping mawk ==

  *The mawk package is synced from debian and it is heavily
  undermaintained: Debian (and thus Ubuntu) still ships version
  1.3.3-17, the same version at least since oldoldstable:
  https://packages.debian.org/search?searchon=names=mawk

  *maintainer Thomas E. Dickey (https://invisible-island.net/mawk/)
  called officially out that Debian "neglected" mawk in 2014 ("As noted,
  mawk has been neglected by some packagers (see for example this
  http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk)". And
  Debian (and Ubuntu) still ship the same version five years later

  *Most other distributions ship mawk at least in its last official
  incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
  FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
  NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 but
  updated snapshots are released in regular intervals. The current
  snapshot is from February 2019: https://github.com/ThomasDickey/mawk-
  snapshots/blob/ab13a164013940e90c0b1ad36a039feae06a0b65/CHANGES

  *A planned rewrite mawk2 was planned by original author Mike Brennan
  in 2016 but obviously came to nothing:
  https://github.com/ploxiln/mawk-2/commits/master

  *Thus mawk sits in Ubuntu main in a version published upstream in 2009
  and celebrates its 10th anniversary of negligence. In a state that
  Debian was called out for 5 years ago.

  *This year it is 10 years unmaintained and largely untouched. At the
  end of the next LTS-support-cycle we can celebrate 15 years of not
  supporting it.

  *awk is included in Linux for POSIX standard compliance. Mawk is known
  to be fast and small but it is the implementation that is farthest
  from being POSIX compliant, missing things like named character
  classes like [[:space:]] within its EREs.

  == Reasons for gawk as a replacement ==

  *It is the official GNU awk implementation and known to work well with
  the rest of the GNU userland.

  *It is actively maintained with the last version 5.01 shipping in
  June, 2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).

  *It is mostly compliant with the POSIX standard.

  *Most other distributions ship it as the standard POSIX
  implementation, with a awk symlink. So it had security reviews already
  by Red Hat and others.

  == Possible problems with switching to gawk in time for Ubuntu 20.4 ==

  - It might need to be MIRed by the Ubuntu security team and a review
  might take some time. So I filed this bug early with Eoan not yet out
  of the door.

  - It is much larger than mawk, the Ubuntu package is 1600 kB in size,
  while mawk is only about 190KB. Thus some might want to split out some
  basic functionality to save size. Like what is vim-tiny to vim. To
  start gawk in --traditional or --posix mode and disable the extensions
  at compile time might be a good start to reduce the size. See:
  https://www.gnu.org/software/gawk/manual/html_node/Additional-
  Configuration-Options.html#Additional-Configuration-Options

  =

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mawk 1.3.3-17ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 20:12:11 2019
  Dependencies:
   gcc-9-base 9.1.0-2ubuntu2~19.04
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-2ubuntu2~19.04
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2018-02-23 (550 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: mawk
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often

2019-11-20 Thread Ian
$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10

$ apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:13.0-1ubuntu1

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

Title:
  pulseaudio disables GP107GL output every so often

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrading to 19.10, the sound output on this PC stops.

  Looking at the volume control's 'sound settings', the GP107GL High
  Definition Audio Controller (digital stereo HMDI 2 output) is
  disabled.

  Doing

  pluseaudio -k

  restores it.

  Possibly relevant from syslog:

  Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2
  Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 4
  Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1853374] [NEW] pulseaudio disables GP107GL output every so often

2019-11-20 Thread Ian
Public bug reported:

Since upgrading to 19.10, the sound output on this PC stops.

Looking at the volume control's 'sound settings', the GP107GL High
Definition Audio Controller (digital stereo HMDI 2 output) is disabled.

Doing

pluseaudio -k

restores it.

Possibly relevant from syslog:

Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 3
Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 2
Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 3
Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 4
Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 3
Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 3
Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 2

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

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

Title:
  pulseaudio disables GP107GL output every so often

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrading to 19.10, the sound output on this PC stops.

  Looking at the volume control's 'sound settings', the GP107GL High
  Definition Audio Controller (digital stereo HMDI 2 output) is
  disabled.

  Doing

  pluseaudio -k

  restores it.

  Possibly relevant from syslog:

  Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2
  Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 4
  Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1849859] Re: error when connecting to smb server

2019-11-20 Thread Till Kamppeter
Can this perhaps have to do with this bug in Fedora 30:
https://bugzilla.redhat.com/show_bug.cgi?id=1706090 ?

See also bug 1853242.

** Bug watch added: Red Hat Bugzilla #1706090
   https://bugzilla.redhat.com/show_bug.cgi?id=1706090

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1853393] [NEW] Xorg freeze

2019-11-20 Thread Zaidan Ilmi
Public bug reported:

when using ubuntu it randomly freeze

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 21 09:41:08 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: I don't know
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GV102 [10de:1e07] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3711]
InstallationDate: Installed on 2019-11-19 (1 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Micro-Star International Co., Ltd. MS-7C37
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic 
root=UUID=4ada2956-717e-4d5d-ae06-bd4aad086b48 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.40
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd09/10/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  when using ubuntu it randomly freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 21 09:41:08 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: I don't know
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GV102 [10de:1e07] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3711]
  InstallationDate: Installed on 2019-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7C37
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic 
root=UUID=4ada2956-717e-4d5d-ae06-bd4aad086b48 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 

[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

2019-11-20 Thread Hui Wang
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846148/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

2019-11-20 Thread Teeedubb
Hi,

I am experiencing the same issue with Kodi 18.5 and Xubuntu 19.10 with
similar stack traces to joe-yasi. Is there anyway to install the updated
package via Ubuntu updates?

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in jackd2 package in Ubuntu:
  Confirmed
Status in jackd2 package in Debian:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

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

2019-11-20 Thread Martin-peres-n
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/drm/amd/issues/365.

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

Title:
  Switching to integrated card with vgaswitcheroo makes the kernel to
  hang, until pulseaudio is killed

Status in Linux:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a dual-GPU notebook, with a Intel Ironlake integrated GPU and a
  AMD 5650m dedicated GPU (muxed system). The AMD gpu is also connected
  to an HDMI port that implies an audio card (I'm running radeon module
  with radeon.audio=1).

  If I switch to the integrated card after that the UI is up and
  pulseaudio is loaded, as soon as I exit from lightdm (both to reload X
  or to shutdown the PC) the kernel hangs (both in 12.10, 13.04 and
  13.10):

  [ 489.177732] hda-intel :01:00.1: Disabling via VGA-switcheroo
  [ 489.297129] hda-intel :01:00.1: Cannot lock devices!
  [ 489.297139] radeon: switched off
  [ 489.300356] [drm] Disabling audio support
  [ 489.319552] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x0015e418 and cpu addr 0xc90009df0418
  [ 489.973886] ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event: unsupported
  [ 489.973903] _handle_hotplug_event_root: Bus check notify on \_SB_.PCI0
  [ 678.992375] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 678.992453] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 683.996303] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 683.996377] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 683.996453] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing C3DC (len 871, WS 0, PS 0) @ 0xC439
  [ 689.000275] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 689.000349] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 694.004285] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 694.004363] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 699.008330] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 699.008414] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 699.514458] init: tty1 main process (2460) killed by QUIT signal
  [ 699.514489] init: tty1 main process ended, respawning
  [ 704.012405] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 704.012492] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 709.016515] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 709.016596] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28

  
  At the contrary, if once lightdm starts I go to tty1 → sudo service lighdm 
stop → sudo killall pulseaudio → echo OFF| sudo tee 
/sys/kernel/debug/vgaswitcheroo/switch #switch to integrated card

  Everything works well instead.

  So it seems that pulseaudio should disable the powered-off card on
  switch (or is this something that the kernel should do?).

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1210470/+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 1210470] Re: Switching to integrated card with vgaswitcheroo makes the kernel to hang, until pulseaudio is killed

2019-11-20 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Unknown

** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #365
   https://gitlab.freedesktop.org/drm/amd/issues/365

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

Title:
  Switching to integrated card with vgaswitcheroo makes the kernel to
  hang, until pulseaudio is killed

Status in Linux:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a dual-GPU notebook, with a Intel Ironlake integrated GPU and a
  AMD 5650m dedicated GPU (muxed system). The AMD gpu is also connected
  to an HDMI port that implies an audio card (I'm running radeon module
  with radeon.audio=1).

  If I switch to the integrated card after that the UI is up and
  pulseaudio is loaded, as soon as I exit from lightdm (both to reload X
  or to shutdown the PC) the kernel hangs (both in 12.10, 13.04 and
  13.10):

  [ 489.177732] hda-intel :01:00.1: Disabling via VGA-switcheroo
  [ 489.297129] hda-intel :01:00.1: Cannot lock devices!
  [ 489.297139] radeon: switched off
  [ 489.300356] [drm] Disabling audio support
  [ 489.319552] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x0015e418 and cpu addr 0xc90009df0418
  [ 489.973886] ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event: unsupported
  [ 489.973903] _handle_hotplug_event_root: Bus check notify on \_SB_.PCI0
  [ 678.992375] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 678.992453] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 683.996303] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 683.996377] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 683.996453] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing C3DC (len 871, WS 0, PS 0) @ 0xC439
  [ 689.000275] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 689.000349] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 694.004285] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 694.004363] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 699.008330] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 699.008414] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 699.514458] init: tty1 main process (2460) killed by QUIT signal
  [ 699.514489] init: tty1 main process ended, respawning
  [ 704.012405] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 704.012492] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 709.016515] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 709.016596] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28

  
  At the contrary, if once lightdm starts I go to tty1 → sudo service lighdm 
stop → sudo killall pulseaudio → echo OFF| sudo tee 
/sys/kernel/debug/vgaswitcheroo/switch #switch to integrated card

  Everything works well instead.

  So it seems that pulseaudio should disable the powered-off card on
  switch (or is this something that the kernel should do?).

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