date:20200313

Public bug reported:

See libfido MIR
https://bugs.launchpad.net/ubuntu/+source/libfido2/+bug/1864439

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


** Tags: update-excuse

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

Title:
  openssh 8.2 waiting on libfido2 MIR

Status in openssh package in Ubuntu:
  New

Bug description:
  See libfido MIR
  https://bugs.launchpad.net/ubuntu/+source/libfido2/+bug/1864439

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1867408/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

This bug was fixed in the package kmod - 27-1ubuntu2

---
kmod (27-1ubuntu2) focal; urgency=medium

  * d/p/verbose_missing_bin: drop this patch to avoid spurious missing
file messages when running depmod -a for the first time in recent
kernels (>= 5.3.x) (LP: #1864992)

 -- Rafael David Tinoco   Thu, 12 Mar 2020
13:15:28 +

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

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  In Progress
Status in kmod source package in Focal:
  Fix Released

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  ---

[Touch-packages] [Bug 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays

This bug was fixed in the package openldap - 2.4.49+dfsg-2ubuntu1

---
openldap (2.4.49+dfsg-2ubuntu1) focal; urgency=medium

  * Merge with Debian unstable (LP: #1866303). Remaining changes:
- Enable AppArmor support:
  - d/apparmor-profile: add AppArmor profile
  - d/rules: use dh_apparmor
  - d/control: Build-Depends on dh-apparmor
  - d/slapd.README.Debian: add note about AppArmor
- Enable GSSAPI support:
  - d/patches/gssapi.diff, thanks to Jerry Carter (Likewise):
- Add --with-gssapi support
- Make guess_service_principal() more robust when determining
  principal
[Dropped the ldap_gssapi_bind_s() hunk as that is already
  - d/configure.options: Configure with --with-gssapi
  - d/control: Added heimdal-dev as a build depend
  - d/rules:
- Explicitly add -I/usr/include/heimdal to CFLAGS.
- Explicitly add -I/usr/lib//heimdal to LDFLAGS.
- Enable ufw support:
  - d/control: suggest ufw.
  - d/rules: install ufw profile.
  - d/slapd.ufw.profile: add ufw profile.
- Enable nss overlay:
  - d/rules:
- add nssov to CONTRIB_MODULES
- add sysconfdir to CONTRIB_MAKEVARS
  - d/slapd.install:
- install nssov overlay
  - d/slapd.manpages:
- install slapo-nssov(5) man page
- d/{rules,slapd.py}: Add apport hook.
- d/slapd.init.ldif: don't set olcRootDN since it's not defined in
  either the default DIT nor via an Authn mapping.
- d/slapd.scripts-common:
  - add slapcat_opts to local variables.
  - Fix backup directory naming for multiple reconfiguration.
- d/{slapd.default,slapd.README.Debian}: use the new configuration style.
- d/rules: Enable -DLDAP_CONNECTIONLESS to build CLDAP (UDP) support
  in the openldap library, as required by Likewise-Open
- Show distribution in version:
  - d/control: added lsb-release
  - d/patches/fix-ldap-distribution.patch: show distribution in version
- d/libldap-2.4-2.symbols: Add symbols not present in Debian.
  - CLDAP (UDP) was added in 2.4.17-1ubuntu2
  - GSSAPI support was enabled in 2.4.18-0ubuntu2
- d/p/contrib-makefiles: given the change in 2.4.47+dfsg-3 regarding
  Debian bug #919136, we also have to patch the nssov makefile
  accordingly and thus update this patch.

openldap (2.4.49+dfsg-2) unstable; urgency=medium

  * slapd.README.Debian: Document the initial setup performed by slapd's
maintainer scripts in more detail. Thanks to Karl O. Pinc.
(Closes: #952501)
  * Import upstream patch to fix slapd crashing in certain configurations when
a client attempts a login to a locked account.
(ITS#9171) (Closes: #953150)

 -- Andreas Hasenack   Fri, 06 Mar 2020 11:39:12
-0300

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

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

Title:
  slapd crash with pwdAccountLockedTime and stacked overlays

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  New
Status in openldap source package in Bionic:
  New
Status in openldap source package in Disco:
  New
Status in openldap source package in Eoan:
  New
Status in openldap package in Debian:
  Unknown

Bug description:
  Hello,

  Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an
  issue in the ppolicy overlay that can crash slapd. Please also
  consider SRUing the patch after it has had some testing time.

  Upstream: https://openldap.org/its/?findid=9171
  Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150

  The ingredients for the crash are:

  1: ppolicy overlay configured with pwdLockout: TRUE
  2. smbk5pwd overlay stacked after ppolicy
  3. an account locked out via pwdAccountLockedTime
  4. a client binding to the locked-out account and also requesting the ppolicy 
control

  The buggy code is not as specific as the above steps, so I suspect
  there are probably other configurations or steps that can trigger the
  same crash.

  I will attach my test script and data for reproducing the crash.

  Expected output (last lines):

  [ ok ] Starting OpenLDAP: slapd.
  slapd running
  ldap_bind: Invalid credentials (49)
  slapd running

  Actual output (last lines):

  [ ok ] Starting OpenLDAP: slapd.
  slapd running
  ldap_bind: Invalid credentials (49)
  slapd dead

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+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 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap

2020-03-13 Thread Gunnar Hjalmarsson

As an experiment I manipulated the deb so it depends on python2 instead
of python:

https://people.ubuntu.com/~gunnarhj/atom-python2-amd64.deb

That file could be installed on focal, and I could successfully use IBus
input methods.

In other words: The issue with IBus failing is specific to the snap
version.

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

Title:
  IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0
  as snap

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0, it simply doesn't work.
  When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+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 1866996] Re: apport-retrace can not be used with https mirrors in sources.list

2020-03-13 Thread Esokrates

@Brian: I will open a separate bug for comment #9 soon, as this issue
here is about the https issue.

Since you asked to reproduce please fully upgrade your focal
installation and use the files as found in the attached tar archive.

Command to reproduce is:

apport-retrace -v -s -R -S system _usr_bin_gnome-shell.1000.crash

** Attachment added: "debuginfo-1866996.tar.gz"
   
https://bugs.launchpad.net/apport/+bug/1866996/+attachment/5336720/+files/debuginfo-1866996.tar.gz

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

Title:
  apport-retrace can not be used with https mirrors in sources.list

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  Here I collect a couple of issues regarding apport-retrace with "-S
  system".

  1. apport-retrace does not work for https mirros in sources.list
  2. If the sandbox is built successfully the stack-trace of generated does 
even contain less info than simply calling "apport-retrace -v -s -R" without 
the sandbox.
  3. I have found fixes / workaround for issue 1. and 2., see the attached 
patches, however in the end I'm still not satisfied with the quality of the 
results:

  For example I tested apport by invoking a crash of gnome-software with kill 
-s SIGSEGV $(pidof gnome-software).
 
  Invoking apport-retrace without sandbox (apport-retrace -R --stdout 
_usr_bin_gnome-software.1000.crash) gives me the following backtrace:

  --- stack trace ---
  #0  0x7f3e39555c3f in __GI___poll (fds=0x55b072be60f0, nfds=3, 
timeout=6816) at ../sysdeps/unix/sysv/linux/poll.c:29
  resultvar = 18446744073709551100
  sc_cancel_oldtype = 0
  sc_ret = 
  #1  0x7f3e3a4b21ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f3e3a4b22e3 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f3e3a362ec5 in g_application_run () from 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #4  0x55b07218ed59 in main ()
  No symbol table info available.
  --- source code stack trace ---
  #0  0x7f3e39555c3f in __GI___poll (fds=0x55b072be60f0, nfds=3, 
timeout=6816) at ../sysdeps/unix/sysv/linux/poll.c:29
[Error: poll.c was not found in source tree]
  #1  0x7f3e3a4b21ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7f3e3a4b22e3 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7f3e3a362ec5 in g_application_run () from 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #4  0x55b07218ed59 in main ()

  Invoking apport-retrace with sandbox (apport-retrace -v -s -R -S
  system _usr_bin_gnome-software.1000.crash) gives me the following
  (which is not much better):

  --- stack trace ---
  #0  0x7f3e39555c3f in poll () from /lib/x86_64-linux-gnu/libc.so.6
  No symbol table info available.
  #1  0x7f3e3a4b21ae in g_main_context_iterate.isra () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f3e3a4b22e3 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f3e3a362ec5 in g_application_run (application=0x55b072bbd0f0, 
argc=, argv=) at ../../../gio/gapplication.c:2559
  arguments = 0x55b072be60d0
  status = 0
  context = 0x55b072be6130
  acquired_context = 1
  __func__ = "g_application_run"
  #4  0x55b07218ed59 in main ()
  No symbol table info available.
  --- source code stack trace ---
  #0  0x7f3e39555c3f in poll () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7f3e3a4b21ae in g_main_context_iterate.isra () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7f3e3a4b22e3 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7f3e3a362ec5 in g_application_run (application=0x55b072bbd0f0, 
argc=, argv=) at ../../../gio/gapplication.c:2559
[Error: gapplication.c was not found in source tree]
  #4  0x55b07218ed59 in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1866996/+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 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0

2020-03-13 Thread Gunnar Hjalmarsson

Thanks. I can confirm your observations on eoan. IBus doesn't work with
atom as snap on focal either.

The deb is not even installable on focal since the python package has
been removed. Atom depends on python2, which is about to be dropped from
the Ubuntu archive. Some kind of workaround may be available before the
release of Ubuntu 20.04, though.

So there are two issues:

* The snap issue, which I would suggest that you report upstream:

  https://github.com/snapcrafters/atom/issues/

* The removal of python2 in Ubuntu - upstream really should port the
software to python3.

So Ubuntu does not seem to be very atom friendly at the moment. I don't
think this is an IBus issue, but since I don't know a better package, I
keep this bug open for now for info purposes.

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

** Summary changed:

- IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0
+ IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap

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

Title:
  IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0
  as snap

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0, it simply doesn't work.
  When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+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 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)

