[Touch-packages] [Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs

[Seth Arnold]

Hello Dan and Matthew, thanks for working on this. I gave the debdiffs a
look, skimmed through openssl changes, and don't see any reason to not
do this. There *are* larger changes to that function in
https://github.com/openssl/openssl/commit/1e41dadfa7b9f792ed0f4714a3d3d36f070cf30e
-- but it's a fairly invasive change, and I'm not recommending or
suggesting we take it instead. It'd be nice though if someone could
double-check the certs in question against a build that uses this newer
commit and make sure that we're not backporting a very short-lived
functional change.

Thanks

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

Title:
  x509 Certificate verification fails when
  basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  In Progress
Status in openssl source package in Groovy:
  In Progress
Status in openssl source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In openssl 1.1.1f, the below commit was merged:

  commit ba4356ae4002a04e28642da60c551877eea804f7
  Author: Bernd Edlinger 
  Date:   Sat Jan 4 15:54:53 2020 +0100
  Subject: Fix error handling in x509v3_cache_extensions and related functions
  Link: 
https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7

  This introduced a regression which caused certificate validation to
  fail when certificates violate RFC 5280 [1], namely, when a
  certificate has "basicConstraints=CA:FALSE,pathlen:0". This
  combination is commonly seen by self-signed leaf certificates with an
  intermediate CA before the root CA.

  Because of this, openssl 1.1.1f rejects these certificates and they
  cannot be used in the system certificate store, and ssl connections
  fail when you try to use them to connect to a ssl endpoint.

  The error you see when you try verify is:

  $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem 
user1_cert.pem
  error 20 at 0 depth lookup: unable to get local issuer certificate
  error user1_cert.pem: verification failed

  The exact same certificates work fine on Xenial, Bionic and Hirsute.

  [1] https://tools.ietf.org/html/rfc5280.html

  [Testcase]

  We will create our own root CA, intermediate CA and leaf server
  certificate.

  Create necessary directories:

  $ mkdir reproducer
  $ cd reproducer
  $ mkdir CA

  Write openssl configuration files to disk for each CA and cert:

  $ cat << EOF >> rootCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Root-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> subCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Sub-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE,pathlen:0
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> user.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test User

  [ usr_cert ]
  basicConstraints= critical,CA:FALSE,pathlen:0
  keyUsage= critical,digitalSignature,keyAgreement
  extendedKeyUsage= clientAuth,serverAuth
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  Then generate the necessary RSA keys and form certificates:

  $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes 
-x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1

  $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem 
-sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey 
rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt 
-CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ c_rehash CA

  $ openssl genpkey -algorithm RSA-PSS -out user1_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config user.cnf -new -out user1_req.pem -key user1_key.pem 
-sigopt 

[Touch-packages] [Bug 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)

[Harrison Chen]

Update: still affects 21.04 and the above Reddit solution no longer
works for me

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

Title:
  Sound card not detected on Dell Latitude 9510 (Realtek ALC711)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem
  (checked via uname -r).

  
  I believe my sound card is not being detected by Ubuntu.  I checked the 
serial number and via BIOS (which I've upgraded to the latest version) 
according to the specs 
(https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf)
 the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D.

  However, when I run lspci only the following device appears:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:02c8]

  In alsamixer, only the HDMI port appears.

  alsa-info output: http://alsa-
  project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1926815] Re: gdb 'call' / 'print' commands don't work properly when attaching to R

[Kevin Ushey]

** Summary changed:

- gdb doesn't work properly when attaching to R
+ gdb 'call' / 'print' commands don't work properly when attaching to R

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

Title:
  gdb 'call' / 'print' commands don't work properly when attaching to R

Status in gdb package in Ubuntu:
  New

Bug description:
  Sorry for the somewhat weird / vague title; hopefully the rest of this
  issue will make it more concrete ...

  First, to set the stage; gdb and R both installed from apt
  repositories:

  $ /usr/bin/gdb --version
  GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  $ /usr/bin/R --version
  R version 4.0.5 (2021-03-31) -- "Shake and Throw"
  Copyright (C) 2021 The R Foundation for Statistical Computing
  Platform: x86_64-pc-linux-gnu (64-bit)

  R is free software and comes with ABSOLUTELY NO WARRANTY.
  You are welcome to redistribute it under the terms of the
  GNU General Public License versions 2 or 3.
  For more information about these matters see
  https://www.gnu.org/licenses/.

  Now, I can use gdb in batch mode to introspect a bash process; e.g.
  print the SHELL environment variable:

  $ /usr/bin/gdb -batch -p $(pgrep -nx bash) -ex 'print (char*) getenv("SHELL")'
  0x7f5623d8c1db in __pselect (nfds=1, readfds=0x7ffdaeda52f0, 
writefds=0x0, exceptfds=0x0, timeout=, sigmask=0x5615fe778140 
<_rl_orig_sigset>) at ../sysdeps/unix/sysv/linux/pselect.c:48
  48  ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
  $1 = 0x5615ffc825d0 "/bin/bash"
  [Inferior 1 (process 640102) detached]

  
  But, if I try to do the same with a running R process, I see:

  $ R -s -e "Sys.sleep(100)" &
  [1] 643585

  $ /usr/bin/gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7f47944050da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
  Invalid character '"' in expression.
  [Inferior 1 (process 643585) detached]

  
  Note the very confusing 'Invalid character '"' in expression.' error, 
implying that gdb was for some reason unable to handle the double-quoted string 
passed to getenv().

  I cannot reproduce this in a version of gdb 9.2 built from sources
  locally; e.g.

  $ gdb --version
  GNU gdb (GDB) 9.2
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  $ gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fba31ad60da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
  $1 = 0x7fff4dc9adfe "/bin/bash"
  [Inferior 1 (process 701827) detached]

  So it seems like something specifically is broken in the version of
  GDB packaged for Ubuntu 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1926815/+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 1926686] Re: lightdm segfaults

[Gunnar Hjalmarsson]

OTOH... If you haven't enabled the guest session feature, the difference
between the lightdm versions in focal-release and focal-proposed can't
possibly cause the segfault.

Did you possibly install everything from focal-proposed? In that case
you may be actually 'testing' this upload:

https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.3

After all the error message includes "error 4 in libc-2.31.so".

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

Title:
  lightdm segfaults

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip
  7f7260003f0b sp 7fffbb5a0600 error 4 in
  libc-2.31.so[7f725ff8e000+178000]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  Uname: Linux 5.10.32 x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 29 20:55:18 2021
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+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 1926686] Re: lightdm segfaults

[Gunnar Hjalmarsson]

On 2021-04-30 23:59, Robert Dinse wrote:
> I was under the impression that the purpose of proposed was to test
> and get feedback and fix such things before it entered mainstream.

It is, but such testing happens normally via dedicated bug reports. As
regards the current lightdm version in -proposed that is bug #1921655.

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

Title:
  lightdm segfaults

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip
  7f7260003f0b sp 7fffbb5a0600 error 4 in
  libc-2.31.so[7f725ff8e000+178000]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  Uname: Linux 5.10.32 x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 29 20:55:18 2021
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+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 1926815] Re: gdb doesn't work properly when attaching to R

[Kevin Ushey]

In addition, I get a segfault if I use a single-quoted string rather
than a double-quoted string. (My understanding is that single-quoted
strings are normally used to reference symbols, so this should be an
error but not a crash)

$ /usr/bin/gdb -batch -p $(pgrep -nx R) -ex "print (char*) getenv('oops')"
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f69b4c870da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
Aborted (core dumped)

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

Title:
  gdb doesn't work properly when attaching to R

Status in gdb package in Ubuntu:
  New

Bug description:
  Sorry for the somewhat weird / vague title; hopefully the rest of this
  issue will make it more concrete ...

  First, to set the stage; gdb and R both installed from apt
  repositories:

  $ /usr/bin/gdb --version
  GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  $ /usr/bin/R --version
  R version 4.0.5 (2021-03-31) -- "Shake and Throw"
  Copyright (C) 2021 The R Foundation for Statistical Computing
  Platform: x86_64-pc-linux-gnu (64-bit)

  R is free software and comes with ABSOLUTELY NO WARRANTY.
  You are welcome to redistribute it under the terms of the
  GNU General Public License versions 2 or 3.
  For more information about these matters see
  https://www.gnu.org/licenses/.

  Now, I can use gdb in batch mode to introspect a bash process; e.g.
  print the SHELL environment variable:

  $ /usr/bin/gdb -batch -p $(pgrep -nx bash) -ex 'print (char*) getenv("SHELL")'
  0x7f5623d8c1db in __pselect (nfds=1, readfds=0x7ffdaeda52f0, 
writefds=0x0, exceptfds=0x0, timeout=, sigmask=0x5615fe778140 
<_rl_orig_sigset>) at ../sysdeps/unix/sysv/linux/pselect.c:48
  48  ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
  $1 = 0x5615ffc825d0 "/bin/bash"
  [Inferior 1 (process 640102) detached]

  
  But, if I try to do the same with a running R process, I see:

  $ R -s -e "Sys.sleep(100)" &
  [1] 643585

  $ /usr/bin/gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7f47944050da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
  Invalid character '"' in expression.
  [Inferior 1 (process 643585) detached]

  
  Note the very confusing 'Invalid character '"' in expression.' error, 
implying that gdb was for some reason unable to handle the double-quoted string 
passed to getenv().

  I cannot reproduce this in a version of gdb 9.2 built from sources
  locally; e.g.

  $ gdb --version
  GNU gdb (GDB) 9.2
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  $ gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fba31ad60da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
  $1 = 0x7fff4dc9adfe "/bin/bash"
  [Inferior 1 (process 701827) detached]

  So it seems like something specifically is broken in the version of
  GDB packaged for Ubuntu 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1926815/+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 1926815] [NEW] gdb doesn't work properly when attaching to R

[Kevin Ushey]

Public bug reported:

Sorry for the somewhat weird / vague title; hopefully the rest of this
issue will make it more concrete ...

First, to set the stage; gdb and R both installed from apt repositories:

$ /usr/bin/gdb --version
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ /usr/bin/R --version
R version 4.0.5 (2021-03-31) -- "Shake and Throw"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under the terms of the
GNU General Public License versions 2 or 3.
For more information about these matters see
https://www.gnu.org/licenses/.

Now, I can use gdb in batch mode to introspect a bash process; e.g.
print the SHELL environment variable:

$ /usr/bin/gdb -batch -p $(pgrep -nx bash) -ex 'print (char*) getenv("SHELL")'
0x7f5623d8c1db in __pselect (nfds=1, readfds=0x7ffdaeda52f0, writefds=0x0, 
exceptfds=0x0, timeout=, sigmask=0x5615fe778140 
<_rl_orig_sigset>) at ../sysdeps/unix/sysv/linux/pselect.c:48
48  ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
$1 = 0x5615ffc825d0 "/bin/bash"
[Inferior 1 (process 640102) detached]


But, if I try to do the same with a running R process, I see:

$ R -s -e "Sys.sleep(100)" &
[1] 643585

$ /usr/bin/gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f47944050da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
Invalid character '"' in expression.
[Inferior 1 (process 643585) detached]


Note the very confusing 'Invalid character '"' in expression.' error, implying 
that gdb was for some reason unable to handle the double-quoted string passed 
to getenv().

I cannot reproduce this in a version of gdb 9.2 built from sources
locally; e.g.

$ gdb --version
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fba31ad60da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
$1 = 0x7fff4dc9adfe "/bin/bash"
[Inferior 1 (process 701827) detached]

So it seems like something specifically is broken in the version of GDB
packaged for Ubuntu 20.04.

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

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

Title:
  gdb doesn't work properly when attaching to R

Status in gdb package in Ubuntu:
  New

Bug description:
  Sorry for the somewhat weird / vague title; hopefully the rest of this
  issue will make it more concrete ...

  First, to set the stage; gdb and R both installed from apt
  repositories:

  $ /usr/bin/gdb --version
  GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  $ /usr/bin/R --version
  R version 4.0.5 (2021-03-31) -- "Shake and Throw"
  Copyright (C) 2021 The R Foundation for Statistical Computing
  Platform: x86_64-pc-linux-gnu (64-bit)

  R is free software and comes with ABSOLUTELY NO WARRANTY.
  You are welcome to redistribute it under the terms of the
  GNU General Public License versions 2 or 3.
  For more information about these matters see
  https://www.gnu.org/licenses/.

  Now, I can use gdb in batch mode to introspect a bash process; e.g.
  print the SHELL environment variable:

  $ /usr/bin/gdb -batch -p $(pgrep -nx bash) -ex 'print (char*) getenv("SHELL")'
  0x7f5623d8c1db in __pselect (nfds=1, readfds=0x7ffdaeda52f0, 
writefds=0x0, exceptfds=0x0, timeout=, sigmask=0x5615fe778140 
<_rl_orig_sigset>) at ../sysdeps/unix/sysv/linux/pselect.c:48
  48  ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
  $1 = 0x5615ffc825d0 "/bin/bash"
  [Inferior 1 (process 640102) detached]

  
  But, if I try to do the same with a running R process, I see:

  $ R -s -e "Sys.sleep(100)" &
  [1] 643585

  $ /usr/bin/gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 

[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Dimitri John Ledkov]

debdiffs are on https://bileto.ubuntu.com/#/ticket/4543

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules

[Dimitri John Ledkov]

I've rebuilt all the packages mentioned above in bileto ppa against
security pocket and pushed them to focal-proposed queue, ready for sru
review and accept.

All, but openafs which ftbfs now, and will need to be fixed up for v5.11
anyway. So it will be rebuild in security pocket with v5.11 fixes later.

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+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 1926686] Re: lightdm segfaults

[Robert Dinse]

Ok, I've installed the old version to see if this occurs, this was not a
frequent problem with this version so I'm unlikely to have an answer
overnight.  However, I was under the impression that the purpose of
proposed was to test and get feedback and fix such things before it
entered mainstream.

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

Title:
  lightdm segfaults

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip
  7f7260003f0b sp 7fffbb5a0600 error 4 in
  libc-2.31.so[7f725ff8e000+178000]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  Uname: Linux 5.10.32 x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 29 20:55:18 2021
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+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 1926661] Re: i think gpu driver isn't working well.

[Shoyayeb Hasan Shafin]

anyone know how to fix this shit?

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

Title:
  i think gpu driver isn't working well.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  there are some glitch and shuttering on desktop and it have so low
  performance as compared to windows. :(

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 02:18:52 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: rtl8188fu, 1.0, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 4th Generation Core Processor Family 
Integrated Graphics Controller [1849:041e]
  InstallationDate: Installed on 2021-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=39f8b6ac-7465-4bb1-992a-61515406828c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H91M-XT PLUS
  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.:bvrP1.10:bd07/27/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH91M-XTPLUS: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926661/+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 1921518] Re: OpenSSL "double free" error

[Mahantesh Salimath]

** Attachment added: "Core dump file"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+attachment/5493968/+files/core-curl.32878.localhost.localdomain.1619816112

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

Title:
  OpenSSL "double free" error

Status in openssl package in Ubuntu:
  New

Bug description:
  "double free" error is seen when using curl utility. Error is from
  libcrypto.so which is part of the OpenSSL package. This happens only
  when OpenSSL is configured to use a dynamic engine.

  OpenSSL version is 1.1.1f

  The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.

  
  OpenSSL can be configured to use a dynamic engine by editing the default 
openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu 
systems.

  On Bluefield systems, config diff to enable PKA dynamic engine, is as
  below:

  +openssl_conf = conf_section
  +
   # Extra OBJECT IDENTIFIER info:
   #oid_file  = $ENV::HOME/.oid
   oid_section= new_oids
   
  +[ conf_section ]
  +engines = engine_section
  +
  +[ engine_section ]
  +bf = bf_section
  +
  +[ bf_section ]
  +engine_id=pka
  +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
  +init=0
  +

  engine_id above refers to dynamic engine name/identifier.
  dynamic_path points to the .so file for the dynamic engine.

  # curl -O https://tpo.pe/pathogen.vim

  double free or corruption (out)

  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1909830] Re: [USB-Audio - Razer Kraken 7.1 V2, playback] Playback problem | VLC Player works correctly

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [USB-Audio - Razer Kraken 7.1 V2, playback] Playback problem | VLC
  Player works correctly

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  USB Headphones do not play test audio from the "Sound" section of the 
configuration application if either of the following are true:
  3.5mm speakers are plugged into port
  HDMI Monitor is attached to computer

  VLC Media player is able to properly choose and play through the USB 
headphones even if both of the above scenarios occur.
  Removing the HDMI monitor and unplugging the 3.5mm speakers allows the 
headphones to work as expected.

  Rebooting the PC with the USB device plugged in does not make a difference in 
output.
  The "Sound" section of the configuration page shows the list of output 
devices exactly as you would expect.
  Selecting the headphones from the list of output devices and choosing "Test" 
does not produce sound if either of the above conditions are true.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  I will investigate trying to disable my HDMI as an audio device.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  1 13:18:15 2021
  InstallationDate: Installed on 2019-12-11 (387 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:V2 successful
  Symptom_Card: Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 
Series] - HDA ATI HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [USB-Audio - Razer Kraken 7.1 V2, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-27 (248 days ago)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.15.0
  dmi.board.name: 09WH54
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.15.0:bd03/25/2020:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision Tower 3620
  dmi.product.sku: 06B7
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1909830/+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 1926802] Re: qt5-default package is missed in 21.04

[Dmitry Shachnev]

Qt 4 was removed, Qt 5 is now default, so that package is no longer
needed.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  qt5-default package is missed in 21.04

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

Bug description:
  Previous 20.10 version has the qt5-default package in place (see
  https://packages.ubuntu.com/groovy/qt5-default ).

  Please upload the  qt5-default package for 21.04 Ubuntu version.

  What is interesting - all its dependencies can be simply installed
  with `sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5
  -dev-tools` .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+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 1926794] Re: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade:
  11.0957:dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Automatic upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu4.8
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Fri Apr 30 17:25:11 2021
  DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu4.8:11.0957:dependency 
problems - leaving triggers unprocessed
  ErrorMessage: 11.0957:dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2021-04-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.7
   apt  1.2.35
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 
11.0957:dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2021-04-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926794/+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 1926794] Re: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed

[Ubuntu Foundations Team Bug Bot]

** Attachment removed: "VarLogDistupgradeTermlog.gz"
   
https://bugs.launchpad.net/bugs/1926794/+attachment/5493933/+files/VarLogDistupgradeTermlog.gz

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

Title:
  package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade:
  11.0957:dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Automatic upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu4.8
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Fri Apr 30 17:25:11 2021
  DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu4.8:11.0957:dependency 
problems - leaving triggers unprocessed
  ErrorMessage: 11.0957:dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2021-04-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.7
   apt  1.2.35
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 
11.0957:dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2021-04-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926794/+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 1920837] Re: apport bugs from official raspi or riscv images are not identified

[William Wilson]

The verification passed for groovy:

ubuntu@ubuntu:~$ apt-cache policy apport
apport:
  Installed: 2.20.11-0ubuntu50.5
  Candidate: 2.20.11-0ubuntu50.6
  Version table:
 2.20.11-0ubuntu50.6 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 
Packages
 *** 2.20.11-0ubuntu50.5 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
500 http://ports.ubuntu.com/ubuntu-ports groovy-security/main arm64 
Packages
100 /var/lib/dpkg/status
 2.20.11-0ubuntu50 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

`ubuntu-bug apport` shows 
== Tags =
 groovy uec-images

ubuntu@ubuntu:~$ sudo apt install apport
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  python3-apport
Suggested packages:
  apport-gtk | apport-kde
The following packages will be upgraded:
  apport python3-apport
2 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
Need to get 214 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 
python3-apport all 2.20.11-0ubuntu50.6 [85.2 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 apport 
all 2.20.11-0ubuntu50.6 [129 kB]
Fetched 214 kB in 1s (258 kB/s)
(Reading database ... 101926 files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.11-0ubuntu50.6_all.deb ...
Unpacking python3-apport (2.20.11-0ubuntu50.6) over (2.20.11-0ubuntu50.5) ...
Preparing to unpack .../apport_2.20.11-0ubuntu50.6_all.deb ...
Unpacking apport (2.20.11-0ubuntu50.6) over (2.20.11-0ubuntu50.5) ...
Setting up python3-apport (2.20.11-0ubuntu50.6) ...
Setting up apport (2.20.11-0ubuntu50.6) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for systemd (246.6-1ubuntu1.3) ...

`ubuntu-bug apport` shows
== Tags =
 arm64-image raspi-image groovy uec-images package-from-proposed

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

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

Title:
  apport bugs from official raspi or riscv images are not identified

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  It would be helpful if bugs reported from images for Raspberry Pi's or
  RISCV systems were tagged so that one could search for bugs from
  systems running those images e.g. 'raspi-image'.

  [Test Case]
  After installing a preinstalled image of Ubuntu for Raspberry Pi do the 
following:
  1) run 'ubuntu-bug apport'
  2) view the bug report and check the Tags field

  With the current version of apport you will not see the tag 'raspi-image'.
  With the version of apport in -proposed you will see the tag 'raspi-image'.

  [Where problems could occur]
  If the code being added is syntactically incorrect then we'd see a Traceback 