2020-03-13 Thread ktaherig

I'm actually running 4.15 as my main OS (specifically Xubuntu 18.04)
specifically because it works perfectly as expected. If you'd like, I
can test older kernels, such as 4.2, 3.16, maybe even 3.5, if you'd
like, just to make sure.

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

Title:
  [HP Pavilion dv9000] Mute toggles on/off while plugged into the
  headphone/speaker jack (19.04+)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-
  pavilion-dv9000/specs/) built many years ago.

  
  Whenever I'm using any distro that's based on Ubuntu which was published from 
Version 19.04 onwards, I've been having a major issue with the mute button 
toggling on and off whenever I have something plugged into the audio out jack. 
I know that it's not the fault of XFCE, because I also use the latest version 
of Manjaro with XFCE on this same computer, and it works fine. I also know it's 
not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 
6) also on this exact same computer, and it also works fine. Qubes, Mageia, and 
Fedora 31 also work perfectly fine and don't have this issue.

  My "lsb-release" is:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  and "apt-cache policy pulseaudio" outputs:
  pulseaudio:
Installed: 1:13.0-1ubuntu1.1
Candidate: 1:13.0-1ubuntu1.1
Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  I've uploaded a short video of the problem that I recorded with my phone here:
  https://www.youtube.com/watch?v=GXaHXQA-5uQ

  
  The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, 
Xubuntu 19.04, and Sparky 5.10 and 2020.02.

  
  I've checked pretty much everything I can think of. There's a log for my ALSA 
help diagnostics results on my current computer (which works properly with 
18.04) at:
  http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829

  
  the result output of lspci is:
  [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2)
  00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2)
  00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2)
  00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2)
  00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2)
  00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2)
  00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2)
  00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3)
  00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3)
  00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3)
  00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1)
  00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2)
  00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2)
  00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g 
WLAN (rev 01)
  05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] 
(rev a1)
  07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
  07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host 
Adapter (rev 19)
  07:05.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter 
(rev 0a)
  07:05.3

[Touch-packages] [Bug 1865517] Re: cannot log in with long username

2020-03-13 Thread Brian Murray

** Tags added: focal

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  cannot log in with long username

Status in util-linux package in Ubuntu:
  Triaged

Bug description:
  We use ldap authentication with mail addresses as usernames.
  So usernames are not posix and some are > 32 chars but are working.

  Some of them fire a bug :
  When trying to log, it doesn't asks for password, it just wait some seconds 
then reset to ask username.

  I can't clearly identify which regex fire the bug or not but this one does
  "username.lastnamelastnamelastn...@domain.fr"

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

  In auth.log, that line pops up when bug is started

  "Mar  2 16:23:14 premier agetty[97945]: checkname failed: Operation
  not permitted"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865517/+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 1863239] Re: /dev/bus/usb// device file of HP multi-function printer assigned to "audio" group

2020-03-13 Thread Till Kamppeter

** Changed in: libmtp (Ubuntu)
   Importance: High => Critical

** Changed in: pulseaudio (Ubuntu)
   Importance: High => Critical

** Changed in: systemd (Ubuntu)
   Importance: High => Critical

** Changed in: udev (Ubuntu)
   Importance: High => Critical

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0

2020-03-13 Thread ytxmobile

Both tried snap and deb versions on Ubuntu 19.10 on a personal computer.
Snap: cannot input Chinese with IBus
Deb: works as normal

Also tried both snap and deb on a workplace computer with Ubuntu 18.04.
Both snap and deb versions of Atom work well with inputting Chinese.

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

Title:
  IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0, it simply doesn't work.
  When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+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 1867390] [NEW] Update libarchive to 3.4.2

2020-03-13 Thread Amr Ibrahim

Public bug reported:

Please update libarchive to 3.4.2.

https://github.com/libarchive/libarchive/releases

Libarchive 3.4.2 is a feature and security release.

New features:

support for atomic file extraction (bsdtar -x --safe-writes) (#1289)
support for mbed TLS (PolarSSL) (#1301)

Important bugfixes:

security fixes in RAR5 reader (#1280 #1326)
compression buffer fix in XAR writer (#1317)
fix uname and gname longer than 32 characters in PAX writer (#1319)
fix segfault when archiving hard links in ISO9660 and XAR writers (#1325)
fix support for extracting 7z archive entries with Delta filter (#987)


Libarchive 3.4.1 is a feature and security release.

New features:

Unicode filename support for reading lha/lzh archives
New pax write option "xattrhdr"

Important bugfixes:

security fixes in wide string processing (#1276 #1298)
security fixes in RAR5 reader (#1212 #1217 #1296)
security fixes and optimizations to write filter logic (#351)
security fix related to use of readlink(2) (1dae5a5)
sparse file handling fixes (#1218 #1260)

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


** Tags: focal upgrade-software-version

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

Title:
  Update libarchive to 3.4.2

Status in libarchive package in Ubuntu:
  New

Bug description:
  Please update libarchive to 3.4.2.

  https://github.com/libarchive/libarchive/releases

  Libarchive 3.4.2 is a feature and security release.

  New features:

  support for atomic file extraction (bsdtar -x --safe-writes) (#1289)
  support for mbed TLS (PolarSSL) (#1301)

  Important bugfixes:

  security fixes in RAR5 reader (#1280 #1326)
  compression buffer fix in XAR writer (#1317)
  fix uname and gname longer than 32 characters in PAX writer (#1319)
  fix segfault when archiving hard links in ISO9660 and XAR writers (#1325)
  fix support for extracting 7z archive entries with Delta filter (#987)

  
  Libarchive 3.4.1 is a feature and security release.

  New features:

  Unicode filename support for reading lha/lzh archives
  New pax write option "xattrhdr"

  Important bugfixes:

  security fixes in wide string processing (#1276 #1298)
  security fixes in RAR5 reader (#1212 #1217 #1296)
  security fixes and optimizations to write filter logic (#351)
  security fix related to use of readlink(2) (1dae5a5)
  sparse file handling fixes (#1218 #1260)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1867390/+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 1864561] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event

2020-03-13 Thread Bjorn Hassler

Hello all,
any updates or thoughts on this?
Many thanks!

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

Title:
For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports
that IM handled the event

Status in gtk+3.0 package in Ubuntu:
New
Status in ibus package in Ubuntu:
New

Bug description:
If the keypress event contains GDK_HYPER_MASK as a modifier,
gtk_im_context_filter_keypress() returns true, reporting that the IM
handled the event, even though it did not, therefore it should return
false.

Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to
enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X
users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful
alternative approaches detailed here:
https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md).
When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus)
reports that it handled the event that had Hyper as the modifier. When we use
export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected.

We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not
sure whether this is an issue in ibus or gtk, so I'm reporting it in
both places (as well as upstream). Apologies for the inconvenience
caused by this. Many thanks for looking at this.

I'll track updates here
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220
and here

https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md
so that people compinging Gnonme Terminal are aware of the status.

Many thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1864561/+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 1864561] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event

2020-03-13 Thread Bjorn Hassler

Hello all,
any updates or thoughts on this?
Many thanks!

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

Title:
For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports
that IM handled the event

Status in gtk+3.0 package in Ubuntu:
New
Status in ibus package in Ubuntu:
New

I'll track updates here
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220
and here

https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md
so that people compinging Gnonme Terminal are aware of the status.

Many thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1864561/+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 1867375] Re: systemd-networkd: Setting UseRoutes to False results in DHCP default gateway not being installed

2020-03-13 Thread Sunil Mukundan

** Summary changed:

- systemd-network: Setting UseRoutes to False results in DHCP default gateway 
not being installed
+ systemd-networkd: Setting UseRoutes to False results in DHCP default gateway 
not being installed

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

Title:
  systemd-networkd: Setting UseRoutes to False results in DHCP default
  gateway not being installed

Status in systemd package in Ubuntu:
  New

Bug description:
  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in 
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867375/+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 1867375] [NEW] systemd-network: Setting UseRoutes to False results in DHCP default gateway not being installed

2020-03-13 Thread Sunil Mukundan

Public bug reported:

requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in 
https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

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

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

Title:
  systemd-network: Setting UseRoutes to False results in DHCP default
  gateway not being installed

Status in systemd package in Ubuntu:
  New

Bug description:
  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in 
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867375/+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 1764860] Re: dbus crashed with SIGABRT in _dbus_abort()

2020-03-13 Thread oldfred

Just had this error in 20.04.
But may be related to this already reported:
[Bug 1866838] [NEW] ippusbxd crashed with SIGSEGV in usb_conn_acquire()

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

Title:
  dbus crashed with SIGABRT in _dbus_abort()

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  bionic beaver @ dell xps12

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 20:42:40 2018
  ExecutablePath: /usr/lib/cups/notifier/dbus
  InstallationDate: Installed on 2018-03-11 (37 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lpstat:
   device for HP_LaserJet_500_color_M551_2F183C_: 
ipp://BKPRT777.local:631/ipp/print
   device for HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: 
ipps://BKPRT777.local:443/ipp/print
   device for Lexmark-W820-Bravo: socket://10.42.9.152:9100
  MachineType: Dell Inc. XPS 12 9Q23
  Papersize: letter
  PpdFiles:
   Lexmark-W820-Bravo: Lexmark W820 PS
   HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: HP LaserJet 500 color 
M551, driverless, cups-filters 1.20.2
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct 
i8042.dumbkbd vt.handoff=1
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct 
i8042.dumbkbd vt.handoff=1
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
   __libc_start_main (main=0x55f0c84c81b0, argc=3, argv=0x7ffcaf592438, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcaf592428) at ../csu/libc-start.c:310
  Title: dbus crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (37 days ago)
  UserGroups:
   
  dmi.bios.date: 12/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.asset.tag: 0004061282
  dmi.board.name: 0520M8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 0004061282
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/07/2012:svnDellInc.:pnXPS129Q23:pvrA05:rvnDellInc.:rn0520M8:rvrA00:cvnDellInc.:ct8:cvrA05:
  dmi.product.family: 103C_5335KV
  dmi.product.name: XPS 12 9Q23
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1764860/+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 1764860] Re: dbus crashed with SIGABRT in _dbus_abort()

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  dbus crashed with SIGABRT in _dbus_abort()

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  bionic beaver @ dell xps12

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 20:42:40 2018
  ExecutablePath: /usr/lib/cups/notifier/dbus
  InstallationDate: Installed on 2018-03-11 (37 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lpstat:
   device for HP_LaserJet_500_color_M551_2F183C_: 
ipp://BKPRT777.local:631/ipp/print
   device for HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: 
ipps://BKPRT777.local:443/ipp/print
   device for Lexmark-W820-Bravo: socket://10.42.9.152:9100
  MachineType: Dell Inc. XPS 12 9Q23
  Papersize: letter
  PpdFiles:
   Lexmark-W820-Bravo: Lexmark W820 PS
   HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: HP LaserJet 500 color 
M551, driverless, cups-filters 1.20.2
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct 
i8042.dumbkbd vt.handoff=1
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct 
i8042.dumbkbd vt.handoff=1
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
   __libc_start_main (main=0x55f0c84c81b0, argc=3, argv=0x7ffcaf592438, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcaf592428) at ../csu/libc-start.c:310
  Title: dbus crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (37 days ago)
  UserGroups:
   
  dmi.bios.date: 12/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.asset.tag: 0004061282
  dmi.board.name: 0520M8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 0004061282
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/07/2012:svnDellInc.:pnXPS129Q23:pvrA05:rvnDellInc.:rn0520M8:rvrA00:cvnDellInc.:ct8:cvrA05:
  dmi.product.family: 103C_5335KV
  dmi.product.name: XPS 12 9Q23
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1764860/+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 1867372] [NEW] Auditd failed when changing the Rsyslog configuration

2020-03-13 Thread Dmitriy Kulikov

Public bug reported:

I found that when changing the Rsyslog configuration 
(/etc/rsyslog.d/50-default.conf) an Auditd failure occurs with distinctive 
strings in syslog:
ExecStartPost=/sbin/augenrules --load (code=exited, status=1/FAILURE)
.
There was an error in line 6 of /etc/audit/audit.rules


Other sign:

# systemctl status auditd
● auditd.service - Security Auditing Service
   Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Fri 2020-03-13 17:49:55 MSK; 12min ago
 Docs: man:auditd(8)
   https://github.com/linux-audit/audit-documentation
  Process: 985 ExecStartPost=/sbin/augenrules --load (code=exited, 
status=1/FAILURE)
  Process: 883 ExecStart=/sbin/auditd (code=exited, status=0/SUCCESS)
 Main PID: 928 (auditd)
Tasks: 4 (limit: 4915)
   CGroup: /system.slice/auditd.service
   ├─928 /sbin/auditd
   └─932 /sbin/audispd


The problem was confirmed on two modern physical Linux Ubuntu servers with all 
the latest system updates.
Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-88-generic x86_64)
---
auditd/bionic,now 1:2.8.2-1ubuntu1 amd64 [installed]
libaudit-common/bionic,bionic,now 1:2.8.2-1ubuntu1 all [installed]
libaudit1/bionic,now 1:2.8.2-1ubuntu1 amd64 [installed]
+
rsyslog/bionic,now 8.32.0-1ubuntu4 amd64 [installed,automatic]


The first time I found a problem trying to reconfigure Auditd logging according 
to the recommendations:
https://serverfault.com/questions/792766/what-is-the-syslog-facility-for-auditd-logs
When I found the problem, I checked its causes on the Rsyslog side on another 
server.
It is confirmed that it is not associated with changes in the configuration of 
Auditd.


Example of replication: 
---
1. Edit /etc/rsyslog.d/50-default.conf
Insert strings for new log facility:
*.*;auth,authpriv.none,cron.none,mail.none,local5.none,local6.none  
-/var/log/syslog
###
###*.*;auth,authpriv.none,cron.none,mail.none,local5.none   
-/var/log/syslog

local6.*/var/log/audit/audit_syslog.log

2. # systemctl restart rsyslog

3. # systemctl restart auditd

4. # systemctl status auditd
● auditd.service - Security Auditing Service
   Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Fri 2020-03-13 18:12:32 MSK; 6s ago
 Docs: man:auditd(8)
   https://github.com/linux-audit/audit-documentation
  Process: 3211 ExecStartPost=/sbin/augenrules --load (code=exited, 
status=1/FAILURE)
  Process: 3183 ExecStart=/sbin/auditd (code=exited, status=0/SUCCESS)
 Main PID: 3186 (auditd)
Tasks: 4 (limit: 4915)
   CGroup: /system.slice/auditd.service
   ├─3186 /sbin/auditd
   └─3190 /sbin/audispd

Mar 13 18:12:32 uk1 augenrules[3211]: failure 1
Mar 13 18:12:32 uk1 augenrules[3211]: pid 3186
Mar 13 18:12:32 uk1 augenrules[3211]: rate_limit 0
Mar 13 18:12:32 uk1 augenrules[3211]: backlog_limit 8192
Mar 13 18:12:32 uk1 augenrules[3211]: lost 0
Mar 13 18:12:32 uk1 augenrules[3211]: backlog 0
Mar 13 18:12:32 uk1 augenrules[3211]: backlog_wait_time 0
Mar 13 18:12:32 uk1 systemd[1]: Started Security Auditing Service.
Mar 13 18:12:32 uk1 auditctl[3225]: There was an error in line 6 of 
/etc/audit/audit.rules
Mar 13 18:12:32 uk1 audispd[3190]: node=uk1 type=SERVICE_START 
msg=audit(1584112352.783:142): pid=1 uid=0 auid=4294967295 ses=4294967295 
msg='unit=auditd comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? 
terminal=? res=success'


But the main problem is that this failure cannot be fixed by deleting changes 
from the Rsyslog configuration file.
It remains even after restarting the server!

I have attached snippets of the system log.
The first part corresponds to restarting the system after rolling back Rsyslog 
changes.
The second part corresponds to the processes after the Auditd restart.

In General, it looks like Auditd is working normally. Logs show its working 
status.
But in the system status auditd is issued:
ExecStartPost=/sbin/augenrules --load (code=exited, status=1/FAILURE)

And this cannot be eliminated.

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


** Tags: augenrules rsyslog

** Attachment added: "Logs and configs"
   
https://bugs.launchpad.net/bugs/1867372/+attachment/5336591/+files/auditd+rsyslog_bug.zip

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

Title:
  Auditd failed when changing the Rsyslog configuration

Status in audit package in Ubuntu:
  New

Bug description:
  I found that when changing the Rsyslog configuration 
(/etc/rsyslog.d/50-default.conf) an Auditd failure occurs with distinctive 
strings in syslog:
  ExecStartPost=/sbin/augenrules --load (code=exited,

[Touch-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264

2020-03-13 Thread knossos456

Thank you Joseph.
As I written in first post, 20.1 git is ok here, tested from: 
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
How can I test more, how to do to push the oibaf compil to ubuntu repository ?

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

Title:
  Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i
  H.264

Status in mesa package in Ubuntu:
  New

Bug description:
  uname -a
  Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  inxi -G
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 
240/340 OEM]
 Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 
9.0.0) version: 4.5 Mesa 19.2.8

  For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen
  (top) compressed image.

  To solve the default, i have to revert via synaptic the package mesa-
  va-driver to 19.0.8.

  Other solution is to take nighty builds as complete mesa package via : 
  https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers   that works 
too and is at mesa 20.1 git

  Please correct the problem to the official Ubuntu repos.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1856884] CurrentDmesg.txt

apport information

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

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (411 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (411 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] Re: not proper sound device

done. you can ask any information to solve this problem

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (411 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] ProcEnviron.txt

apport information

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

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (411 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] Dependencies.txt

apport information

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

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (411 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] PulseList.txt

apport information

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

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (411 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] AudioDevicesInUse.txt

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1856884/+attachment/5336547/+files/AudioDevicesInUse.txt

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (411 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] Re: not proper sound device

apport information

** Description changed:

  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.5
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-01-26 (411 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: pulseaudio 1:13.0-1ubuntu1.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
+ Tags:  eoan
+ Uname: Linux 5.3.0-40-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/19/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P5.40
+ dmi.board.name: AB350 Pro4
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.sku: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.

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

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Touch-packages] [Bug 1867304] Re: LG OLED TV screen resolution not properly detected

2020-03-13 Thread Brian Murray

** Tags added: eoan

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

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

Title:
  LG OLED TV screen resolution not properly detected

Status in xorg package in Ubuntu:
  New

Bug description:
  When I connect my LG OLED B9 TV to my computer, black bars appear at
  the top and bottom.  The desktop won't scale to the full screen.

  Here's some basic info:

  Ubuntu 19.10
  AMD 560 graphics card
  LG OLED B9 TV

  I tried changing the display settings, but the black bars won't go
  away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1867304/+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 1867304] [NEW] LG OLED TV screen resolution not properly detected

You have been subscribed to a public bug:

When I connect my LG OLED B9 TV to my computer, black bars appear at the
top and bottom.  The desktop won't scale to the full screen.

Here's some basic info:

Ubuntu 19.10
AMD 560 graphics card
LG OLED B9 TV

I tried changing the display settings, but the black bars won't go away.

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


** Tags: bot-comment eoan
-- 
LG OLED TV screen resolution not properly detected
https://bugs.launchpad.net/bugs/1867304
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1867352] [NEW] Xorg freeze after boot if use xorg.conf generated by nvidia-xconfig

2020-03-13 Thread Igor Zubarev

Public bug reported:

Hello!

I have constant X crash if use xorg.conf generated by nvidia-xconfig.
Currently my xorg.conf is absent. Only if I have an empty conf file or it is 
absent I can start X.
The problem exists in 19.10 and 20.04 development version

Also I have strange messages if I run nvidia-xconfig:
$ sudo nvidia-xconfig

WARNING: Unable to locate/open X configuration file.

Package xorg-server was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-server.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xorg-server' found
New X configuration file written to '/etc/X11/xorg.conf'


Here is my xorg.conf generated by nvidia:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 440.64

Section "ServerLayout"
Identifier "Layout0"
Screen  0  "Screen0"
InputDevice"Keyboard0" "CoreKeyboard"
InputDevice"Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "Unknown"
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
DefaultDepth24
SubSection "Display"
Depth   24
EndSubSection
EndSection

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.2.1 20200304 (Ubuntu 9.2.1-31ubuntu1)
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 13 16:44:45 2020
DistUpgraded: 2020-03-13 00:50:36,699 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: I don't know
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller 
[104d:90b7]
   Subsystem: Sony Corporation GK208M [GeForce GT 735M] [104d:90b7]
MachineType: Sony Corporation SVF15A1S9RB
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=81c8a442-a191-4c83-b415-ee0f1f2b0b81 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-03-12 (0 days ago)
dmi.bios.date: 07/19/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0250DA
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0250DA:bd07/19/2016:svnSonyCorporation:pnSVF15A1S9RB:pvrC10H9CDB:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: SVF15A1S9RB
dmi.product.sku: 54581586
dmi.product.version: C10H9CDB
dmi.sys.vendor: Sony Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1

[Touch-packages] [Bug 1867349] [NEW] [HP ENVY Notebook, Realtek ALC3241, Speaker, Internal] Underruns, dropouts or crackling sound

2020-03-13 Thread Santiago

Public bug reported:

I recently did a dual boot to my pc, but I've been having some issues
with the sound. Every time I play music or a video, my speaker starts to
do a weird noise, like crackling and beeps.

My sound card is: HDA Intel PCH

My chip is: Realtek ALC3241

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  santiago   1285 F pulseaudio
  santiago   4110 F alsamixer
 /dev/snd/pcmC0D0p:   santiago   1285 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 13 08:51:11 2020
InstallationDate: Installed on 2020-03-13 (0 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog: mar 13 08:09:52 HP-ENVY-Notebook dbus-daemon[795]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.35' (uid=1000 pid=1285 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined")
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [HP ENVY Notebook, Realtek ALC3241, Speaker, Internal] Underruns, 
dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/14/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.52
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80E5
dmi.board.vendor: HP
dmi.board.version: 87.78
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd06/14/2019:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.78:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook
dmi.product.sku: P0D91LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug bionic

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

Title:
  [HP ENVY Notebook, Realtek ALC3241, Speaker, Internal] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I recently did a dual boot to my pc, but I've been having some issues
  with the sound. Every time I play music or a video, my speaker starts
  to do a weird noise, like crackling and beeps.

  My sound card is: HDA Intel PCH

  My chip is: Realtek ALC3241

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  santiago   1285 F pulseaudio
santiago   4110 F alsamixer
   /dev/snd/pcmC0D0p:   santiago   1285 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 13 08:51:11 2020
  InstallationDate: Installed on 2020-03-13 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 13 08:09:52 HP-ENVY-Notebook dbus-daemon[795]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.35' (uid=1000 pid=1285 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [HP ENVY Notebook, Realtek ALC3241, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.52
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80E5
  dmi.board.vendor: HP
  dmi.board.version: 87.78
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd06/14/2019:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.78:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP

[Touch-packages] [Bug 1790926] Re: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to
  accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to
  accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Sep  5 20:34:37 2018
  InstallationDate: Installed on 2018-06-18 (78 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1790926/+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 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends

2020-03-13 Thread AsciiWolf

Related issue: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1867345

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

Title:
  Add chrome-gnome-shell to ubuntu-desktop recommends

Status in One Hundred Papercuts:
  New
Status in chrome-gnome-shell package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Please, consider adding the chrome-gnome-shell package as a
  recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The
  chrome-gnome-shell package provides GNOME Shell integration
  (connector) for Firefox, Chrome, Chromium and other web browsers that
  is necessary for users to be able to manage GNOME Shell extensions
  using a extensions.gnome.org website. Since the Shell Extensions
  support was removed from gnome-software since 3.36 and the replacement
  Extensions application cannot be used to find and install new
  extensions, there is not any user friendly way to install new Shell
  Extensions without having the chrome-gnome-shell package installed.

  More information:
  https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+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 1853383] Re: autopkgtest regression in test_add_proc_info

** Tags added: id-5e54067a6e5bea5dc7fe43a3

** Tags added: id-5e5406d81dc5c5831b42574e

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

Title:
  autopkgtest regression in test_add_proc_info

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Disco:
  New
Status in apport source package in Eoan:
  New

Bug description:
  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'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1853383/+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 1851806] Re: 'module' object has no attribute 'O_PATH'

** Tags added: id-5e540609ebb75b15e089ff0e

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

Title:
  'module' object has no attribute 'O_PATH'

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  I encountered the following exception in python-apport while
  encountering an exception `bup` which uses `python-apport`. I'm sure
  that the exception lies in the responsibility of `python-apport` (the
  `AttributeError` stacktrace is relevant):

  ```
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
  return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in 
apport_excepthook
  pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/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)
  AttributeError: 'module' object has no attribute 'O_PATH'

  Original exception was:
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: python-apport 2.20.11-0ubuntu8.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:43:02 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851806/+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 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

** Tags added: id-5e4eb982f81e3673a2d90aa6

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Triaged
Status in python3-defaults package in Ubuntu:
  Triaged
Status in command-not-found source package in Focal:
  Triaged
Status in python3-defaults source package in Focal:
  Triaged

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1863195] Re: py3compile should not emit python runtime warnings during dist-upgrade

** Tags added: id-5e4eb9bd8595f13168db02d2

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

Title:
  py3compile should not emit python runtime warnings during dist-upgrade

Status in dh-python package in Ubuntu:
  Confirmed
Status in dh-python source package in Focal:
  Confirmed

Bug description:
  py3compile should compile without emitting python runtime warnings

  on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are
  emitted during apt upgrade, due to buffering=1 being deprecated.

  We will not fix all the packages, and these warnings are not helpful
  to the users, as they cannot and shouldn't need to do anything about
  them, as they come from packages that are maintained by the distro.

  Imho py3compile should execute python interpreter with -W ignore

  Or maybe set PYTHONWARNINGS=ignore in the environment during the
  upgrade?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1863195/+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 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" o

** Tags added: id-5e6a590e09cc81526b48641d

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

Title:
  Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line
  buffering (buffering=1) isn't supported in binary mode, the default
  buffer size will be used" on simple APT usage

Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3.8 package in Ubuntu:
  Won't Fix
Status in python3-defaults source package in Focal:
  Confirmed
Status in python3.8 source package in Focal:
  Won't Fix
Status in python3-defaults package in Debian:
  Unknown

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Run regular APT task such as `sudo apt dist-upgrade`
  3. Wait it to finish

  Expected results:
  * APT runs without any warnings and/or errors

  Actual results:
  * APT runs with many python-related warnings like

  >```
  >/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering 
(buffering=1) isn't supported >in binary mode, the default buffer size will be 
used
  >  self.stdin = io.open(p2cwrite, 'wb', bufsize)
  >
  >```

  Full output below:

  ```
  $ sudo apt dist-upgrade 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
ruby-json ruby-pg ruby-sequel ruby-sequel-pg
  Use 'sudo apt autoremove' to remove them.
  The following NEW packages will be installed:
kdevelop55-libs libxentoolcore1 ubuntu-mate-wallpapers-focal
  The following packages will be upgraded:
atril atril-common debootstrap dmeventd dmsetup dnsmasq-base engrampa 
engrampa-common fwupd fwupd-signed gir1.2-atrildocument-1.5.0
gir1.2-atrilview-1.5.0 gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-pluma-1.0 
initramfs-tools initramfs-tools-bin initramfs-tools-core
iproute2 isc-dhcp-client isc-dhcp-common jekyll k3b k3b-data k3b-i18n 
kdevelop kdevelop-data libatrildocument-dev libatrildocument3
libatrilview-dev libatrilview3 libdevmapper-event1.02.1 libdevmapper1.02.1 
libdistro-info-perl libfwupd2 libfwupdplugin1
libgirepository-1.0-1 libk3b7 libk3b7-extracodecs liblvm2cmd2.03 
libmate-sensors-applet-plugin-dev libmate-sensors-applet-plugin0
libmate-slab0 libmate-window-settings-dev libmate-window-settings1 
libmatedict-dev libmatedict6 libmysqlclient21 libmysqlclient21:i386
libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu 
libvirt-daemon-driver-storage-rbd libvirt-daemon-system
libvirt-daemon-system-systemd libvirt0 libxenstore3.0 
libxmlgraphics-commons-java lvm2 mate-applets mate-applets-common mate-common
mate-control-center mate-control-center-common mate-core 
mate-desktop-environment mate-desktop-environment-core
mate-desktop-environment-extra mate-desktop-environment-extras 
mate-dock-applet mate-media mate-media-common mate-netbook
mate-netbook-common mate-notification-daemon 
mate-notification-daemon-common mate-power-manager mate-power-manager-common
mate-screensaver mate-screensaver-common mate-sensors-applet 
mate-sensors-applet-common mate-sensors-applet-nvidia mate-system-monitor
mate-system-monitor-common mate-terminal mate-terminal-common 
mate-user-share mate-user-share-common mate-utils mate-utils-common maxima
maxima-doc maxima-share mozo nano pluma pluma-common pluma-dev pluma-doc 
plymouth-theme-ubuntu-mate-logo plymouth-theme-ubuntu-mate-text
python-caja-common python3-caja python3-distro-info python3-macaroonbakery 
qemu-block-extra qemu-kvm qemu-system-common qemu-system-data
qemu-system-gui qemu-system-x86 qemu-utils ubuntu-mate-artwork 
ubuntu-mate-default-settings ubuntu-mate-icon-themes
ubuntu-mate-lightdm-theme ubuntu-mate-live-settings ubuntu-mate-themes 
ubuntu-mate-wallpapers ubuntu-mate-wallpapers-artful
ubuntu-mate-wallpapers-bionic ubuntu-mate-wallpapers-common 
ubuntu-mate-wallpapers-complete ubuntu-mate-wallpapers-cosmic
ubuntu-mate-wallpapers-disco ubuntu-mate-wallpapers-eoan 
ubuntu-mate-wallpapers-legacy ubuntu-mate-wallpapers-photos
ubuntu-mate-wallpapers-utopic ubuntu-mate-wallpapers-vivid 
ubuntu-mate-wallpapers-wily ubuntu-mate-wallpapers-xenial
ubuntu-mate-wallpapers-yakkety ubuntu-mate-wallpapers-zesty umbrello
  136 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
  Need to get 215 MB of archives.
  After this operation, 12,8 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://archive.ubuntu.com/ubuntu focal/universe amd64 mate-common all 
1.24.0-1ubuntu1 [17,0 kB]
  ...
  Get:139 http://archive.ubuntu.com/ubuntu focal/universe amd64 
mate-dock-applet amd64 20.04.0-0ubuntu1 [91,8 kB]
  Fetched 215 MB in 4min 4s (882 kB/s)

[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

** Tags added: id-5e4ecf76b760f78c1c9f34d6

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0)

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

Bug description:
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5

  ---

  Session suddenly stopped and came back to login screen, all opened
  windows lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1864644] Re: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4)

** Tags added: id-5e6a5656faaf574535da3ea6

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

Title:
  I get logged out immediately after login to an X session (QXL Xorg
  driver on kernel 5.4)

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Triaged
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Triaged
Status in xserver-xorg-video-qxl source package in Focal:
  Invalid

Bug description:
  I just installed ubuntu 20.04 in a virtual machine and did 'apt-get
  update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a
  non-X session). After that, I tried logging in to a gnome session, and
  got logged out during login processing. This happened a few times;
  then I installed xfce4, rebooted, and got the same behaviour (logout
  during login processing) while trying to log in to an xfce session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  Date: Tue Feb 25 12:06:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2020-02-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-eoan
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-eoan
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+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/systemd/+bug/1864644/+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 1801338] Re: apt fails to properly handle server-side connection closure

** Tags added: id-5e4fb2b7ce3e637d085a94bb

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

Title:
  apt fails to properly handle server-side connection closure

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Triaged

Bug description:
  [Impact]
  In some cases, apt does not correctly handle server-side connection closure 
after a pipeline, and aborts the file being downloaded with an "Undetermined 
Error" when the connection has been closed.

  [Test case]
  This could be seen by running apt build-dep evince on cosmic with a recent 
apt with the pipelining fix (such as 1.6.6) against a local mirror running 
apache from trusty. It remains to be seen whether this is easily reproducible 
for anyone.

  [Regression potential]
  N/A yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+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 1867337] Re: even after login the login page was displaying everywhere.

2020-03-13 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  even after login the login page was displaying everywhere.

Status in xorg package in Ubuntu:
  New

Bug description:
  I logged into Ubuntu and the system crashed and the login screen was a frozen 
screen with login page on it.
  All the apps were not as responsive as the expected login screen won't go.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 13 17:20:00 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fa]
  InstallationDate: Installed on 2020-03-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: Apple Inc. MacBookPro9,2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 229.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+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/1867337/+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 1867337] [NEW] even after login the login page was displaying everywhere.

You have been subscribed to a public bug:

I logged into Ubuntu and the system crashed and the login screen was a frozen 
screen with login page on it.
All the apps were not as responsive as the expected login screen won't go.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 13 17:20:00 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa]
InstallationDate: Installed on 2020-03-11 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
MachineType: Apple Inc. MacBookPro9,2
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2019
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 229.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: 
dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+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 crash focal regression single-occurrence ubuntu
-- 
even after login the login page was displaying everywhere.
https://bugs.launchpad.net/bugs/1867337
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries

2020-03-13 Thread Cash App

Visit our website https://www.apponlinesolutions.com/ as providing
solutions money transfer which is made a lot more easier, we also
provide assistance if by chance any  error occurs then they con contact
us at cash app support number.

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

Title:
  Treats bluetooth input device batteries as batteries

Status in gnome-power-manager package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-power-manager source package in Precise:
  Invalid
Status in upower source package in Precise:
  Fix Released
Status in gnome-power-manager source package in Quantal:
  Invalid
Status in upower source package in Quantal:
  Won't Fix
Status in gnome-power-manager source package in Raring:
  Invalid
Status in upower source package in Raring:
  Fix Released
Status in gnome-power-manager source package in Saucy:
  Invalid
Status in upower source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * There are many Bluetooth devices with battery information inside.
  When they are treated as system battery, it will make the system
  poweroff/suspend/hibernate when some Bluetooth device has critical low
  battery. It is a very annoying behavior for the users. Originally,
  there is no such Bluetooth battery information until Ubuntu 12.04
  brings linux-quantal-lts and linux-raring-lts, so those linux kernels
  also bring this issue.

  [Test Case]

   * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple 
Wireless Keyboard.
   * Click the power indicator and you can find Apple Wireless Mouse is listed 
as system battery, and there is no Apple Wireless Keyboard. If you open 
gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse 
is 'Yes' but it should not be.

  [Regression Potential]

   * There is no obvious regression as I know.

  [Other Info]

   * Most patches are from upstream, modified to fix the conflicts, and made by 
the same developer (i.e. fourdollars).
   * We need another patch from 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2
 to make Apple Wireless Keyboard showing.

  [Original Bug Description]

  This is a weird one... the system is an HP Pavilion 23 All In One and
  is powered by a large power supply brick.

  I currently have an Apple Magic Mouse connected via Bluetooth.  As
  soon as the mouse is connected, the Battery indicator shows up and
  clicking on that shows that the system is reading my mouse as a
  battery!

  See the attached screen shot for what I see in the Power status.

  Looking at hcitool:
  ubuntu@201206-11396:~$ hcitool dev
  Devices:
   hci0 9C:B7:0D:80:71:DB

  To make matters even more weird, I actually observed the battery
  indicator go from full to "Critically Low" and the system suspended
  itself.  Keep in mind, again, that this system has NO battery, it's
  reading my bluetooth mouse as a battery device.

  I disconnected the magic mouse and the battery indicator went to Empty
  Red outline and status showed Battery Disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: wl fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16'
     Mixer name : 'Realtek ALC269VC'
     Components : 'HDA:10ec0269,103c2aee,00100202'
     Controls  : 21
     Simple ctrls  : 10
  Date: Mon Mar 11 03:54:36 2013
  HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: Hewlett-Packard a654
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic

[Touch-packages] [Bug 1867157] Re: Improve command-not-found package headers

https://salsa.debian.org/cpython-team/python2/-/merge_requests/2

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in python3.8 package in Ubuntu:
  New

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+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 1867157] Re: Improve command-not-found package headers

https://salsa.debian.org/cpython-team/python3/-/merge_requests/5

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in python3.8 package in Ubuntu:
  New

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+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 1867157] Re: Improve command-not-found package headers

https://salsa.debian.org/cpython-team/python-defaults/-/merge_requests/1

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in python3.8 package in Ubuntu:
  New

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+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 1867157] Re: Improve command-not-found package headers

https://salsa.debian.org/cpython-
team/python3-defaults/-/merge_requests/3

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in python3.8 package in Ubuntu:
  New

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+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 1867330] [NEW] Ubuntu 20.04 Pulse Audio not detecting Headset in Asus Sephyrus Laptoop

2020-03-13 Thread Abraham Alvarez

Public bug reported:

I own an Asus Zephyrus laptop ( ROG Zephyrus S GX701 Gaming Laptop,
17.3" HDR 144Hz FHD IPS, GeForce RTX 2080, Intel Core i7-9750H
Processor, 32GB DDR4, 1TB PCIe NVMe SSD Hyper Drive) and I installed
Ubuntu 20.04. At one point in time my headset was working (connected to
USB) but about 2 weeks ago it stopped working after an upgrade. It
doesn't work not even connecting it to the headphone jack. I have gone
into the Settings and even though my device appears to be detected the
configuration doesn't seem to take place. The audio keep coming out the
standard output (speakers). It simply does not respect the settings.
Even when I click on the two buttons to (TEST LEFT and TEST RIGHT) with
my headset selected as the output device the sound still comes out the
speakers. Is this a known issue?

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

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

Title:
  Ubuntu 20.04 Pulse Audio not detecting Headset in Asus Sephyrus
  Laptoop

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  I own an Asus Zephyrus laptop ( ROG Zephyrus S GX701 Gaming Laptop,
  17.3" HDR 144Hz FHD IPS, GeForce RTX 2080, Intel Core i7-9750H
  Processor, 32GB DDR4, 1TB PCIe NVMe SSD Hyper Drive) and I installed
  Ubuntu 20.04. At one point in time my headset was working (connected
  to USB) but about 2 weeks ago it stopped working after an upgrade. It
  doesn't work not even connecting it to the headphone jack. I have gone
  into the Settings and even though my device appears to be detected the
  configuration doesn't seem to take place. The audio keep coming out
  the standard output (speakers). It simply does not respect the
  settings. Even when I click on the two buttons to (TEST LEFT and TEST
  RIGHT) with my headset selected as the output device the sound still
  comes out the speakers. Is this a known issue?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1867330/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-03-13 Thread Michael Reiger

I am back on Kernel 5.3.0-40.

That would explain my microphone troubles.
Will try out the new version when it is -proposed and give feedback.

Thank you for the good work!

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

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

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions

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

[Touch-packages] [Bug 1866996] Re: apport-retrace can not be used with https mirrors in sources.list

2020-03-13 Thread Esokrates

@Brian: Thanks for merging the patch. As for reproducing the https
issue: The issue happens if ALL entries in fstab are https mirrors, like

deb https://mirror.init7.net/ubuntu/ focal main restricted universe multiverse
deb-src https://mirror.init7.net/ubuntu/ focal main restricted universe 
multiverse

deb https://mirror.init7.net/ubuntu/ focal-updates main restricted universe 
multiverse
deb-src https://mirror.init7.net/ubuntu/ focal-updates main restricted universe 
multiverse

deb https://mirror.init7.net/ubuntu/ focal-backports main restricted universe 
multiverse
deb-src https://mirror.init7.net/ubuntu/ focal-backports main restricted 
universe multiverse

deb https://mirror.init7.net/ubuntu/ focal-security main restricted universe 
multiverse
deb-src https://mirror.init7.net/ubuntu/ focal-security main restricted 
universe multiverse

The you will be 100% able to reproduce the error.

As for the other issues
1. Did you try to retrace my texstudio crash on focal machine in sandbox mode?
2. Did you obtain a backtrace without missing symboles?

As I mentioned in comment #2 just retracing the crash file with
apport-retrace -v -s -R -S system _usr_bin_texstudio.1000.crash gives me the 
following useless stack trace:

--- stack trace ---
#0 0x7fa95a8273eb in ?? ()
No symbol table info available.
#1 0x in ?? ()
No symbol table info available.
--- source code stack trace ---
#0 0x7fa95a8273eb in ?? ()
#1 0x in ?? ()

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

Title:
  apport-retrace can not be used with https mirrors in sources.list

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  Here I collect a couple of issues regarding apport-retrace with "-S
  system".

  1. apport-retrace does not work for https mirros in sources.list
  2. If the sandbox is built successfully the stack-trace of generated does 
even contain less info than simply calling "apport-retrace -v -s -R" without 
the sandbox.
  3. I have found fixes / workaround for issue 1. and 2., see the attached 
patches, however in the end I'm still not satisfied with the quality of the 
results:

  For example I tested apport by invoking a crash of gnome-software with kill 
-s SIGSEGV $(pidof gnome-software).
 
  Invoking apport-retrace without sandbox (apport-retrace -R --stdout 
_usr_bin_gnome-software.1000.crash) gives me the following backtrace:

  --- stack trace ---
  #0  0x7f3e39555c3f in __GI___poll (fds=0x55b072be60f0, nfds=3, 
timeout=6816) at ../sysdeps/unix/sysv/linux/poll.c:29
  resultvar = 18446744073709551100
  sc_cancel_oldtype = 0
  sc_ret = 
  #1  0x7f3e3a4b21ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f3e3a4b22e3 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f3e3a362ec5 in g_application_run () from 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #4  0x55b07218ed59 in main ()
  No symbol table info available.
  --- source code stack trace ---
  #0  0x7f3e39555c3f in __GI___poll (fds=0x55b072be60f0, nfds=3, 
timeout=6816) at ../sysdeps/unix/sysv/linux/poll.c:29
[Error: poll.c was not found in source tree]
  #1  0x7f3e3a4b21ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7f3e3a4b22e3 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7f3e3a362ec5 in g_application_run () from 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #4  0x55b07218ed59 in main ()

  Invoking apport-retrace with sandbox (apport-retrace -v -s -R -S
  system _usr_bin_gnome-software.1000.crash) gives me the following
  (which is not much better):

  --- stack trace ---
  #0  0x7f3e39555c3f in poll () from /lib/x86_64-linux-gnu/libc.so.6
  No symbol table info available.
  #1  0x7f3e3a4b21ae in g_main_context_iterate.isra () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f3e3a4b22e3 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f3e3a362ec5 in g_application_run (application=0x55b072bbd0f0, 
argc=, argv=) at ../../../gio/gapplication.c:2559
  arguments = 0x55b072be60d0
  status = 0
  context = 0x55b072be6130
  acquired_context = 1
  __func__ = "g_application_run"
  #4  0x55b07218ed59 in main ()
  No symbol table info available.
  --- source code stack trace ---
  #0  0x7f3e39555c3f in poll () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7f3e3a4b21ae in g_main_context_iterate.isra () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7f3e3a4b22e3 in g_main_context_iteration () from

[Touch-packages] [Bug 1867319] Re: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories"

2020-03-13 Thread leonardo

Edit on the previous comments, the processes are not owned by the user,
processes are owned by root but ps  returns several lines like:

/usr/lib/policykit-1/polkit-agent-helper-1 USERNAME

where USERNAME is the user that gets stuck

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

Title:
  Can not access desktop after switching user: stuck at "authentication
  required to refresh system repositories"

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When switching from the user (sudo-enabled) I normally use to another one 
(which I rarely use, and is also sudo-enabled), I can not access the desktop. 
  A window opens blocking the whole screen and asking the user password (the 
second user), whatever I type, the window does not close (see screenshot). In 
some cases after a random number of times I push "cancel" the window 
disappears, but not all the times.

  
  Steps to reproduce the bug:
   - switch from user A to user B
   - enter password in gdm, log-in is successful
   - update window opens and never disappears. I can not access the desktop.

  To exit this situation I need to change desktop with CTRL+ALT+F4 and
  log-in again with user A, which works. If I switch to user B again I
  am stuck again.

  Note that after this happens, I updated/upgraded repositories using
  user A and the window will be still there when switching to user B.

  
  What you expected to happen:
   - If I enter the user password the window should do something (start 
updating) but instead it produces an error (something on the line "This did not 
work") and the window remains there
   - If I push "cancel" the window remains there, only in some cases it did 
disappear after clicking cancel many times (tens of times)

  I'v seen this page describing something similar, but I don't have xRDP
  installed

  https://c-nergy.be/blog/?p=14051

  $ dpkg -l| grep -i xrdp
  $ 


  Ubuntu Version: packages updated to March 13 2020.
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  GNOME: 3.34.2
  Graphics: Intel UHD Graphics (Whiskey Lake 3x8 GT2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1867319/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

2020-03-13 Thread Efthimios Chaskaris

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

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in software-properties package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1867319] Re: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories"

2020-03-13 Thread leonardo

I see that the user has tens of /usr/lib/policykit-1/polkit-agent-
helper-1 processes running, which seems to be part of the policykit-1
package


** Package changed: ubuntu => policykit-1 (Ubuntu)

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

Title:
  Can not access desktop after switching user: stuck at "authentication
  required to refresh system repositories"

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When switching from the user (sudo-enabled) I normally use to another one 
(which I rarely use, and is also sudo-enabled), I can not access the desktop. 
  A window opens blocking the whole screen and asking the user password (the 
second user), whatever I type, the window does not close (see screenshot). In 
some cases after a random number of times I push "cancel" the window 
disappears, but not all the times.

  
  Steps to reproduce the bug:
   - switch from user A to user B
   - enter password in gdm, log-in is successful
   - update window opens and never disappears. I can not access the desktop.

  To exit this situation I need to change desktop with CTRL+ALT+F4 and
  log-in again with user A, which works. If I switch to user B again I
  am stuck again.

  Note that after this happens, I updated/upgraded repositories using
  user A and the window will be still there when switching to user B.

  
  What you expected to happen:
   - If I enter the user password the window should do something (start 
updating) but instead it produces an error (something on the line "This did not 
work") and the window remains there
   - If I push "cancel" the window remains there, only in some cases it did 
disappear after clicking cancel many times (tens of times)

  I'v seen this page describing something similar, but I don't have xRDP
  installed

  https://c-nergy.be/blog/?p=14051

  $ dpkg -l| grep -i xrdp
  $ 


  Ubuntu Version: packages updated to March 13 2020.
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  GNOME: 3.34.2
  Graphics: Intel UHD Graphics (Whiskey Lake 3x8 GT2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1867319/+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 1867319] [NEW] Can not access desktop after switching user: stuck at "authentication required to refresh system repositories"