which would be bad as it could affect all bug / crash reports.

  [Other Info]
  Since there aren't any Groovy images for RISC-V there will be nothing to test 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1921518] Re: OpenSSL "double free" error

[Mahantesh Salimath]

** Description changed:

  "double free" error is seen when using curl utility. Error is from
  libcrypto.so which is part of the OpenSSL package. This happens only
  when OpenSSL is configured to use a dynamic engine.
  
  OpenSSL version is 1.1.1f
  
- This issue is not encountered if
+ The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.
+ 
+ 
+ OpenSSL can be configured to use a dynamic engine by editing the default 
openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu 
systems.
+ 
+ On Bluefield systems, config diff to enable PKA dynamic engine, is as
+ below:
+ 
+ +openssl_conf = conf_section
+ +
+  # Extra OBJECT IDENTIFIER info:
+  #oid_file  = $ENV::HOME/.oid
+  oid_section= new_oids
+  
+ +[ conf_section ]
+ +engines = engine_section
+ +
+ +[ engine_section ]
+ +bf = bf_section
+ +
+ +[ bf_section ]
+ +engine_id=pka
+ +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
+ +init=0
+ +
+ 
+ engine_id above refers to dynamic engine name/identifier.
+ dynamic_path points to the .so file for the dynamic engine.
  
  # curl -O https://tpo.pe/pathogen.vim
  
  double free or corruption (out)
  
  Aborted (core dumped)

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

Title:
  OpenSSL "double free" error

Status in openssl package in Ubuntu:
  New

Bug description:
  "double free" error is seen when using curl utility. Error is from
  libcrypto.so which is part of the OpenSSL package. This happens only
  when OpenSSL is configured to use a dynamic engine.

  OpenSSL version is 1.1.1f

  The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.

  
  OpenSSL can be configured to use a dynamic engine by editing the default 
openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu 
systems.

  On Bluefield systems, config diff to enable PKA dynamic engine, is as
  below:

  +openssl_conf = conf_section
  +
   # Extra OBJECT IDENTIFIER info:
   #oid_file  = $ENV::HOME/.oid
   oid_section= new_oids
   
  +[ conf_section ]
  +engines = engine_section
  +
  +[ engine_section ]
  +bf = bf_section
  +
  +[ bf_section ]
  +engine_id=pka
  +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
  +init=0
  +

  engine_id above refers to dynamic engine name/identifier.
  dynamic_path points to the .so file for the dynamic engine.

  # curl -O https://tpo.pe/pathogen.vim

  double free or corruption (out)

  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs

[Dan Streetman]

added ubuntu-security to the bug, just for quick review to make sure
they don't object to the patch

I can sponsor this to -updates if there's no objection

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

Title:
  x509 Certificate verification fails when
  basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  In Progress
Status in openssl source package in Groovy:
  In Progress
Status in openssl source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In openssl 1.1.1f, the below commit was merged:

  commit ba4356ae4002a04e28642da60c551877eea804f7
  Author: Bernd Edlinger 
  Date:   Sat Jan 4 15:54:53 2020 +0100
  Subject: Fix error handling in x509v3_cache_extensions and related functions
  Link: 
https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7

  This introduced a regression which caused certificate validation to
  fail when certificates violate RFC 5280 [1], namely, when a
  certificate has "basicConstraints=CA:FALSE,pathlen:0". This
  combination is commonly seen by self-signed leaf certificates with an
  intermediate CA before the root CA.

  Because of this, openssl 1.1.1f rejects these certificates and they
  cannot be used in the system certificate store, and ssl connections
  fail when you try to use them to connect to a ssl endpoint.

  The error you see when you try verify is:

  $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem 
user1_cert.pem
  error 20 at 0 depth lookup: unable to get local issuer certificate
  error user1_cert.pem: verification failed

  The exact same certificates work fine on Xenial, Bionic and Hirsute.

  [1] https://tools.ietf.org/html/rfc5280.html

  [Testcase]

  We will create our own root CA, intermediate CA and leaf server
  certificate.

  Create necessary directories:

  $ mkdir reproducer
  $ cd reproducer
  $ mkdir CA

  Write openssl configuration files to disk for each CA and cert:

  $ cat << EOF >> rootCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Root-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> subCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Sub-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE,pathlen:0
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> user.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test User

  [ usr_cert ]
  basicConstraints= critical,CA:FALSE,pathlen:0
  keyUsage= critical,digitalSignature,keyAgreement
  extendedKeyUsage= clientAuth,serverAuth
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  Then generate the necessary RSA keys and form certificates:

  $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes 
-x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1

  $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem 
-sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey 
rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt 
-CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ c_rehash CA

  $ openssl genpkey -algorithm RSA-PSS -out user1_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config user.cnf -new -out user1_req.pem -key user1_key.pem 
-sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ openssl x509 -req -sha256 -in user1_req.pem -CA CA/subCA_cert.pem -CAkey 
subCA_key.pem -out user1_cert.pem -CAserial subCA_serial.txt -CAcreateserial 
-extfile user.cnf -extensions usr_cert -days 1825 -sigopt rsa_padding_mode:pss 
-sigopt rsa_pss_saltlen:-1

  Now, let's try verify the generated certificates:

  $ openssl version
  OpenSSL 1.1.1f  31 Mar 2020
  $ openssl verify 

[Touch-packages] [Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified

[William Wilson]

The verification passed for focal:

ubuntu@ubuntu:~$ apt-cache policy apport
apport:
  Installed: 2.20.11-0ubuntu27.16
  Candidate: 2.20.11-0ubuntu27.17
  Version table:
 2.20.11-0ubuntu27.17 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf 
Packages
 *** 2.20.11-0ubuntu27.16 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf 
Packages
500 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf 
Packages
100 /var/lib/dpkg/status
 2.20.11-0ubuntu27 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages

`ubuntu-bug apport` shows:
== Tags =
 focal uec-images

ubuntu@ubuntu:~$ sudo apt install apport
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  python3-apport
Suggested packages:
  apport-gtk | apport-kde
The following packages will be upgraded:
  apport python3-apport
2 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
Need to get 214 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf 
python3-apport all 2.20.11-0ubuntu27.17 [85.2 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf apport all 
2.20.11-0ubuntu27.17 [129 kB]
Fetched 214 kB in 1s (247 kB/s)
(Reading database ... 99636 files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.11-0ubuntu27.17_all.deb ...
Unpacking python3-apport (2.20.11-0ubuntu27.17) over (2.20.11-0ubuntu27.16) ...
Preparing to unpack .../apport_2.20.11-0ubuntu27.17_all.deb ...
Unpacking apport (2.20.11-0ubuntu27.17) over (2.20.11-0ubuntu27.16) ...
Setting up python3-apport (2.20.11-0ubuntu27.17) ...
Setting up apport (2.20.11-0ubuntu27.17) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for systemd (245.4-4ubuntu3.6) ...

`ubuntu-bug apport` shows
== Tags =
 armhf-image raspi-image focal uec-images package-from-proposed

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

Title:
  apport bugs from official raspi or riscv images are not identified

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  It would be helpful if bugs reported from images for Raspberry Pi's or
  RISCV systems were tagged so that one could search for bugs from
  systems running those images e.g. 'raspi-image'.

  [Test Case]
  After installing a preinstalled image of Ubuntu for Raspberry Pi do the 
following:
  1) run 'ubuntu-bug apport'
  2) view the bug report and check the Tags field

  With the current version of apport you will not see the tag 'raspi-image'.
  With the version of apport in -proposed you will see the tag 'raspi-image'.

  [Where problems could occur]
  If the code being added is syntactically incorrect then we'd see a Traceback 
which would be bad as it could affect all bug / crash reports.

  [Other Info]
  Since there aren't any Groovy images for RISC-V there will be nothing to test 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

[JohnDoe_71Rus]

when we can wait for the update?

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

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Fedora:
  Confirmed

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1915870/+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 1926624] Re: failed to start commit a transient machine-id on disk

[Dan Streetman]

how did you install the system onto the usb stick? that service
shouldn't run during normal boots.

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

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

Title:
  failed to start commit a transient machine-id on disk

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hello.
  I installed the Hirsute Hippo version (21.04) in a partition of a USB stick. 
The boot is slow. This is certainly normal. But a lot of "time-out" messages 
are reported in the log. The first one met
  is "failed to start commit a transient machine-id on disk".
  I do not know that they will be the consequences. Is it possible to configure 
the waiting time?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926624/+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 1926802] [NEW] qt5-default package is missed in 21.04

[Norbert]

Public bug reported:

Previous 20.10 version has the qt5-default package in place (see
https://packages.ubuntu.com/groovy/qt5-default ).

Please upload the  qt5-default package for 21.04 Ubuntu version.

What is interesting - all its dependencies can be simply installed with
`sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools`
.

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


** Tags: hirsute

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

Title:
  qt5-default package is missed in 21.04

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

Bug description:
  Previous 20.10 version has the qt5-default package in place (see
  https://packages.ubuntu.com/groovy/qt5-default ).

  Please upload the  qt5-default package for 21.04 Ubuntu version.

  What is interesting - all its dependencies can be simply installed
  with `sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5
  -dev-tools` .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+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 1926796] [NEW] [SRU] Enable support for Xena Cloud Archive

[Corey Bryant]

Public bug reported:

Please add support for:

   cloud-archive:xena
   cloud-archive:xena-proposed

This will also need to be SRU'd back to focal.

[Impact]
End users have to manually enable the xena cloud archive pockets.

[Test case]
sudo add-apt-repository cloud-archive:xena
sudo add-apt-repository cloud-archive:xena-proposed

[Regression potential]
Limited - just a data item addition

** Affects: software-properties (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: software-properties (Ubuntu Focal)
 Importance: High
 Status: Triaged

** Affects: software-properties (Ubuntu Impish)
 Importance: High
 Status: Triaged

** Also affects: software-properties (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  [SRU] Enable support for Xena Cloud Archive

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Focal:
  Triaged
Status in software-properties source package in Impish:
  Triaged

Bug description:
  Please add support for:

 cloud-archive:xena
 cloud-archive:xena-proposed

  This will also need to be SRU'd back to focal.

  [Impact]
  End users have to manually enable the xena cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:xena
  sudo add-apt-repository cloud-archive:xena-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1926796/+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 1926658] Re: initramfs-tools 0.140ubuntu1 causes failure to boot due to /usr/share/initramfs-tools/init not being executable

[Michael Marley]

Fixed in 0.140ubuntu2.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Fix Released

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

Title:
  initramfs-tools 0.140ubuntu1 causes failure to boot due to /usr/share
  /initramfs-tools/init not being executable

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  After updating the initramfs-tools 0.140ubuntu1, the system no longer
  boots.  Instead, the busybox shell is started.  The error says that
  "/init" cannot be started due to error -13.

  In investigated and figured out that the error occurs because the
  /usr/share/initramfs-tools/init script is not executable.  It was
  executable in previous initramfs-tools versions.  "chmod +x"ing it and
  rebuilding the initramfs works around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1926658/+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 1926794] [NEW] package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed

[Ian Bultitude]

Public bug reported:

Automatic upgrade failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-0 2.48.2-0ubuntu4.8
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
Date: Fri Apr 30 17:25:11 2021
DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu4.8:11.0957:dependency 
problems - leaving triggers unprocessed
ErrorMessage: 11.0957:dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2021-04-30 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.7
 apt  1.2.35
SourcePackage: glib2.0
Title: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 
11.0957:dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2021-04-30 (0 days ago)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package dist-upgrade i386 need-duplicate-check xenial

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

Title:
  package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade:
  11.0957:dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Automatic upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu4.8
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Fri Apr 30 17:25:11 2021
  DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu4.8:11.0957:dependency 
problems - leaving triggers unprocessed
  ErrorMessage: 11.0957:dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2021-04-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.7
   apt  1.2.35
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 
11.0957:dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2021-04-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926794/+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 1926784] [NEW] package libpng12-0 (not installed) failed to install/upgrade: impossible d'installer une nouvelle version de « /lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier

[Yves le Doeuff]

Public bug reported:

Ubuntu installed on a VMWARE (for Windows) virtual machine.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpng12-0 (not installed)
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
AptOrdering:
 libpng12-0:amd64: Install
 libssl1.0.0:amd64: Install
 xfonts-75dpi:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Apr 21 12:44:12 2021
ErrorMessage: impossible d'installer une nouvelle version de « 
/lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type
InstallationDate: Installed on 2021-04-21 (8 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: libpng
Title: package libpng12-0 (not installed) failed to install/upgrade: impossible 
d'installer une nouvelle version de « /lib/x86_64-linux-gnu/libpng12.so.0 »: 
Aucun fichier ou dossier de ce type
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package libpng12-0 (not installed) failed to install/upgrade:
  impossible d'installer une nouvelle version de « /lib/x86_64-linux-
  gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type

Status in libpng package in Ubuntu:
  New

Bug description:
  Ubuntu installed on a VMWARE (for Windows) virtual machine.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpng12-0 (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   libpng12-0:amd64: Install
   libssl1.0.0:amd64: Install
   xfonts-75dpi:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 21 12:44:12 2021
  ErrorMessage: impossible d'installer une nouvelle version de « 
/lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type
  InstallationDate: Installed on 2021-04-21 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: libpng
  Title: package libpng12-0 (not installed) failed to install/upgrade: 
impossible d'installer une nouvelle version de « 
/lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1926784/+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 1926783] [NEW] [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-pitched and distorted

[Michal Lašan]

Public bug reported:

It works normally when playing youtube videos, only audio files on PC are a 
problem.
Also, kernel 5.8.0-50-generic does not have this problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.10
ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 
5.11.13
Uname: Linux 5.11.0-7614-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  michal 1518 F pulseaudio
 /dev/snd/controlC2:  michal 1518 F pulseaudio
 /dev/snd/controlC1:  michal 1518 F pulseaudio
 /dev/snd/pcmC1D0p:   michal 1518 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Fri Apr 30 17:05:38 2021
InstallationDate: Installed on 2021-01-31 (89 days ago)
InstallationMedia:
 
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
Symptom_Card: TU104 HD Audio Controller - HDA NVidia
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: Default string
dmi.board.name: Z390-A PRO (MS-7B98)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7B98
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-pitched
  and distorted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  It works normally when playing youtube videos, only audio files on PC are a 
problem.
  Also, kernel 5.8.0-50-generic does not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.10
  ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 
5.11.13
  Uname: Linux 5.11.0-7614-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michal 1518 F pulseaudio
   /dev/snd/controlC2:  michal 1518 F pulseaudio
   /dev/snd/controlC1:  michal 1518 F pulseaudio
   /dev/snd/pcmC1D0p:   michal 1518 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Fri Apr 30 17:05:38 2021
  InstallationDate: Installed on 2021-01-31 (89 days ago)
  InstallationMedia:
   
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: TU104 HD Audio Controller - HDA NVidia
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390-A PRO (MS-7B98)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B98
  dmi.product.sku: 

[Touch-packages] [Bug 1926305] Re: 20.04 Online Accounts - Google Shared Drives

[max]

Thank you for looking into it.

I appreciate it may not be an easy process.  However corporate
environments will not be upgraded until the next LTS.  This is quite an
important feature for end users and administrators alike.  As a
workaround we use rclone, but to have it all ready to go in the Desktop
environment would really make a big difference.

Just a thought for Canonical to consider.

But thanks again for your help.

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

Title:
  20.04 Online Accounts - Google Shared Drives

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  Just tested out 21.04 and Google Shared Drives works just fine.

  Any chance the 20.04 LTS gnome-online-accounts could be updated to
  support it?

  If that is not possible, any way to build the package from source?

  Patch available here:
  
https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1

  Problem is that building requires dependencies newer than package.
  Tried this with 3-36 as gnome on 20.04 is 3.36
  https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36

  Example error:
  meson.build:305:2: ERROR: Invalid version of dependency, need 
'polkit-gobject-1' ['>= 0.114'] found '0.105'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926305/+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 1926661] Re: i think gpu driver isn't working well.

[Shoyayeb Hasan Shafin]

i can't even use my desktop, properply :(

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

Title:
  i think gpu driver isn't working well.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  there are some glitch and shuttering on desktop and it have so low
  performance as compared to windows. :(

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 02:18:52 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: rtl8188fu, 1.0, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 4th Generation Core Processor Family 
Integrated Graphics Controller [1849:041e]
  InstallationDate: Installed on 2021-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=39f8b6ac-7465-4bb1-992a-61515406828c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H91M-XT PLUS
  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.:bvrP1.10:bd07/27/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH91M-XTPLUS: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926661/+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 1926661] Re: i think gpu driver isn't working well.

[Shoyayeb Hasan Shafin]

** Attachment added: "is it?"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926661/+attachment/5493887/+files/log

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

Title:
  i think gpu driver isn't working well.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  there are some glitch and shuttering on desktop and it have so low
  performance as compared to windows. :(

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 02:18:52 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: rtl8188fu, 1.0, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 4th Generation Core Processor Family 
Integrated Graphics Controller [1849:041e]
  InstallationDate: Installed on 2021-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=39f8b6ac-7465-4bb1-992a-61515406828c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H91M-XT PLUS
  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.:bvrP1.10:bd07/27/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH91M-XTPLUS: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926661/+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 1926770] Re: Bluetooth switches back on each reboot

[Steve Langasek]

** Package changed: shim (Ubuntu) => bluez (Ubuntu)

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

Title:
  Bluetooth switches back on each reboot

Status in bluez package in Ubuntu:
  New

Bug description:
  
  Dear,

  When switching off Bluetooth in the settings menu, after each reboot
  and login into GNOME, the Bluetooth radio stack seems to be switched
  on again.

  Could this setting made by persistent over reboots?

  Thanks,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926770/+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 1926770] [NEW] Bluetooth switches back on each reboot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:


Dear,

When switching off Bluetooth in the settings menu, after each reboot and
login into GNOME, the Bluetooth radio stack seems to be switched on
again.

Could this setting made by persistent over reboots?

Thanks,

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

-- 
Bluetooth switches back on each reboot
https://bugs.launchpad.net/bugs/1926770
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez 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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

[Sebastien Bacher]

@Jeremyszu, backporting the patches that landed upstream in Ubuntu is
alright if it helps you

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1916931] Re: omshell returns inconsistent results or segfaults

[Paweł Moll]

I've noticed that the omshell as shipped in the package is doing bad
things memory access wise...

$ valgrind /usr/bin/omshell 
==735304== Memcheck, a memory error detector
==735304== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==735304== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==735304== Command: /usr/bin/omshell
==735304== 
==735304== Conditional jump or move depends on uninitialised value(s)
==735304==at 0x48760C0: irs_resconf_load (in 
/usr/lib/x86_64-linux-gnu/libirs-export.so.161.0.1)
==735304==by 0x155D67: dhcp_dns_client_setservers (isclib.c:51)
==735304==by 0x15620B: dns_client_init (isclib.c:381)
==735304==by 0x15620B: dns_client_init (isclib.c:354)
==735304==by 0x1562BB: dhcp_context_create (isclib.c:246)
==735304==by 0x114C15: dhcpctl_initialize (dhcpctl.c:45)
==735304==by 0x11374B: main (omshell.c:118)
==735304== 
> connect
==735304== Invalid read of size 8
==735304==at 0x14EC6B: omapi_one_dispatch (dispatch.c:676)
==735304==by 0x14F462: omapi_wait_for_completion (dispatch.c:455)
==735304==by 0x114D62: dhcpctl_connect (dhcpctl.c:115)
==735304==by 0x113F23: main (omshell.c:420)
==735304==  Address 0x7010cf0 is 32 bytes inside a block of size 96 free'd
==735304==at 0x483CA3F: free (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==735304==by 0x14A39F: dfree (alloc.c:203)
==735304==by 0x14A39F: omapi_object_dereference (alloc.c:709)
==735304==by 0x14E1DA: omapi_io_dereference (dispatch.c:39)
==735304==by 0x14E1DA: omapi_unregister_io_object (dispatch.c:410)
==735304==by 0x14B217: omapi_disconnect.part.0 (connection.c:528)
==735304==by 0x14B4C4: omapi_disconnect (connection.c:465)
==735304==by 0x14B4C4: omapi_connection_connect_internal (connection.c:728)
==735304==by 0x14B61C: omapi_connection_connect (connection.c:615)
==735304==by 0x14EC4E: omapi_one_dispatch (dispatch.c:693)
==735304==by 0x14F462: omapi_wait_for_completion (dispatch.c:455)
==735304==by 0x114D62: dhcpctl_connect (dhcpctl.c:115)
==735304==by 0x113F23: main (omshell.c:420)
==735304==  Block was alloc'd at
==735304==at 0x483DD99: calloc (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==735304==by 0x149F11: dmalloc (alloc.c:71)
==735304==by 0x14A094: omapi_object_allocate (alloc.c:543)
==735304==by 0x14: omapi_io_allocate (dispatch.c:39)
==735304==by 0x14: omapi_register_io_object (dispatch.c:223)
==735304==by 0x14BCA7: omapi_connect_list (connection.c:219)
==735304==by 0x14C012: omapi_connect (connection.c:96)
==735304==by 0x146BD6: omapi_protocol_connect (protocol.c:55)
==735304==by 0x114D21: dhcpctl_connect (dhcpctl.c:106)
==735304==by 0x113F23: main (omshell.c:420)
==735304== 
dhcpctl_connect: no more

When I build ISC's dhcpd from their git repository manually, not using
the source package, it works fine. I haven't got to the bottom of it,
though.

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

Title:
  omshell returns inconsistent results or segfaults

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I have just built a Ubuntu 20.04 server and installed isc-dhcp-server
  4.4.1 on it and I am seeing inconsistent returns from omshell. 
  Initially omshell returns data as expected, but when I exit and re-enter 
  omshell connections fail.

  Here is the initial, working, session:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  obj: 
  > new failover-state
  obj: failover-state
  > set name = "dhcp-failover"
  obj: failover-state
  name = "dhcp-failover"
  > open
  obj: failover-state
  name = "dhcp-failover"
  partner-address = c0:9d:e9:76:e9:55:00:00
  partner-port = 00:00:02:07
  local-address = 10:9d:e9:76:e9:55:00:00
  local-port = 00:00:02:07
  max-outstanding-updates = 00:00:00:0a
  mclt = 00:00:01:2c
  load-balance-max-secs = 00:00:00:03
  load-balance-hba =
  
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
  partner-state = 00:00:00:02
  local-state = 00:00:00:02
  partner-stos = 60:36:d0:68
  local-stos = 60:36:8b:3b
  hierarchy = 00:00:00:01
  last-packet-sent = 00:00:00:00
  last-timestamp-received = 00:00:00:00
  skew = 00:00:00:00
  max-response-delay = 00:00:00:3c
  cur-unacked-updates = 00:00:00:00

  Here is what I see when the connect fails.  Well, just hangs really.

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect

  And then I hit ctrl-c to break out and tried again:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  Segmentation fault (core dumped)

  Note, the peer to this server is still running Ubuntu 18.04 with
  isc-dhcp-server 4.3.5.  Running the exact same commands on 

[Touch-packages] [Bug 1926661] Re: i think gpu driver isn't working well.

[Sebastien Bacher]

the log is incomplete, you want to 'journalctl -b 0 > log' and attach
'log' to the report

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

Title:
  i think gpu driver isn't working well.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  there are some glitch and shuttering on desktop and it have so low
  performance as compared to windows. :(

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 02:18:52 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: rtl8188fu, 1.0, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 4th Generation Core Processor Family 
Integrated Graphics Controller [1849:041e]
  InstallationDate: Installed on 2021-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=39f8b6ac-7465-4bb1-992a-61515406828c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H91M-XT PLUS
  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.:bvrP1.10:bd07/27/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH91M-XTPLUS: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926661/+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 1926760] Re: display is flickering and not responsive from login screen

[Sebastien Bacher]

Thank you for your bug report, if that's specific to newer kernels then
it's an issue with the kernel, reassigning to linux

** Package changed: xorg (Ubuntu) => linux (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/1926760

Title:
  display is flickering and not responsive from login screen

Status in linux package in Ubuntu:
  New

Bug description:
  display is flickering and not responsive from login screen, before
  even typing anything.

  This happens with kernels newer than 5.8.0-48-generic, i.e  -49 and
  -50.

  On the occasion I was able to boot in, I was using a recovery mode and
  display was deemed unknown. I am not sure if this is because of
  recovery mode settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 12:33:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation Motherboard [1849:0162]
  InstallationDate: Installed on 2020-07-04 (300 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=3cea77a7-cb0e-4309-8963-651539349612 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: Z77 Extreme4
  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.:bvrP2.00:bd07/13/2012:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926760/+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 1926110] Re: Apps interface flickering

[Md Ayquassar]

After switching from X on groove to wayland on hirsute, I see no
flickering.

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

Title:
  Apps interface flickering

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  It has been 1-ish months since this problem appeared.
  The app/system interface randomly starts flickering. This problem doesn't 
occur on the entire system, sometime it occurs in some apps, other times in the 
system, and other times all of these.
  It occurs since installation.

  Some images and videos (Unfortunetly you'll need to download the videos)
  
https://media.discordapp.net/attachments/748527796405403749/836001618255806484/unknown.png
  
https://media.discordapp.net/attachments/748527796405403749/836004993991311400/unknown.png
  
https://media.discordapp.net/attachments/586951783944028179/832728657075372102/unknown.png
  
https://cdn.discordapp.com/attachments/804416273701797909/832780706790375444/20210416_215049_576x324.mp4
  
https://cdn.discordapp.com/attachments/748527796405403749/836048880592355368/simplescreenrecorder-2021-04-25_22.05.52.mp4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 22:23:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer 3rd Gen Core 
processor Graphics Controller [1297:2027]
  InstallationDate: Installed on 2021-04-17 (9 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Positivo Informatica SA DC8CR01TV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=e2946f04-ffa3-4934-b119-e6dcc363a2da ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.01.U
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DC8CR01TV
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: POSITIVO
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Positivo Informatica SA
  dmi.chassis.version: POSITIVO
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.01.U:bd03/31/2014:br4.6:efr1.22:svnPositivoInformaticaSA:pnDC8CR01TV:pvr2.01.U_POS_TV:rvnPositivoInformaticaSA:rnDC8CR01TV:rvrPOSITIVO:cvnPositivoInformaticaSA:ct13:cvrPOSITIVO:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: DC8CR01TV
  dmi.product.sku: 1700644
  dmi.product.version: 2.01.U_POS_TV
  dmi.sys.vendor: Positivo Informatica SA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926110/+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 1926760] [NEW] display is flickering and not responsive from login screen

[Gonçalo Gomes]

Public bug reported:

display is flickering and not responsive from login screen, before even
typing anything.

This happens with kernels newer than 5.8.0-48-generic, i.e  -49 and -50.

On the occasion I was able to boot in, I was using a recovery mode and
display was deemed unknown. I am not sure if this is because of recovery
mode settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 30 12:33:44 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Motherboard [1849:0162]
InstallationDate: Installed on 2020-07-04 (300 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=3cea77a7-cb0e-4309-8963-651539349612 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.00
dmi.board.name: Z77 Extreme4
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.:bvrP2.00:bd07/13/2012:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4: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.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution third-party-packages ubuntu

** Description changed:

  display is flickering and not responsive from login screen, before even
  typing anything.
  
- This happens with kernels older than 5.8.0-48-generic, at least -49 and
- -50.
+ This happens with kernels newer than 5.8.0-48-generic, i.e  -49 and -50.
  
  On the occasion I was able to boot in, I was using a recovery mode and
  display was deemed unknown. I am not sure if this is because of recovery
  mode settings.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 12:33:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASRock Incorporation Motherboard [1849:0162]
+  Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASRock Incorporation Motherboard [1849:0162]
  InstallationDate: Installed on 2020-07-04 (300 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=3cea77a7-cb0e-4309-8963-651539349612 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: Z77 

[Touch-packages] [Bug 1926661] Re: i think gpu driver isn't working well.

[Shoyayeb Hasan Shafin]

i reinstalled but it doesn't fixed at all :(

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

Title:
  i think gpu driver isn't working well.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  there are some glitch and shuttering on desktop and it have so low
  performance as compared to windows. :(

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 02:18:52 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: rtl8188fu, 1.0, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 4th Generation Core Processor Family 
Integrated Graphics Controller [1849:041e]
  InstallationDate: Installed on 2021-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=39f8b6ac-7465-4bb1-992a-61515406828c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H91M-XT PLUS
  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.:bvrP1.10:bd07/27/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH91M-XTPLUS: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926661/+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 1926661] Re: i think gpu driver isn't working well.

[Shoyayeb Hasan Shafin]

-- Logs begin at Fri 2021-04-30 05:45:36 +06, end at Fri 2021-04-30 17:26:43 +>
এপ্রিল 30 05:45:36 ubuntu kernel: microcode: microcode updated early to revisio>
এপ্রিল 30 05:45:36 ubuntu kernel: Linux version 5.8.0-50-generic (buildd@lgw01->
এপ্রিল 30 05:45:36 ubuntu kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0->
এপ্রিল 30 05:45:36 ubuntu kernel: KERNEL supported cpus:
এপ্রিল 30 05:45:36 ubuntu kernel:   Intel GenuineIntel
এপ্রিল 30 05:45:36 ubuntu kernel:   AMD AuthenticAMD
এপ্রিল 30 05:45:36 ubuntu kernel:   Hygon HygonGenuine
এপ্রিল 30 05:45:36 ubuntu kernel:   Centaur CentaurHauls
এপ্রিল 30 05:45:36 ubuntu kernel:   zhaoxin   Shanghai  
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87>
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE>
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX>
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes>
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Enabled xstate features 0x7, context>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-provided physical RAM map:
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x00058000-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x00059000-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x0009f000-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x0010-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0xb47cc000-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0xb47d3000-0x>
lines 1-23













-- Logs begin at Fri 2021-04-30 05:45:36 +06, end at Fri 2021-04-30 17:26:43 +>
এপ্রিল 30 05:45:36 ubuntu kernel: microcode: microcode updated early to revisio>
এপ্রিল 30 05:45:36 ubuntu kernel: Linux version 5.8.0-50-generic (buildd@lgw01->
এপ্রিল 30 05:45:36 ubuntu kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0->
এপ্রিল 30 05:45:36 ubuntu kernel: KERNEL supported cpus:
এপ্রিল 30 05:45:36 ubuntu kernel:   Intel GenuineIntel
এপ্রিল 30 05:45:36 ubuntu kernel:   AMD AuthenticAMD
এপ্রিল 30 05:45:36 ubuntu kernel:   Hygon HygonGenuine
এপ্রিল 30 05:45:36 ubuntu kernel:   Centaur CentaurHauls
এপ্রিল 30 05:45:36 ubuntu kernel:   zhaoxin   Shanghai  
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87>
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE>
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX>
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes>
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Enabled xstate features 0x7, context>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-provided physical RAM map:
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x00058000-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x00059000-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x0009f000-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0x0010-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0xb47cc000-0x>
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 0xb47d3000-0x>
lines 1-23...skipping...
-- Logs begin at Fri 2021-04-30 05:45:36 +06, end at Fri 2021-04-30 17:26:43 
+06. --
এপ্রিল 30 05:45:36 ubuntu kernel: microcode: microcode updated early to 
revision 0x28, date = 2019-11-12
এপ্রিল 30 05:45:36 ubuntu kernel: Linux version 5.8.0-50-generic 
(buildd@lgw01-amd64-030) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #>
এপ্রিল 30 05:45:36 ubuntu kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=d5daed63-d819-46e3-a5b0-903edc5f7cd8 ro quiet splash vt.handoff=7
এপ্রিল 30 05:45:36 ubuntu kernel: KERNEL supported cpus:
এপ্রিল 30 05:45:36 ubuntu kernel:   Intel GenuineIntel
এপ্রিল 30 05:45:36 ubuntu kernel:   AMD AuthenticAMD
এপ্রিল 30 05:45:36 ubuntu kernel:   Hygon HygonGenuine
এপ্রিল 30 05:45:36 ubuntu kernel:   Centaur CentaurHauls
এপ্রিল 30 05:45:36 ubuntu kernel:   zhaoxin   Shanghai  
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 
floating point registers'
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE 
registers'
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX 
registers'
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: xstate_offset[2]:  576, 
xstate_sizes[2]:  256
এপ্রিল 30 05:45:36 ubuntu kernel: x86/fpu: Enabled xstate features 0x7, context 
size is 832 bytes, using 'standard' format.
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-provided physical RAM map:
এপ্রিল 30 05:45:36 ubuntu kernel: BIOS-e820: [mem 
0x-0x00057fff] usable
এপ্রিল 30 05:45:36 

[Touch-packages] [Bug 1925217] Re: package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: new python3-uno package pre-removal script subprocess returned error exit status 1

[Rico Tzschichholz]

** Package changed: libreoffice (Ubuntu) => python3-defaults (Ubuntu)

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

Title:
  package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to
  install/upgrade: new python3-uno package pre-removal script subprocess
  returned error exit status 1

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  It shows that debpython module is not there but it is not installable
  as well.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-uno 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Apr 18 12:50:16 2021
  ErrorMessage: new python3-uno package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2021-04-02 (17 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: libreoffice
  Title: package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to 
install/upgrade: new python3-uno package pre-removal script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1925217/+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 1925217] [NEW] package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: new python3-uno package pre-removal script subprocess returned error exit status 1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

It shows that debpython module is not there but it is not installable as
well.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3-uno 1:6.4.6-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Apr 18 12:50:16 2021
ErrorMessage: new python3-uno package pre-removal script subprocess returned 
error exit status 1
InstallationDate: Installed on 2021-04-02 (17 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: libreoffice
Title: package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: 
new python3-uno package pre-removal script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal
-- 
package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: new 
python3-uno package pre-removal script subprocess returned error exit status 1
https://bugs.launchpad.net/bugs/1925217
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to python3-defaults 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 1892559] Re: [MIR] ccid opensc pcsc-lite

[Sebastien Bacher]

@opensc

* the dh_missing has been reported to Debian now,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987817

* the launchpad buglist has been triaged a bit and fixed issues closed

* the libraries are private (no .so provided, other softwares can't
really build with it), ideally they would move it to a subdir but do we
really need .symbols added in such cases?

** Bug watch added: Debian Bug tracker #987817
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987817

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

Title:
  [MIR] ccid opensc pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  Invalid
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 

[Touch-packages] [Bug 1926737] [NEW] Lack of permissions to access display on X11 causes QT to dump core

[Sergio Callegari]

Public bug reported:

Lack of permissions to access the display causes QT to dump core.

You get

Qt WARNING: could not connect to display
Qt FATAL: This application failed to start because no Qt platform plugin could 
be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs,
linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland,
wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Aborted (core dumped)

but this should not be a condition to abort with a core dump, rather a
mere error on which the application should exit (as I believe it used to
do until not long ago)

To trigger the issue it is enough to be on X11, su to another user (not
having permission to use the display) try to launch a QT application
from that user.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libqt5core5a 5.12.8+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Apr 30 11:31:57 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-02-16 (439 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: qtbase-opensource-src
UpgradeStatus: Upgraded to focal on 2020-05-23 (342 days ago)

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


** Tags: amd64 apport-bug focal third-party-packages

** Description changed:

- Lack of permissions to access the display causes X11 to dump core.
+ Lack of permissions to access the display causes QT to dump core.
  
  You get
  
- Qt WARNING: could not connect to display 
+ Qt WARNING: could not connect to display
  Qt FATAL: This application failed to start because no Qt platform plugin 
could be initialized. Reinstalling the application may fix this problem.
  
  Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs,
  linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland,
  wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
  
  Aborted (core dumped)
  
  but this should not be a condition to abort with a core dump, rather a
  mere error on which the application should exit (as I believe it used to
  do until not long ago)
  
  To trigger the issue it is enough to be on X11, su to another user (not
  having permission to use the display) try to launch a QT application
  from that user.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5core5a 5.12.8+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Apr 30 11:31:57 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (439 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to focal on 2020-05-23 (342 days ago)

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

Title:
  Lack of permissions to access display on X11 causes QT to dump core

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

Bug description:
  Lack of permissions to access the display causes QT to dump core.

  You get

  Qt WARNING: could not connect to display
  Qt FATAL: This application failed to start because no Qt platform plugin 
could be initialized. Reinstalling the application may fix this problem.

  Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs,
  linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland,
  wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

  Aborted (core dumped)

  but this should not be a condition to abort with a core dump, rather a
  mere error on which the application should exit (as I believe it used
  to do until not long ago)

  To trigger the issue it is enough to be on X11, su to another user
  (not having permission to use the display) try to launch a QT
  application from that user.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5core5a 5.12.8+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Apr 30 11:31:57 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (439 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to focal on 2020-05-23 (342 days ago)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1923464] Re: ideally should boot rootfs from a matching hard drive

[Dimitri John Ledkov]

My understanding of resilient boot is that there are multiple ESPs
trying to boot the same raid device.

If there is only one rootfs filesystem, boot that one. Which in case of
raid, there will be only one.

I'm more concerned about the case of two ubuntu-server preinstalled
images on two usb sticks not booting of the right place, when there are
two different installations.

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

Title:
  ideally should boot rootfs from a matching hard drive

Status in cloud-images:
  New
Status in grub2 package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in u-boot package in Ubuntu:
  New
Status in u-boot-menu package in Ubuntu:
  New

Bug description:
  Ideally we should strive to boot rootfs from a matching hard drive.

  I.e. if we are booting rootfs by UUID, we should try to find the one
  that came from the same drive as where ESP (UEFI) came from, or u-boot
  spl / u-boot got loaded from (loader1/loader2).

  Such that for example, when booted from external usb stick, rootfs
  from there is mounted.

  Or when booted from internal drive whilst a dd backup is attached over
  usb, rootfs is loaded from the internal drive not from the usb
  attached backup.

  This would need:

  * u-boot to export the drive it loaded extlinux.conf / bootscript
  from, and pass it on kernel command line

  * grub to export the device UUID it got loaded from (from the
  BootServices EFI table) and pass it on the kernel command line or via
  runtime EFI variable

  * sdboot already does that I believe, but not sure if initramfs-tools
  consumes the sdboot provided information

  * initramfs-tools to consume above and sort the discovered devices
  based on that, when deciding what to mount as rootfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1923464/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall

[lincvz]

I plan to migrate BDB backend to MDB. Maybe it could help ?

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

Title:
  slapd enter in infinite loop on sched_yield syscall

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  On a production server, sometimes slapd become unbresponsive, some threads 
loops in sched_yield syscall and consumme all CPU.
  To recover, slapd needs to restart.
  No related information is reported in log file.
  All same issues in OpenLDAP upstream project are old and fixed.
  So maybe this issue affects only Ubuntu package.
  It occurs randomly, so I have no steps to reproduce.

  
  OS : Bionic

  Openldap version:

  libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
 
  libldap-common 2.4.45+dfsg-1ubuntu1.10
 
  slapd  2.4.45+dfsg-1ubuntu1.10
 

  Modules loaded:

  olcModuleLoad: {0}back_bdb
  olcModuleLoad: {1}syncprov
  olcModuleLoad: {2}back_monitor
  olcModuleLoad: {3}memberof.la
  olcModuleLoad: {4}refint.la
  olcModuleLoad: {5}rwm
  olcModuleload: {6}back_ldap

  
  Backend is BDB. slapd run in (single) master - (multi) slave mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall

[lincvz]

Thanks for your support.

> - Your full openldap configuration (please remove any confidential bits, of 
> course).
There is lots of ldif files with many private datas. Do you need a particular 
configuration ?

> - Any log messages from slapd or related services.
olcLogLevel is "sync stats". During the last 40 minutes before (forced) kill, 
slapd send no more logs to syslog. You can see below an extract but it doesn't 
help:

Apr 27 04:50:01 front01 slapd[1023]: conn=10282468 fd=732 TLS established 
tls_ssf=128 ssf=128
Apr 27 04:50:01 front01 slapd[1023]: conn=10282453 op=13 SRCH 
base="cn=Write,cn=Waiters,cn=Monitor" scope=0 deref=2 filter="(objectClass=*)"
Apr 27 04:50:01 front01 slapd[1023]: conn=10282453 op=13 SRCH 
attr=monitorCounter
Apr 27 05:31:59 front01 slapd[1023]: daemon: shutdown requested and initiated.
Apr 27 05:31:59 front01 slapd[1023]: conn=10281700 fd=16 closed (slapd shutdown)
[...777 more . ]
Apr 27 05:31:59 front01 slapd[1023]: conn=10276270 fd=854 closed (slapd 
shutdown)
Apr 27 05:31:59 front01 slapd[1023]: daemon: shutdown requested and initiated.
Apr 27 05:32:18 front01 slapd[122011]: @(#) $OpenLDAP: slapd  (Ubuntu) (Feb 18 
2021 14:22:42) $#012#011Debian OpenLDAP Maintainers 

Apr 27 05:32:18 front01 slapd[122012]: bdb_db_open: database "dc=fti,dc=net": 
unclean shutdown detected; attempting recovery.
Apr 27 05:32:26 front01 slapd[122012]: slapd starting


>- If you can, please install the debug symbols for openldap/slapd and run "gdb 
>-p 
> $PROCESS_PID" (where "$PROCESS_PID" is slapd's PID), then run a "bt" command 
> and attach 
> the output to this bug.
Ok I install the debugging package "slapd-dbgsym" to provide a backtrace next 
time.


>- More information about what is going on in the system when the problem 
>happens. For 
> example, I've read that this might happen when the system load is high; do 
> you notice that 
> as well?
The servers hosting slapd are constantly under load, but issue occur even when 
overall CPU usage is about 5% ..
Maybe it can help you: the problem didn't occur on old Trusty machines (same 
config, same load).

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

Title:
  slapd enter in infinite loop on sched_yield syscall

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  On a production server, sometimes slapd become unbresponsive, some threads 
loops in sched_yield syscall and consumme all CPU.
  To recover, slapd needs to restart.
  No related information is reported in log file.
  All same issues in OpenLDAP upstream project are old and fixed.
  So maybe this issue affects only Ubuntu package.
  It occurs randomly, so I have no steps to reproduce.

  
  OS : Bionic

  Openldap version:

  libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
 
  libldap-common 2.4.45+dfsg-1ubuntu1.10
 
  slapd  2.4.45+dfsg-1ubuntu1.10
 

  Modules loaded:

  olcModuleLoad: {0}back_bdb
  olcModuleLoad: {1}syncprov
  olcModuleLoad: {2}back_monitor
  olcModuleLoad: {3}memberof.la
  olcModuleLoad: {4}refint.la
  olcModuleLoad: {5}rwm
  olcModuleload: {6}back_ldap

  
  Backend is BDB. slapd run in (single) master - (multi) slave mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1926305] Re: 20.04 Online Accounts - Google Shared Drives

[Sebastien Bacher]

it's not as easy as backporting those changes though, they rely on a new
api in libgdata so we would need to update that library to a newer
version which isn't only a bugfix one

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

Title:
  20.04 Online Accounts - Google Shared Drives

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  Just tested out 21.04 and Google Shared Drives works just fine.

  Any chance the 20.04 LTS gnome-online-accounts could be updated to
  support it?

  If that is not possible, any way to build the package from source?

  Patch available here:
  
https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1

  Problem is that building requires dependencies newer than package.
  Tried this with 3-36 as gnome on 20.04 is 3.36
  https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36

  Example error:
  meson.build:305:2: ERROR: Invalid version of dependency, need 
'polkit-gobject-1' ['>= 0.114'] found '0.105'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926305/+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 1926305] Re: 20.04 Online Accounts - Google Shared Drives

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu.

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Fix Released

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

Title:
  20.04 Online Accounts - Google Shared Drives

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  Just tested out 21.04 and Google Shared Drives works just fine.

  Any chance the 20.04 LTS gnome-online-accounts could be updated to
  support it?

  If that is not possible, any way to build the package from source?

  Patch available here:
  
https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1

  Problem is that building requires dependencies newer than package.
  Tried this with 3-36 as gnome on 20.04 is 3.36
  https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36

  Example error:
  meson.build:305:2: ERROR: Invalid version of dependency, need 
'polkit-gobject-1' ['>= 0.114'] found '0.105'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926305/+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 1926316] Re: lxappearance crashes on launch

[Sebastien Bacher]

** Package changed: lxappearance (Ubuntu) => glib2.0 (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Committed

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

Title:
  lxappearance crashes on launch

Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Backtrace of the segmentation fault

  Program received signal SIGSEGV, Segmentation fault.
  0x7790c79d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x7790c79d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x7790ccc1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7790cf41 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7790d079 in g_key_file_load_from_file () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x55407072 in load_icon_themes_from_dir ()
  #5  0x554073dd in icon_theme_init ()
  #6  0x55404c92 in main ()

  Strace shows that the programs borks while trying to load the icon
  theme "/usr/share/icons/gnome/index.theme".

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lxappearance 0.6.3-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Config_System_openbox: Error: [Errno 2] No such file or directory: 
'/etc/xdg/lxsession/openbox/desktop.conf'
  CurrentDesktop: lxde
  Date: Tue Apr 27 21:47:03 2021
  Icons_Default: No icons theme configured by default
  InstallationDate: Installed on 2021-01-12 (105 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: lxappearance
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+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 1926325] Re: After upgrade to 21.04, WiFi unable to connect on channel 13

[Sebastien Bacher]

Thank you for your bug report, you might have a better chance to get a
reply if you report it upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues

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

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

Title:
  After upgrade to 21.04, WiFi unable to connect on channel 13

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have upgraded a desktop system from 20.10 to 21.04
  Then, the computer didn't connect to my WiFi network anymore ! When I opened 
Network manager, I could see the WiFi networks of my neighbours but not mine !

  My Wifi network is provided by a Freebox (french provider Free) and choose 
automatically the channel for the Wifi network (n type). At home, it was 
channel n° 13. The neighbours were on channel 6.
  So I changed the setup of my box manually to channel 11 and the computer can 
see again my network and connect without problem ! Of course, this problem 
didn't happen with the 20.10 version : it was connected on channel 13 before 
the upgrade !

  So it seems that Ubuntu 21.04 is unable to connect to a network on
  channel 13 !

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 27 19:01:54 2021
  InstallationDate: Installed on 2020-04-10 (382 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IpRoute:
   default via 192.168.0.254 dev wlp4s6 proto dhcp metric 600 
   default via 172.20.10.1 dev bnep0 proto dhcp metric 750 
   169.254.0.0/16 dev bnep0 scope link metric 1000 
   172.20.10.0/28 dev bnep0 proto kernel scope link src 172.20.10.6 metric 750 
   192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to hirsute on 2021-04-26 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1926325/+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 1926316] [NEW] lxappearance crashes on launch

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Backtrace of the segmentation fault

Program received signal SIGSEGV, Segmentation fault.
0x7790c79d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0x7790c79d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7790ccc1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7790cf41 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7790d079 in g_key_file_load_from_file () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x55407072 in load_icon_themes_from_dir ()
#5  0x554073dd in icon_theme_init ()
#6  0x55404c92 in main ()

Strace shows that the programs borks while trying to load the icon theme
"/usr/share/icons/gnome/index.theme".

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: lxappearance 0.6.3-1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
Config_System_openbox: Error: [Errno 2] No such file or directory: 
'/etc/xdg/lxsession/openbox/desktop.conf'
CurrentDesktop: lxde
Date: Tue Apr 27 21:47:03 2021
Icons_Default: No icons theme configured by default
InstallationDate: Installed on 2021-01-12 (105 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: lxappearance
UpgradeStatus: Upgraded to hirsute on 2021-04-22 (5 days ago)

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Status: Fix Committed


** Tags: amd64 apport-bug hirsute
-- 
lxappearance crashes on launch
https://bugs.launchpad.net/bugs/1926316
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to glib2.0 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 1926509] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.2+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1877165
   package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package libgdk-pixbuf-2.0-0:amd64 2.42.2+dfsg-1build1 failed to
  install/upgrade: triggers looping, abandoned

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Everything is crashing and I don't know why

  ProblemType: Package
  DistroRelease: Ubuntu 21.04
  Package: libgdk-pixbuf-2.0-0:amd64 2.42.2+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 28 21:02:13 2021
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2021-04-07 (20 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu1
   apt  2.2.3
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf-2.0-0:amd64 2.42.2+dfsg-1build1 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to hirsute on 2021-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1926509/+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 1926485] Re: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: triggers looping, abandoned

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1877165
   package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to
  install/upgrade: triggers looping, abandoned

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Groovy gorilla upgrade failure

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 28 11:36:04 2021
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2020-06-21 (311 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.3
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to groovy on 2021-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1926485/+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 1926544] Re: Version=Ubuntu 21.04 (Impish Indri)

[Sebastien Bacher]

https://bugs.launchpad.net/ubuntu/+source/base-files/11.1ubuntu2

** Changed in: base-files (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Version=Ubuntu 21.04 (Impish Indri)

Status in base-files package in Ubuntu:
  Fix Committed

Bug description:
  There maybe a reason for this, but it looks strange (was something missed)?
  VERSION="21.04 (Impish Indri)"

  ** Actual Results

  guiverc@d960-ubu2:~/uwn$   cat /etc/os-release 
  PRETTY_NAME="Ubuntu Impish Indri (development branch)"
  NAME="Ubuntu"
  VERSION_ID="21.10"
  VERSION="21.04 (Impish Indri)"
  VERSION_CODENAME=impish
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=impish
  guiverc@d960-ubu2

  ** Expected Results

  VERSION="21.10 (Impish Indri)"

  importance is LOW

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: base-files 11.1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Thu Apr 29 12:35:19 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-16 (1260 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1926544/+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 1926661] Re: i think gpu driver isn't working well.

[Sebastien Bacher]

Thank you for your bug report, could you add your 'journalctl -b 0' log
after noticing the issue?

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

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

Title:
  i think gpu driver isn't working well.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  there are some glitch and shuttering on desktop and it have so low
  performance as compared to windows. :(

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 02:18:52 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: rtl8188fu, 1.0, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 4th Generation Core Processor Family 
Integrated Graphics Controller [1849:041e]
  InstallationDate: Installed on 2021-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=39f8b6ac-7465-4bb1-992a-61515406828c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H91M-XT PLUS
  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.:bvrP1.10:bd07/27/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH91M-XTPLUS: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[Sebastien Bacher]

Thank you for your bug report. How often do you get the issue? Could you
take  a photo or video showing the issue? Would you please add the
'journalctl -b 0' log after getting the problem?

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  the screem freezes and when i open a couple programs many bugs start
  to show up

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 01:09:02 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:1b7d]
  InstallationDate: Installed on 2020-12-11 (139 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b725 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. Z450LA
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=5f3995ba-8da9-4c41-9bf9-e59240f2ca6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z450LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z450LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ450LA.204:bd08/12/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnZ450LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ450LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Z
  dmi.product.name: Z450LA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[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/1926688

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  the screem freezes and when i open a couple programs many bugs start
  to show up

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 01:09:02 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:1b7d]
  InstallationDate: Installed on 2020-12-11 (139 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b725 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. Z450LA
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=5f3995ba-8da9-4c41-9bf9-e59240f2ca6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z450LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z450LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ450LA.204:bd08/12/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnZ450LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ450LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Z
  dmi.product.name: Z450LA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

the screem freezes and when i open a couple programs many bugs start to
show up

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 30 01:09:02 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed
 v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller 
[1043:1b7d]
InstallationDate: Installed on 2020-12-11 (139 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:b725 Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. Z450LA
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=5f3995ba-8da9-4c41-9bf9-e59240f2ca6c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2015
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Z450LA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Z450LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ450LA.204:bd08/12/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnZ450LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ450LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: Z
dmi.product.name: Z450LA
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug false-gpu-hang focal freeze third-party-packages 
ubuntu
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1926688
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 1926686] Re: lightdm segfaults

[Gunnar Hjalmarsson]

Thanks for your report!

Since you use lightdm 1.30.0-0ubuntu4~20.04.1 from focal-proposed, can
you please downgrade to version 1.30.0-0ubuntu3.1 and let us know if it
makes a difference.

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

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

Title:
  lightdm segfaults

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip
  7f7260003f0b sp 7fffbb5a0600 error 4 in
  libc-2.31.so[7f725ff8e000+178000]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  Uname: Linux 5.10.32 x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 29 20:55:18 2021
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+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 1892559] Re: [MIR] ccid opensc pcsc-lite

[Sebastien Bacher]

Updating the title, hopefully it reflects correctly what needs to be
promoted.

@Marco, the binaries we want installed are those 'libpam-sss opensc-
pkcs11 pcscd' right?

libpam-sss is already in main and pcscd depends on libccid which also
needs promotion as a result

** Summary changed:

- [MIR] ccid libpcsc-perl opensc pcsc-tools pcsc-lite
+ [MIR] ccid opensc pcsc-lite

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

Title:
  [MIR] ccid opensc pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  Invalid
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it 

[Touch-packages] [Bug 1925798] Re: SRU the current 1.2.4 stable update

[Sebastien Bacher]

** Description changed:

  * Impact
  
  That's the current GNOME stable update, including some bugfixes
  https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS
  
  * Test case
- 
- The update is part of GNOME stable updates
- https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
  
  The library is used by rygel for pnp media sharing. Enable the option
  from the settings and try browsing and playing for another computer
  using for example rhythmbox.
  
  * Regression potential
  
  The main fix is around IPv6 local resolution, check that if possible.

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

Title:
  SRU the current 1.2.4 stable update

Status in gupnp package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  That's the current GNOME stable update, including some bugfixes
  https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS

  * Test case

  The library is used by rygel for pnp media sharing. Enable the option
  from the settings and try browsing and playing for another computer
  using for example rhythmbox.

  * Regression potential

  The main fix is around IPv6 local resolution, check that if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1925798/+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 1926697] Re: gdebi does not start w msg 'Download failed'

[corrado venturini]

Attached screenshot with message

** Attachment added: "screenshot with message"
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1926697/+attachment/5493545/+files/Screenshot%20from%202021-04-30%2009-28-47.png

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

Title:
  gdebi does not start w msg 'Download failed'

Status in gdebi package in Ubuntu:
  New

Bug description:
  Just click on gdebi icon on dash.
  problem occurs in both xorg and wayland sessions

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gdebi 0.9.5.7+nmu4
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 08:15:15 2021
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2021-04-23 (6 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterpreterPath: /usr/bin/python3.9
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1926697/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Sebastien Bacher]

I've uploaded the fix to focal, hirsute and impish are going to be fixed
with the GNOME 40.1 update, tarballs are due this weekend and we are
going to wait on that to upload to those series

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Committed

Bug description:
  There is a recently introduced bug in evolution-data-server which
  broke access to email in iCloud.

  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1892559] Re: [MIR] ccid llibpcsc-perl opensc pcsc-tools pcsc-lite

[Sebastien Bacher]

** Summary changed:

- [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
+ [MIR] ccid llibpcsc-perl opensc pcsc-tools pcsc-lite

** Summary changed:

- [MIR] ccid llibpcsc-perl opensc pcsc-tools pcsc-lite
+ [MIR] ccid libpcsc-perl opensc pcsc-tools pcsc-lite

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

Title:
  [MIR] ccid libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  Invalid
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it seems funny all the same.

  Otherwise appears to satisfy FHS and Debian 

[Touch-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter

[Didier Roche]

** Description changed:

- When a user is logged in to the Ubuntu desktop, a power button event
- will cause the user to be prompted to choose if they'd like to proceed
- with a shutdown. However, if the system is sitting at a greeter screen,
- a power button event will instead attempt a suspend w/o prompting. This
- is due to a different set of defaults for the greeter and the user:
+ [Impact] 
+ When a user is logged in to the Ubuntu desktop, a power button event will 
cause the user to be prompted to choose if they'd like to proceed with a 
shutdown. However, if the system is sitting at a greeter screen, a power button 
event will instead attempt a suspend w/o prompting. This is due to a different 
set of defaults for the greeter and the user.
+ This is a fix for this, aligning all power actions between the greeter 
behaviour and the user session one on the user session.
+ 
+ [Test Plan] 
+ 1. Install new package and reboot
+ 2. On the greeter screen (gdm), press the physical power button of your 
machine.
+ 3. You should be now prompted about what to do, like shutdown. You can 
dismiss it.
+ 4. Clicking on the physical suspend button should suspend the machine 
immediatly.
+ 
+ [Where problems could occur]
+ We change the scope of when we applied those settings: we were only applying 
them to the GNOME session ran by the user, and it will now be applied as 
default to the GNOME session ran by gdm.
+ Impacts is thus limited to the greeter screen.
+ 
+ 
+ Diff is available on this commit: 
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89
+ 
+ --
+ Original report content:
  
  For a logged-in desktop user, they
  see:
  
  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'
  
  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'
  
  Changing the gdm user's setting to "interactive" using gsettings causes
  the greeter to begin prompting, consistent with the logged in user
  experience.

** Changed in: ubuntu-settings (Ubuntu Focal)
   Status: Incomplete => Triaged

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Focal:
  Triaged
Status in ubuntu-settings source package in Hirsute:
  Fix Released

Bug description:
  [Impact] 
  When a user is logged in to the Ubuntu desktop, a power button event will 
cause the user to be prompted to choose if they'd like to proceed with a 
shutdown. However, if the system is sitting at a greeter screen, a power button 
event will instead attempt a suspend w/o prompting. This is due to a different 
set of defaults for the greeter and the user.
  This is a fix for this, aligning all power actions between the greeter 
behaviour and the user session one on the user session.

  [Test Plan] 
  1. Install new package and reboot
  2. On the greeter screen (gdm), press the physical power button of your 
machine.
  3. You should be now prompted about what to do, like shutdown. You can 
dismiss it.
  4. Clicking on the physical suspend button should suspend the machine 
immediatly.

  [Where problems could occur]
  We change the scope of when we applied those settings: we were only applying 
them to the GNOME session ran by the user, and it will now be applied as 
default to the GNOME session ran by gdm.
  Impacts is thus limited to the greeter screen.

  
  Diff is available on this commit: 
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89

  --
  Original report content:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1926437] Autopkgtest regression report (python-apt/1.1.0~beta1ubuntu0.16.04.12)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python-apt 
(1.1.0~beta1ubuntu0.16.04.12) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

botch/unknown (arm64)
update-notifier/unknown (arm64)
snapcraft/unknown (arm64)
ubiquity/unknown (arm64)
isenkram/unknown (arm64)
python-apt/unknown (arm64)
update-manager/unknown (arm64)
apport/2.20.1-0ubuntu2.30 (amd64, i386)
snapcraft/2.43.1+16.04.1 (amd64, armhf, i386)
bzr-builddeb/unknown (arm64)
firefox/unknown (arm64)
chromium-browser/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#python-apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] Backport zstd support, fix bug in python-apt

Status in apt package in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  New
Status in apt source package in Xenial:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt source package in Hirsute:
  New
Status in python-apt source package in Impish:
  New

Bug description:
  [Impact]
  APT in xenial needs to learn about zstd support to enable Launchpad to work 
with zstd packages.

  python-apt in all releases needs to be adjusted to pass the compressor
  names instead of programs to ExtractTar, as otherwise, if
  /usr/bin/zstd does not exist, it will pass "false" as the compressor,
  and then ExtractTar fails (same for other compressors).

  On hirsute, the python-apt upload also includes some new  
annotations for build-dependencies, as it's a straight upload of the 2.2
  stable series.

  [Test plan]
  The apt regression tests cover the compression methods extensively, including 
even stored compressed lists in /var/lib/apt and fetching Packages files 
compressed with such methods, for all compression methods.

  The final test is to make apt_inst.DebFile("glibc-doc-
  reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
  1923845 work in python3-apt.

  For hirsute, the build dependency changes will verify themselves
  during the build ;)

  [Where problems could occur]

  APT:

  The changes to APT are adding the zstd compression backend to FileFd
  and then linking it into the configuration. The former is adding new
  code, triggered only on zstd files, and should not be able to cause
  regressions.

  The latter is a bunch of small lines here and there, and it caused
  issues during backporting in the test suite because it expected
  compressors in a specific order. However, chances are that nothing
  else has as stringent requirements as the test suite, so I don't
  believe that is a problem for existing users.

  Bugs can of course be in the code dealing with zstd, and that might
  open you up to security vulnerabilities in the zstd code if you pass
  APT zstd compressed files.

  A regression can be if clients used apt-helper cat-file to cat a zstd-
  compressed file ending in .zst - they'll now get uncompressed content,
  rather than compressed.

  python-apt:

  The change just replaces Binary with Name, aligning the code with APT
  itself, so it's so trivial, we don't expect regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1902898] Re: power-button action inconsistent between user session and greeter

[Didier Roche]

We are going to backport it to focal. Groovy, as being EOL in a couple
of months, doesn’t work any SRU work, removing the task.

** No longer affects: ubuntu-settings (Ubuntu Groovy)

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Focal:
  Incomplete
Status in ubuntu-settings source package in Hirsute:
  Fix Released

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1926697] [NEW] gdebi does not start w msg 'Download failed'

[corrado venturini]

Public bug reported:

Just click on gdebi icon on dash.
problem occurs in both xorg and wayland sessions

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gdebi 0.9.5.7+nmu4
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 30 08:15:15 2021
ExecutablePath: /usr/share/gdebi/gdebi-gtk
InstallationDate: Installed on 2021-04-23 (6 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
InterpreterPath: /usr/bin/python3.9
PackageArchitecture: all
Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
PythonDetails: N/A
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

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

Title:
  gdebi does not start w msg 'Download failed'

Status in gdebi package in Ubuntu:
  New

Bug description:
  Just click on gdebi icon on dash.
  problem occurs in both xorg and wayland sessions

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gdebi 0.9.5.7+nmu4
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 08:15:15 2021
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2021-04-23 (6 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterpreterPath: /usr/bin/python3.9
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1926697/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Sebastien Bacher]

I'm going to work on SRUing that fix

** Changed in: evolution-data-server (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Committed

Bug description:
  There is a recently introduced bug in evolution-data-server which
  broke access to email in iCloud.

  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1926009] Re: Incomplete display of text

[Sebastien Bacher]

Thanks, now could you try to update again tjhe amdgpu binary to see if
the issue is in this one so we know to which package to reassign?

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

Title:
  Incomplete display of text

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu release: 20.04.1

  * What is expected to happen.

  All gui text elements to display complete words.

  * What actually happens.

  Since a recent update, gui text displays incompletely.

  I'm posting this with some difficulty from the affected system, but
  have noted similar issues being experienced by others and I share
  links below:

  https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text
  https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words
  
https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly
  https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text

  The issues above seem to suggest the the issue may lie with the AMD
  graphics driver, although in my case I think I am using the 'radeon'
  open source driver.

  The issue occurs regardless of me use the current or previous kernel
  version installed.

  Please let me know if there is any more information that I can
  provide, and I will do my best to get it to you.

  Many thanks,
  Mark.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Apr 24 12:07:35 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] 
[1002:990e] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526]
  MachineType: NOVATECH LTD MBB-66004G
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55-M LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MBB-66004G
  dmi.product.sku: SKU
  dmi.product.version: 1.0
  dmi.sys.vendor: NOVATECH LTD
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2
  version.libgl1-mesa-dri: libgl1-mesa-dri 
21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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