[Touch-packages] [Bug 1943288] Re: Soname change and transition started without a ffe

2021-09-14 Thread Sebastien Bacher
not directly related but we should try to ensure that libffi updates
exercise the tests from some of its rdepends as gjs, it's not working
today since those depends on libglib and not directly on libffi which
means the update could have migrated despite the issue if we hadn't be
lucky

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  New

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1943288] Re: Soname change and transition started without a ffe

2021-09-14 Thread Sebastien Bacher
There are several desktop packages which started having red autopkgtests
due to the update

https://autopkgtest.ubuntu.com/packages/g/gtk+3.0
https://autopkgtest.ubuntu.com/packages/p/python-dbusmock
https://autopkgtest.ubuntu.com/packages/u/umockdev

The i386 tests also showed problems but it could be that they just need
to be retried with the current revision since it seems the issues were
mostly installability problems

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  New

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1943133] Re: [FFe] Sync expat 2.4.1-1 (main) from Debian experimental (main)

2021-09-13 Thread Sebastien Bacher
This bug was fixed in the package expat - 2.4.1-2
Sponsored for Rico Tzschichholz (ricotz)

---
expat (2.4.1-2) unstable; urgency=medium

  * Upload to Sid.

 -- Laszlo Boszormenyi (GCS)   Thu, 09 Sep 2021 21:26:21
+0200

expat (2.4.1-1) experimental; urgency=high

  * New upstream release:
- fix CVE-2013-0340: protect against billion laughs attacks
  (denial-of-service; flavors targeting CPU time or RAM or both,
  leveraging general entities or parameter entities or both).
  * Update libexpat1 symbols.

 -- Laszlo Boszormenyi (GCS)   Mon, 24 May 2021 10:14:11
+0200

** Changed in: expat (Ubuntu)
   Status: Triaged => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-0340

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

Title:
  [FFe] Sync expat 2.4.1-1 (main) from Debian experimental (main)

Status in expat package in Ubuntu:
  Fix Released

Bug description:
  Please sync expat 2.4.1-1 (main) from Debian experimental (main)

  https://github.com/libexpat/libexpat/blob/R_2_4_1/expat/Changes

  CVE-2013-0340
  https://github.com/libexpat/libexpat/pull/466/files

  Changelog entries since current impish version 2.3.0-1:

  expat (2.4.1-1) experimental; urgency=high

    * New upstream release:
  - fix CVE-2013-0340: protect against billion laughs attacks
    (denial-of-service; flavors targeting CPU time or RAM or both,
    leveraging general entities or parameter entities or both).
    * Update libexpat1 symbols.

   -- Laszlo Boszormenyi (GCS)   Mon, 24 May 2021
  10:14:11 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+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 1942940] Re: Hover text in wrong place

2021-09-13 Thread Sebastien Bacher
Thanks for the screenshot, in fact it's a gtk issue which has been
reported upstream as https://gitlab.gnome.org/GNOME/gtk/-/issues/1708

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #1708
   https://gitlab.gnome.org/GNOME/gtk/-/issues/1708

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Triaged

** Also affects: gtk via
   https://gitlab.gnome.org/GNOME/gtk/-/issues/1708
   Importance: Unknown
   Status: Unknown

** Tags added: desktop-lts-wishlist

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

Title:
  Hover text in wrong place

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Open Nautilus, click the hamburger button, hover over the "New
  tab/window/folder" icons. The popup hover text is way over to the LHS
  of the Nautilus window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  8 10:53:38 2021
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'303'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(999, 784)'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
  InstallationDate: Installed on 2019-04-27 (864 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-07-13 (56 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1942940/+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 1943288] Re: Soname change and transition started without a ffe

2021-09-13 Thread Sebastien Bacher
Alright, unsure why the transition hadn't been started between june and
now, the timing is a bit unfortunate since it's blocking stack of
packages in proposed before beta now but let's take that discussion
elsewhere if that's not a release concern

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  Fix Released

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1943288] [NEW] Soname change and transition started without a ffe

2021-09-10 Thread Sebastien Bacher
Public bug reported:

It seems the recent upload includes a soname change and is starting a
transition, such changes at the point of the cycle would require a ffe

** Affects: libffi (Ubuntu)
 Importance: High
 Status: New


** Tags: block-proposed impish rls-ii-incoming

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

** Tags added: impish rls-ii-incoming

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  New

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1942975] Re: gcr 3.40.0-2 ftbfs

2021-09-10 Thread Sebastien Bacher
Trevinho fixed it in
https://bugs.launchpad.net/ubuntu/+source/gcr/3.40.0-3

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

** Changed in: gcr (Ubuntu)
   Status: New => Fix Released

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

Title:
  gcr 3.40.0-2 ftbfs

Status in gcr package in Ubuntu:
  Fix Released

Bug description:
  Reported upstream as https://gitlab.gnome.org/GNOME/gcr/-/issues/84.
  Looks like it might be a flaky test?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1942975/+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 1910908] Re: Web-login page for captive portals not opening on public wireless networks

2021-09-07 Thread Sebastien Bacher
Unsure if the issue is due to network-manager if the firefox portal
isn't working either

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

Title:
  Web-login page for captive portals not opening on public wireless
  networks

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 20.04.1 LTS Focal Fossa the web page to log on to public
  wireless networks does not open. Without this, it is not possible to
  access public networks in cafes and hotels. It neither works with
  Firefox, Chrome nor Konqueror. I could ping the gateway so the
  redirection to the web login page seems to fail. In Ubuntu 16.04 and
  Windows 10, the login page opens as expected on the same machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  Uname: Linux 5.8.0-050800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 10 18:11:46 2021
  InstallationDate: Installed on 2015-11-05 (1893 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp src 192.168.1.136 metric 302 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto dhcp scope link src 192.168.1.136 metric 302
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-09-10 (122 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-02-11T22:32:49.282695
  mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024
  nmcli-dev:
   DEVICE  TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp3s0  wifi  connected full  full  
/org/freedesktop/NetworkManager/Devices/2  Linksys01382 1  
cdc94299-456e-46e1-8487-08b668336342  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   p2p-dev-wlp3s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   lo  loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  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/1910908/+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 1910908] Re: Web-login page for captive portals not opening on public wireless networks

2021-09-07 Thread Sebastien Bacher
Thank you for your bug report. Could you add the 'journalctl -b 0' log
from a system having the issue next time you hit the bug?

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

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Web-login page for captive portals not opening on public wireless
  networks

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 20.04.1 LTS Focal Fossa the web page to log on to public
  wireless networks does not open. Without this, it is not possible to
  access public networks in cafes and hotels. It neither works with
  Firefox, Chrome nor Konqueror. I could ping the gateway so the
  redirection to the web login page seems to fail. In Ubuntu 16.04 and
  Windows 10, the login page opens as expected on the same machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  Uname: Linux 5.8.0-050800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 10 18:11:46 2021
  InstallationDate: Installed on 2015-11-05 (1893 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp src 192.168.1.136 metric 302 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto dhcp scope link src 192.168.1.136 metric 302
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-09-10 (122 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-02-11T22:32:49.282695
  mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024
  nmcli-dev:
   DEVICE  TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp3s0  wifi  connected full  full  
/org/freedesktop/NetworkManager/Devices/2  Linksys01382 1  
cdc94299-456e-46e1-8487-08b668336342  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   p2p-dev-wlp3s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   lo  loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  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/1910908/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

2021-08-25 Thread Sebastien Bacher
no, new features don't really qualify for a stable update

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1938753] Re: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches auch in Pa

2021-08-09 Thread Sebastien Bacher
** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade:
  Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu
  überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  Just tried to install updates, then the error reporting popped up.

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio-utils 1:14.2-2ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucl   2483 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Aug  3 08:12:26 2021
  ErrorMessage: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu 
überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist
  InstallationDate: Installed on 2021-08-02 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210801)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulsecommon-14.2.so: cannot open 
shared object file: No such file or directory
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: pulseaudio
  Title: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: 
Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, 
welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938753/+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 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

2021-07-16 Thread Sebastien Bacher
Is that still an issue with other fixes that landed?

** Changed in: pulseaudio (Ubuntu)
 Assignee: Sebastien Bacher (seb128) => (unassigned)

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: <https://certification.ubuntu.com/hardware/201905-27083>
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1871329/+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 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

2021-07-16 Thread Sebastien Bacher
The autopkgtests worked after a retry

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every time. The unwritten bytes if you do a bindiff from before
  and after will be all set to zero.

  [Where problems can occur]

  I am doubtful that any programs are relying on buggy non-deterministic
  behaviour from random bytes found in uninitialised memory, so this
  

[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page

2021-07-16 Thread Sebastien Bacher
>  - What mechanism can we use to determine if it should show?

I don't think we have one atm which is why I was suggesting to just
change the key default so false there

> is it worth bringing that into Impish

I'm just trying to anticipate a discussion with the SRU team and extra
delays due to it but let me ask them directly instead

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

Title:
  Add Ubuntu Pro banner to Livepatch page

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New

Bug description:
  [Impact]
  Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for 
Desktop. Note that this is not shown in current releases, as this feature only 
applies to older versions.

  [Test Case]
  1. Open Software Properties.
  2. Go to Livepatch tab.
  Expected result:
  A banner is shown directing the user to Ubuntu Pro.
  The banner can be dismissed, and doesn't return when restarting 
software-properties.

  [Regression Potential]
  Some risk of introducing a new bug, however the change is quite small and 
doesn't have any complex interactions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

2021-07-16 Thread Sebastien Bacher
** Changed in: modemmanager (Ubuntu)
   Status: New => Fix Released

** Changed in: libmbim (Ubuntu)
   Status: New => Fix Released

** Changed in: libqmi (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  = Certification Validation =

  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make
  sure the other modems still work as expected.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  To support 

[Touch-packages] [Bug 1936312] Re: nm-online times out, failing autopkgtests

2021-07-15 Thread Sebastien Bacher
Thanks Lukas, I hadn't noticed that the systemd was reverted, I added
back the nm change for now

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Committed

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

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

Title:
  nm-online times out, failing autopkgtests

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  The nm-online util does not return successfully as of 1.32.2-0ubuntu1
  (currently in impish-proposed).

  systemd VS network-manager autopkgtests (in LXD) fail, because the
  autopkgtest-virt-lxd runner tries to wait for "network ready" before
  it is reconnecting after a reboot. This happens by checking the
  'systemctl start network-online.target' command, in turn executing the
  'nm-online -s -q' util (via NetworkManager-wait-online.service), in
  addition to systemd-networkd-wait-online.service (which seems to be
  working OK).

  nm-online does not return successfully anymore as of 1.32.2-0ubuntu1,
  but it times out. That is a regression compared to v1.30.

  Reproducer:
  $ lxc launch ubuntu-daily:impish test
  $ lxc exec test bash
  # apt install network-manager #(version 1.30.0-1ubuntu4)
  # time systemctl start network-online.target

  real  0m0.071s
  user  0m0.021s
  sys   0m0.023s
  # time nm-online -s
  Connecting...   30s [started]

  real  0m0.043s
  user  0m0.027s
  sys   0m0.006s
  root@test:~# echo $?
  0

  Everything is OK up to here.

  # vim /etc/apt/sources.list #(enable impish-proposed)
  # apt update && apt install network-manager #(1.32.2-0ubuntu1)
  # time nm-online -s
  Connecting...0s [startup-pending]

  real  0m30.019s
  user  0m0.021s
  sys   0m0.014s

  # time systemctl start network-online.target

  real  1m0.104s
  user  0m0.013s
  sys   0m0.023s
  # journalctl -u NetworkManager | grep startup
  Jul 15 09:05:06 test NetworkManager[1912]:   [1626339906.6507] manager: 
startup complete
  root@test:~# NetworkManager -V
  1.32.2
  root@test:~# nm-online -s
  Connecting...0s [startup-pending]
  root@test:~# echo $?
  1
  root@test:~# nm-online 
  Connecting...0s [offline]
  root@test:~# echo $?
  1

  The journal log contains the "startup completed" line, so 'nm-online
  -s' should return immediately. But as we can see, nm-online fails
  (after a timeout) and thus blocks network-online.target, failing the
  systemd autopkgtests (in LXD).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1936312/+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 1920757] Re: Don't update pango to 1.48.3

2021-07-14 Thread Sebastien Bacher
The issue seems to be code doing undocumented things and was fixed in
the corresponding project, let's update it's early in the cycle now and
we can deal with fallouts if needed

** Changed in: pango1.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Don't update pango to 1.48.3

Status in pango1.0 package in Ubuntu:
  Fix Released

Bug description:
  The upgrade is creating issues, see
  https://gitlab.gnome.org/GNOME/pango/-/issues/542

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1920757/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device

2021-07-12 Thread Sebastien Bacher
Upload to the bionic queue now

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-
  Audio.pcm.iec958_device

Status in OEM Priority Project:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-lib source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Where problems will occur]
  "Cmedia Audio" is the sound card name of this usb audio dongle, and this 
string is got from usb string descriptor, that is to say the "Cmedia Audio" is 
hard-coded in the firmware of that usb dongle.
  Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't 
set string descriptor, then the audio driver sets a generic name "USB Audio 
Device" for them, if a dongle has string descriptor, it may have different 
string like "C-Media USB Headphone Set", and all dongles I met before don't 
have SPDIF interface.
  So If this SRU could introduce regression, it will happen on a Cmedia usb 
audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor 
and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF 
playback device from the gnome-sound-setting. But this regression chance is 
very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in 
the string descriptor and it is very rare a usb audio dongle has SPDIF 
interface. So far we haven't met such a cmedia usb audio dongle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1935794] Re: BlueZ release 5.60

2021-07-12 Thread Sebastien Bacher
** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  BlueZ release 5.60

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  http://www.bluez.org/release-of-bluez-5-60/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935794/+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 1934439] Re: Add Ubuntu Pro banner to Livepatch page

2021-07-09 Thread Sebastien Bacher
Thanks Robert, I saw that you uploaded to bionic and focal now, any
reason to not merge to impish? If technically the feature doesn't apply
to the current serie maybe we should just merge with a default setting
to false so we just need to turn the option on for the next LTS if
needed?

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

Title:
  Add Ubuntu Pro banner to Livepatch page

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New

Bug description:
  [Impact]
  Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for 
Desktop. Note that this is not shown in current releases, as this feature only 
applies to older versions.

  [Test Case]
  1. Open Software Properties.
  2. Go to Livepatch tab.
  Expected result:
  A banner is shown directing the user to Ubuntu Pro.
  The banner can be dismissed, and doesn't return when restarting 
software-properties.

  [Regression Potential]
  Some risk of introducing a new bug, however the change is quite small and 
doesn't have any complex interactions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1925798] Re: SRU the current 1.2.4 stable update

2021-07-06 Thread Sebastien Bacher
Testing 1.2.4-0ubuntu1 browsing and playing in pnp shared media still
works as expected

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

-- 
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
Status in gupnp source package in Focal:
  Fix Committed

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 1934439] Re: Add Ubuntu Pro banner to Livepatch page

2021-07-02 Thread Sebastien Bacher
Hey Robert, I'm going to share some thoughts but ideally confirmation
would come from design

> - Does the banner only show if you haven't already attached this
machine to Ubuntu Advantage?

I guess it makes sense to only show it when the service isn't already in
use

>  - When closing the banner, does it return next time?

The design on miro has a note 'Users should be able to permanently
dismis this', they didn't specify how, by asking the question when
dismissing I guess?

> Does it make sense for this to be in the "Livepatch" tab - should that
tab be renamed to "Ubuntu Pro" at the same time?

I think you pointed out during the first discussions that the banner
would make more sense in the updates tab, we should get design to
comment about that. Renaming sounds like an alternative

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

Title:
  Add Ubuntu Pro banner to Livepatch page

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New
Status in software-properties source package in Impish:
  New

Bug description:
  Add a banner to the Livepatch page to invite users to join the Ubuntu
  Pro for Desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1934199] Re: Switch from Livepatch service to UA client

2021-07-01 Thread Sebastien Bacher
After discussing that a bit it sounds like we only want to replace the
use of the livepatch auth service and enable livepatch using UA, we can
keep using the socket to get the other informations

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New
Status in software-properties source package in Impish:
  New

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1797850] Re: /lib/systemd/systemd:11:__strlen_avx2:message_append_basic:sd_bus_message_append_basic:sd_bus_message_appendv:sd_bus_message_append

2021-07-01 Thread Sebastien Bacher
there has been no report since 19.10 so we can assume it's resolved now

** Changed in: systemd (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  
/lib/systemd/systemd:11:__strlen_avx2:message_append_basic:sd_bus_message_append_basic:sd_bus_message_appendv:sd_bus_message_append

Status in systemd package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797850/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2021-06-29 Thread Sebastien Bacher
Upstream change for replaced by this one now,
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/582

-- 
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 1933078] Re: BlueZ 5.59 release

2021-06-24 Thread Sebastien Bacher
uploaded, thanks Daniel

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

Title:
  BlueZ 5.59 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release BlueZ 5.59 to impish.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-24 Thread Sebastien Bacher
@Daniel, I'm undupping, the bug is referenced in the SRUes uploaded and
I don't intend to a reject/rebuild/fix the vcs etc dance only to change
the reference

** This bug is no longer a duplicate of bug 1926062
   [hirsute/impish] Can't turn bluetooth on again after turning it off

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893=1=2

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

2021-06-22 Thread Sebastien Bacher
uploaded to hirsute SRU queue for review now

-- 
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 Released
Status in evolution-data-server source package in Focal:
  Fix Released
Status in evolution-data-server source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-06-22 Thread Sebastien Bacher
** Changed in: evolution-data-server (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: evolution-data-server (Ubuntu Hirsute)
   Importance: Undecided => High

** Changed in: evolution-data-server (Ubuntu Hirsute)
   Status: Triaged => Fix Committed

-- 
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 Released
Status in evolution-data-server source package in Focal:
  Fix Released
Status in evolution-data-server source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  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 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop

2021-06-22 Thread Sebastien Bacher
Thank you for the report§. Is the issue specific to hdmi connections? Is
that different from already reported hdmi related problem like bug
#1924903 ?

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

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

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

Title:
  Wrong audio output device selected on Raspberry Pi Desktop

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On each boot, an incorrect audio output device is selected, at least
  when HDMI audio output is in use (still need to test the TV/aux
  output; will update the bug when done).

  Specifically, the settings application lists "Multichannel Output -
  Built-in Audio" as the selected output device. However, for audio to
  play through the connected HDMI device, "Analog Output - Built-in
  Audio" must be selected instead. Unfortunately, this setting will be
  lost on subsequent boots. A workaround is to remove the following
  lines from /etc/pulse/default.pa:

  ### Use hot-plugged devices like Bluetooth or USB automatically (LP: 
#1702794)
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  However, removal of these lines will (as the comment suggests) result
  in hot-plugged USB devices *not* being automatically selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-22 Thread Sebastien Bacher
Do you need 20.10? I don't think we have kernels that trigger the issue
on that serie and I don't think it's worth the effort since it's non-LTS
and not-current-stable?

Upload to hirsute and focal now with the bug reference added to the
changelog as required by the SRU process

We will handle impish as we update bluez to the current upstream version

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893=1=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-22 Thread Sebastien Bacher
** Changed in: bluez (Ubuntu)
   Status: New => Fix Committed

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

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893=1=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-06-22 Thread Sebastien Bacher
Ok, so the issue there was triggered by kernel changes, you can read the 
details in the commit message of the GNOME fix
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/d2200632

The fix is in gnome-settings-daemon 3.38.2 in impish, bluez also
requires a similar fix which is being SRUed now as bug #1933221.

Daniel since you are working on updating bluez to 5.59 in impish could
you check if that commit is included and if it's not then cherrypick the
change?

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  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: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1933188] Re: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned er

2021-06-22 Thread Sebastien Bacher
** Package changed: fprintd (Ubuntu) => systemd (Ubuntu)

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

Title:
  package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to
  install/upgrade: installed libpam-fprintd:amd64 package post-
  installation script subprocess returned error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Got this problem when doing a regular "Update/upgrade" from shell

  /usr/bin/deb-systemd-invoke: 32 =head1: not found
  /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected

  Endless loop of these two lines in bash before the crash.

  June 22 sentout uopdate

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114
  Uname: Linux 5.4.0-74-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  AptOrdering:
   alsa-ucm-conf:amd64: Install
   libpam-fprintd:amd64: Install
   fprintd:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 22 06:52:05 2021
  ErrorMessage: installed libpam-fprintd:amd64 package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2021-03-29 (84 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: fprintd
  Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to 
install/upgrade: installed libpam-fprintd:amd64 package post-installation 
script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1933188/+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 1933194] Re: lagg display

2021-06-22 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

** 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/1933194

Title:
  lagg display

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  lagg display

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 22 11:46:23 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3973]
 Subsystem: Device [03ea:1af4]
  InstallationDate: Installed on 2021-06-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 006: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81AX
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic 
root=UUID=dd6defad-6211-4700-8037-049192e91a9b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2018
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6SCN41WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V330-15IKB
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvr6SCN41WW:bd12/19/2018:br1.41:efr1.19:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB:
  dmi.product.family: V330-15IKB
  dmi.product.name: 81AX
  dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB
  dmi.product.version: Lenovo V330-15IKB
  dmi.sys.vendor: LENOVO
  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/1933194/+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 1932066] Re: PulseAudio Preferences searches for libraries in incorrect location

2021-06-21 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1907882 ***
https://bugs.launchpad.net/bugs/1907882

** This bug has been marked a duplicate of bug 1907882
   paprefs does not find modules

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

Title:
  PulseAudio Preferences searches for libraries in incorrect location

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio Preferences (paprefs) appears to be searching for modules
  in the wrong location.

  Specifically, the "install" button appears when modules relevant
  modules cannot be found by paprefs.

  
  paprefs is searching for modules in the location: 
/usr/lib/pulse-13.99/modules/
  the modules are actually located in: /usr/lib/pulse-13.99.1/modules/

  The specifics of this were determined via `strace paprefs`, which
  (among a lot of other things), produces:

  access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) = 
-1 ENOENT (No such file or directory)

  
  creating a symlink from /usr/lib/pulse-13.99.1 to /usr/lib/pulse-13.99 
resolves the issue.

  paprefs should perhaps be updated to match the version of the
  pulseaudio package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1932066/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?

2021-06-21 Thread Sebastien Bacher
similar to bug #1907886 if upstream decided to include it in the noinst
set they might have a reason?

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

Title:
  Can you add the btvirt executable to bluez-tests?

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  See the Debian package: https://packages.debian.org/buster/i386/bluez-
  test-tools/filelist

  The Ubuntu package contains the same tools, except for btvirt. Would
  it be possible to add this? The buildlog shows that the btvirt
  executable is already built, but just not put into the *.deb package.

  Additions to be done to debian/bluez-tests.install:

  emulator/b1ee usr/bin
  emulator/btvirt usr/bin
  emulator/hfp usr/bin

  Having the btvirt tool available will make testing on CI systems a lot
  easier.

  References:
  https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82
  https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1925795] Re: SRU the current 0.20.4 stable update

2021-06-16 Thread Sebastien Bacher
@Chris, would you need the SRU in proposed or to migrate to updates? If
that's the later I don't think we want to waste verification resources
on that at the moment, in which case we would rather delay copying until
we stop doing SRUs for 20.10, sorry for the LTS users waiting for the
update

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

Title:
  SRU the current 0.20.4 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Committed

Bug description:
  * Impact

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

  There are non trivial changes to the meson build system included in
  the update but we still build using autotools so that's not impacting
  us

  
  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Libsecret is providing an API to access gnome-keyring secrets, try a few 
applications using it and make sure credentials are correctly available. To 
list a few possible candidate softwares
  - evince (try to open a a password protected pdf, it should store and 
remember the password)
  - evolution
  - epiphany-browser 
  - vinagre
  - balsa
  - deja-dup

  * Regression potential

  Nothing specific to try in those changes, just ensure the library
  still access the passwords as expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1931907] Re: Spacebar in Incremental search in open-file dialog doesn't work

2021-06-15 Thread Sebastien Bacher
Thank you for your bug report, that's known upstream, see for example
https://gitlab.gnome.org/GNOME/gtk/-/issues/3247

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #3247
   https://gitlab.gnome.org/GNOME/gtk/-/issues/3247

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Triaged

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

Title:
  Spacebar in Incremental search in open-file dialog doesn't work

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce

  
  Stimulate the Nautilus "open-file" dialog to appear somehow. (Say, by Ctrl+O 
in Firefox on Ubuntu 20.04.
  Click the "search" icon (a magnifying glass at top right), or just start 
typing.
  Begin to type a search in the search box that appears.

  Reproducible in:
  "Files" 3.36.3-stable on Ubuntu 20.04

  Current behavior
  There's a race condition, where, if you're faster than the search, you can 
type something including a space. However, if you type slowly, as soon as you 
hit space, the first result will be opened.

  (Note, this incremental search was buggy in a different way back in
  v3.26.4 on Ubuntu 18.04, when I reported this upstream, was told to
  take it downstream, and then had to go back to doing real work. See
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/936#note_454231 )

  Expected behavior
  The incremental search will continue as we type in the search box, without 
any focus-stealing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1931907/+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 1931722] Re: software-properties-gtk generates python errors

2021-06-14 Thread Sebastien Bacher
Thank you for your bug report, the error suggests the system has no dbus
connection left to allocate. Does it happen in specific circonstances?
What is active on your system at the time of the issue?

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

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

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

Title:
  software-properties-gtk generates python errors

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Launching software-properties-gtk gives all these Python errors after
  having upgraded to 21.04:

  Gtk-Message: 17:32:53.643: Failed to load module "appmenu-gtk-module"
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 196, in __init__
  bus = dbus.SystemBus()
File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 195, in __new__
  return Bus.__new__(cls, Bus.TYPE_SYSTEM, mainloop=mainloop,
File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__
  bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__
  bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.LimitsExceeded: The 
maximum number of active connections for UID 1000 has been reached

  Version: 0.99.10

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: software-properties-common 0.99.10
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Jun 11 17:36:34 2021
  InstallationDate: Installed on 2020-09-06 (277 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to hirsute on 2021-06-08 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1931722/+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 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

2021-06-14 Thread Sebastien Bacher
It sounds like the report are being submitted but did you actually go to
https://errors.ubuntu.com/user/ID as you wrote on comment #6? Because as
Daniel wrote in comment #3 'ID is the content of file /var/lib/whoopsie
/whoopsie-id on the machine', so the "ID" part of the URL should
actually be a number specific to your installation and leading to a page
showing your reports

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

Title:
  Pulseaudio 14.2 says: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if the bluez error is related, perhaps not (this is a desktop
  without Wifi/Bluetooth).

  jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
  jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired,>

  Intel i3-9100, C246 chipset, 32GB ram.

  Ubuntu Budgie 21.04 installed via usb boot disk.

  It gives me a popup "error occured" every time I reboot..

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asterix1749 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Jun  1 12:48:36 2021
  InstallationDate: Installed on 2021-05-11 (21 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x
  dmi.board.name: D3644-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3644-B1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: OEM-FTS
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930409/+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 1931799] Re: audio not working on Raspberry Pi 4

2021-06-14 Thread Sebastien Bacher
Thank you for your bug report, could you give some details on what
'stops working' means exactly? When does it happen and what are you
doing at the time? Does it happen in the middle of playing a video for
example? Could you add the 'journalctl --b 0' log of the system after
getting the issue?

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

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

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

Title:
  audio not working on Raspberry Pi 4

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio stops working. After I use the command "systemctl --user
  restart pulseaudio.service" ,it's starting to work, but for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18
  Uname: Linux 5.8.0-1026-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  daniel 1396 F pulseaudio
   /dev/snd/pcmC1D0p:   daniel 1396 F...m pulseaudio
   /dev/snd/controlC0:  daniel 1396 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 13 14:24:39 2021
  ImageMediaBuild: 20201022
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+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 1931793] Re: two bluetooth icons

2021-06-14 Thread Sebastien Bacher
Thank you for your bug report, could you take a screenshot showing the
issue?

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

** 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/1931793

Title:
  two bluetooth icons

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  There two different bluetooth icons on my taskbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
  Uname: Linux 5.4.0-74-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 13 13:49:02 2021
  DistUpgraded: 2020-05-22 21:25:58,624 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:81eb]
  InstallationDate: Installed on 2020-01-28 (501 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd HP TrueVision 
HD
   Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic 
root=UUID=e8d9a762-01b7-4681-bf37-86327e77af4a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-22 (386 days ago)
  dmi.bios.date: 01/05/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EB
  dmi.board.vendor: HP
  dmi.board.version: 61.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd01/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: 1DE70PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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 20.2.6-0ubuntu0.20.04.1
  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/1931793/+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 1931834] Re: Bluetooth sound card not detected

2021-06-14 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Bluetooth sound card not detected

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Gtk-CRITICAL

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-56.63-generic 5.8.18
  Uname: Linux 5.8.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angelina   6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 08:14:36 2021
  InstallationDate: Installed on 2018-08-10 (1038 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to groovy on 2021-04-15 (59 days ago)
  dmi.bios.date: 10/13/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UAK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541UAK.308:bd10/13/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931834/+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 1922951] Re: SRU the current 3.36.5 stable update

2021-06-02 Thread Sebastien Bacher
The 3.36.5-0ubuntu1 update is working as expected, evolution is able to
access calendar emails and contact, gnome-calendar integration is
working

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

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

Title:
  SRU the current 3.36.5 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1922951/+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 1829665] Re: Network Manager and upower not starting, libhogweed error

2021-05-28 Thread Sebastien Bacher
Thank you for your bug report, is that still an issue in newer versions?

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

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

Title:
  Network Manager and upower not starting, libhogweed error

Status in nettle package in Ubuntu:
  Incomplete

Bug description:
  After updating Lubuntu 18.10 to 19.04, NetworkManager and upower no
  longer start. After a bit of digging it shows the source to be
  libhogweed4 v3.4.1-1. The error is:

  relocation error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: symbol
  nettle_rsa_sec_decrypt version HOGWEED_4 not defined in file
  libhogweed.so.4 with link time reference

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1829665/+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 1925775] Re: SRU the current 3.36.1 stable update

2021-05-28 Thread Sebastien Bacher
Using 3.36.1-0ubuntu1 the account are working as expected

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

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

Title:
  SRU the current 3.36.1 stable update

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some API documentation 
fixes and translation updates
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Try adding online account in a GNOME session, ensure the service is
  correctly enabled in application, for example that a google accounts
  are picked up in gnome-calendar and evolution.

  * Regression potential

  The changes are in API documentation so nothing specific to check, if
  there is an issue it would be from a toolchain regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+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 1925795] Re: SRU the current 0.20.4 stable update

2021-05-28 Thread Sebastien Bacher
The 0.20.4-0ubuntu1 update works as expected, accessing the keyring is
working. Trying to open a protected pdf in evince the password is
correctly stored and re-used after trying to open the document again.

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

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

Title:
  SRU the current 0.20.4 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Committed

Bug description:
  * Impact

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

  There are non trivial changes to the meson build system included in
  the update but we still build using autotools so that's not impacting
  us

  
  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Libsecret is providing an API to access gnome-keyring secrets, try a few 
applications using it and make sure credentials are correctly available. To 
list a few possible candidate softwares
  - evince (try to open a a password protected pdf, it should store and 
remember the password)
  - evolution
  - epiphany-browser 
  - vinagre
  - balsa
  - deja-dup

  * Regression potential

  Nothing specific to try in those changes, just ensure the library
  still access the passwords as expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1926843] Re: online accounts integration with fb isn't working

2021-05-28 Thread Sebastien Bacher
Confirmed that using 3.38.1-1ubuntu1.1 facebook isn't listed, other
provides are still available and keep working

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

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Committed
Status in gnome-online-accounts source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)

2021-05-28 Thread Sebastien Bacher
The focal SRU has been reuploaded merging the fixes

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

Title:
  [SRU] pulseaudio: let a single alsa mixer support up to 8 channels
  (focal only)

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Many Lenovo laptops have up to 4 microphones (microphone array), before the 
linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the 
PA in the focal also supports up to 2 chanels for a single alsa mixer, so the 
PA in the focal works well with linux kernel 5.10 and lower on those Lenovo 
laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA 
in the focal can't handle 4 channels of the digital mic, it will use pure 
software volume for digital mic, user can't adjust hardware volume of the 
digital mic anymore.

  
  [Fix]
  Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have 
these 2 patches, so this SRU is for focal only. After applying these 2 patches, 
the PA could handle up to 8 channels for a single alsa mixer. 

  [Test]
  Install patched PA on Lenovo laptops with 4 digital microphone, I could 
change the hardware input volume of digital mic through pulseaudio. I also 
installed patched PA to some old lenovo and Dell machines, all output and input 
devices worked as well as before, there is no regression observed.

  [Where problems could occur]
  This could introduce a regression on the output/input volume control, for 
example, the output or input volume only supports software volume in the PA, 
users can't adjust the hardware volume through pulseaudio anymore. But this 
regression possibility is very low, first the hirsute already has these 2 
patches, second I already tested these 2 patches on different machines, all 
worked as well as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)

2021-05-28 Thread Sebastien Bacher
Oh, I see now that you comment on the other bug, already I will merge
the changes

** Changed in: pulseaudio (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  [SRU] pulseaudio: let a single alsa mixer support up to 8 channels
  (focal only)

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Many Lenovo laptops have up to 4 microphones (microphone array), before the 
linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the 
PA in the focal also supports up to 2 chanels for a single alsa mixer, so the 
PA in the focal works well with linux kernel 5.10 and lower on those Lenovo 
laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA 
in the focal can't handle 4 channels of the digital mic, it will use pure 
software volume for digital mic, user can't adjust hardware volume of the 
digital mic anymore.

  
  [Fix]
  Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have 
these 2 patches, so this SRU is for focal only. After applying these 2 patches, 
the PA could handle up to 8 channels for a single alsa mixer. 

  [Test]
  Install patched PA on Lenovo laptops with 4 digital microphone, I could 
change the hardware input volume of digital mic through pulseaudio. I also 
installed patched PA to some old lenovo and Dell machines, all output and input 
devices worked as well as before, there is no regression observed.

  [Where problems could occur]
  This could introduce a regression on the output/input volume control, for 
example, the output or input volume only supports software volume in the PA, 
users can't adjust the hardware volume through pulseaudio anymore. But this 
regression possibility is very low, first the hirsute already has these 2 
patches, second I already tested these 2 patches on different machines, all 
worked as well as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt

2021-05-28 Thread Sebastien Bacher
Closing since it's an old issue with no report in 8 years also not
likely Mathieu is still working on it at this point

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  0.9.8.0-0ubuntu13 is causing conf prompt

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Got a conf promt. not sure why =)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)

2021-05-28 Thread Sebastien Bacher
Thanks for the work, there is already a SRU in the queue 
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=pulseaudio

Do you want to include your changes and do another upload since it
hasn't been accepted yet or should we wait for the other SRU to clear
out first?

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

Title:
  [SRU] pulseaudio: let a single alsa mixer support up to 8 channels
  (focal only)

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  [Impact]
  Many Lenovo laptops have up to 4 microphones (microphone array), before the 
linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the 
PA in the focal also supports up to 2 chanels for a single alsa mixer, so the 
PA in the focal works well with linux kernel 5.10 and lower on those Lenovo 
laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA 
in the focal can't handle 4 channels of the digital mic, it will use pure 
software volume for digital mic, user can't adjust hardware volume of the 
digital mic anymore.

  
  [Fix]
  Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have 
these 2 patches, so this SRU is for focal only. After applying these 2 patches, 
the PA could handle up to 8 channels for a single alsa mixer. 

  [Test]
  Install patched PA on Lenovo laptops with 4 digital microphone, I could 
change the hardware input volume of digital mic through pulseaudio. I also 
installed patched PA to some old lenovo and Dell machines, all output and input 
devices worked as well as before, there is no regression observed.

  [Where problems could occur]
  This could introduce a regression on the output/input volume control, for 
example, the output or input volume only supports software volume in the PA, 
users can't adjust the hardware volume through pulseaudio anymore. But this 
regression possibility is very low, first the hirsute already has these 2 
patches, second I already tested these 2 patches on different machines, all 
worked as well as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

2021-05-27 Thread Sebastien Bacher
Uploaded to focal, 20.10 is probably not worth doing at this point

** No longer affects: alsa-ucm-conf (Ubuntu Groovy)

** No longer affects: pulseaudio (Ubuntu Groovy)

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In Lenovo P520, which using a codec for front panel, the other codec for rear 
panel and both are on a same card.

  In this case, the rear Mic will present on input devices of "Sound
  Settings" even if attaching nothing to rear mic jack.

  [Fix]
  For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl 
because of
  ```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
  ```
  After applying "Rear Mic Jack", the rear Mic will not always there anymore 
but it's not there as well if hot-plugging audio device on rear mic. Thus, it 
needs to change pulseaudio to handle if all devices are off cases.

  For pulseaudio, if there is no any audio devices attached, then
  attaching an input device on rear mic jack. The port will not be
  selected automatically because the profiles is off. It needs patch
  pulseaudio to check off profiles (for dual codec case).

  [Test]
  After applying these patches, the rear mic jack works good in all cases (boot 
without mic and then attach mic, boot with mic and then hotplug it) and other 
functions (line-in / line-out) work pretty well.

  [Where problems could occur]
  This change only apply the bonus on below cases:
  ```
  if ((has_input_port && found_available_input_port && !has_output_port) ||
  (has_output_port && found_available_output_port && !has_input_port) ||
  (has_input_port && found_available_input_port && has_output_port && 
found_available_output_port)) 
  ```
  and these cases have been tested.
  If there are some complex codec design then it might cause problem but so far 
we didn't see that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

2021-05-27 Thread Sebastien Bacher
Upload to Impish and Hirsute now, Focal is coming

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Fix Committed

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

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  New
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In Lenovo P520, which using a codec for front panel, the other codec for rear 
panel and both are on a same card.

  In this case, the rear Mic will present on input devices of "Sound
  Settings" even if attaching nothing to rear mic jack.

  [Fix]
  For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl 
because of
  ```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
  ```
  After applying "Rear Mic Jack", the rear Mic will not always there anymore 
but it's not there as well if hot-plugging audio device on rear mic. Thus, it 
needs to change pulseaudio to handle if all devices are off cases.

  For pulseaudio, if there is no any audio devices attached, then
  attaching an input device on rear mic jack. The port will not be
  selected automatically because the profiles is off. It needs patch
  pulseaudio to check off profiles (for dual codec case).

  [Test]
  After applying these patches, the rear mic jack works good in all cases (boot 
without mic and then attach mic, boot with mic and then hotplug it) and other 
functions (line-in / line-out) work pretty well.

  [Where problems could occur]
  This change only apply the bonus on below cases:
  ```
  if ((has_input_port && found_available_input_port && !has_output_port) ||
  (has_output_port && found_available_output_port && !has_input_port) ||
  (has_input_port && found_available_input_port && has_output_port && 
found_available_output_port)) 
  ```
  and these cases have been tested.
  If there are some complex codec design then it might cause problem but so far 
we didn't see that.

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

2021-05-26 Thread Sebastien Bacher
** Changed in: evolution-data-server (Ubuntu)
 Assignee: Harald Meier (supersluttommy) => (unassigned)

-- 
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 Released
Status in evolution-data-server source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  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 1929011] Re: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

2021-05-26 Thread Sebastien Bacher
Check /etc/sysctl.d/10-magic-sysrq.conf for details of the actions
allowed by default, but in any case it's not an issue in the ubuntu-
settings package which provides desktop configurations

** Package changed: ubuntu-settings (Ubuntu) => procps (Ubuntu)

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

Title:
  Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

Status in procps package in Ubuntu:
  Incomplete

Bug description:
  Left-Alt is always operational & Right-Alt is not at any time & not specific 
to this report's subject category.
  True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso.
  It is natural to use Right-Alt due to a closer distance to the SysRq key.
  This might help explain why some say REISUB does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 00:27:12 2021
  InstallationDate: Installed on 2020-07-14 (309 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1929011/+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 1929011] Re: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

2021-05-26 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

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

Title:
  Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

Status in procps package in Ubuntu:
  Incomplete

Bug description:
  Left-Alt is always operational & Right-Alt is not at any time & not specific 
to this report's subject category.
  True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso.
  It is natural to use Right-Alt due to a closer distance to the SysRq key.
  This might help explain why some say REISUB does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 00:27:12 2021
  InstallationDate: Installed on 2020-07-14 (309 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1929011/+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 273507] Re: No sound effects play when "play sound effects when buttons are clicked" is enabled

2021-05-18 Thread Sebastien Bacher
@Chris that linked comment seems like spam, I reported it now

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

Title:
  No sound effects play when "play sound effects when buttons are
  clicked" is enabled

Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: libcanberra-gtk-module

  As initially detailed in some of the comments in #258703, selecting
  the "Play sound effects when buttons are clicked" has no effect.

  The instructions in this mailing list post
  (https://tango.0pointer.de/pipermail/libcanberra-
  discuss/2008-July/21.html) need to be followed to enable
  libcanberra gtk integration, which will properly enable gtk-sound
  effects. Quoted here:

  "...Packagers!

  If you package libcanberra, make sure to include a script like this
  one in your package:

  
  #!/bin/sh

  if [ -z "$GTK_MODULES" ] ; then
  GTK_MODULES="libcanberra-gtk-module"
  else
  GTK_MODULES="$GTK_MODULES:libcanberra-gtk-module"
  fi

  export GTK_MODULES
  

  This script should be sourced in each Gnome session and will enable
  the libcanberra gtk module for all gtk programs.

  In fedora we install it as "libcanberra-gtk-module.sh" in
  /etc/X11/xinit/xinitrc.d/. I assume other distributions have similar
  directories.
  ..."

  I think this is missing from the ubuntu libcanberra packages, which is
  preventing the gtk sound effects from working properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/273507/+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 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported

2021-05-18 Thread Sebastien Bacher
The GTK issue is known as
https://gitlab.gnome.org/GNOME/gtk/-/issues/931

There is perhaps a cheese issue there as well though on what it's trying
to render

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #931
   https://gitlab.gnome.org/GNOME/gtk/-/issues/931

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

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Attempting to run cheese on a HDPI display in Wayland results in the
  following errors:

  (cheese:9303): Gdk-CRITICAL **: 10:29:11.221:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed

  (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller
  than 65535 pixels are not supported

  When this error happens, the cheese window does not open.

  Sometimes the "Native Windows ... not supported" does not occur, the
  cheese window does open. However, the photo area is black. I can work
  around this problem by changing the "Photo resolution" in preferences
  to a different value, and then changing it back.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: cheese 3.38.0-3
  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: pass
  CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
  Date: Sat May  8 10:32:03 2021
  InstallationDate: Installed on 2021-04-28 (10 days ago)
  InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
  MachineType: HP HP Spectre x360 Convertible 15-bl1XX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2020
  dmi.bios.release: 15.43
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827F
  dmi.board.vendor: HP
  dmi.board.version: 95.11
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-bl1XX
  dmi.product.sku: 1VW22AV
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-04-28 (17 days ago)
  InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
  MachineType: HP HP Spectre x360 Convertible 15-bl1XX
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 3.38.0-3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  Tags:  hirsute gstreamer-error
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2020
  dmi.bios.release: 15.43
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827F
  dmi.board.vendor: HP
  dmi.board.version: 95.11
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-bl1XX
  dmi.product.sku: 1VW22AV
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 

[Touch-packages] [Bug 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported

2021-05-18 Thread Sebastien Bacher
** Package changed: cheese (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  Error launching cheese: Native Windows taller than 65535 pixels are
  not supported

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Attempting to run cheese on a HDPI display in Wayland results in the
  following errors:

  (cheese:9303): Gdk-CRITICAL **: 10:29:11.221:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed

  (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller
  than 65535 pixels are not supported

  When this error happens, the cheese window does not open.

  Sometimes the "Native Windows ... not supported" does not occur, the
  cheese window does open. However, the photo area is black. I can work
  around this problem by changing the "Photo resolution" in preferences
  to a different value, and then changing it back.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: cheese 3.38.0-3
  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: pass
  CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
  Date: Sat May  8 10:32:03 2021
  InstallationDate: Installed on 2021-04-28 (10 days ago)
  InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
  MachineType: HP HP Spectre x360 Convertible 15-bl1XX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2020
  dmi.bios.release: 15.43
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827F
  dmi.board.vendor: HP
  dmi.board.version: 95.11
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-bl1XX
  dmi.product.sku: 1VW22AV
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-04-28 (17 days ago)
  InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
  MachineType: HP HP Spectre x360 Convertible 15-bl1XX
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 3.38.0-3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  Tags:  hirsute gstreamer-error
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2020
  dmi.bios.release: 15.43
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827F
  dmi.board.vendor: HP
  dmi.board.version: 95.11
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-bl1XX
  dmi.product.sku: 1VW22AV
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:

[Touch-packages] [Bug 1925795] Re: SRU the current 0.20.4 stable update

2021-05-13 Thread Sebastien Bacher
The pinenty test was successful after a retry

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

Title:
  SRU the current 0.20.4 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Committed

Bug description:
  * Impact

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

  There are non trivial changes to the meson build system included in
  the update but we still build using autotools so that's not impacting
  us

  
  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Libsecret is providing an API to access gnome-keyring secrets, try a few 
applications using it and make sure credentials are correctly available. To 
list a few possible candidate softwares
  - evince (try to open a a password protected pdf, it should store and 
remember the password)
  - evolution
  - epiphany-browser 
  - vinagre
  - balsa
  - deja-dup

  * Regression potential

  Nothing specific to try in those changes, just ensure the library
  still access the passwords as expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

2021-05-13 Thread Sebastien Bacher
The software-properties tests were successful after a retry

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

Title:
  Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The auto-correction in libreoffice is not action as it should

  * Test case

  see comment 9

  * Regression potential

  The changes are in the input handling so check that standard input,
  keyboard layouts, compose and keybinding as worked as expected on
  different layout and language type, include ibus and chinese.

   
  I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then 
discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I 
was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, 
same LibreOffice profile, same LibreOffice document, and no changes on my part 
to my LibreOffice settings since I installed Ubuntu 21.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

2021-05-13 Thread Sebastien Bacher
settings as verification-done, thanks @sgage for testing!

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

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

Title:
  Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The auto-correction in libreoffice is not action as it should

  * Test case

  see comment 9

  * Regression potential

  The changes are in the input handling so check that standard input,
  keyboard layouts, compose and keybinding as worked as expected on
  different layout and language type, include ibus and chinese.

   
  I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then 
discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I 
was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, 
same LibreOffice profile, same LibreOffice document, and no changes on my part 
to my LibreOffice settings since I installed Ubuntu 21.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1928327] Re: logrotate on 20.04 is ancient and misses important bugfixes

2021-05-13 Thread Sebastien Bacher
Thank you for your bug report, usually SRU include selected fixes rather
than updating to new version. Do you have issues that you care more
specifically that are affecting focal and resolved in newer versions?
Ideally a SRU would need to start by having a testcase explaining how to
trigger the problem so it's possible to confirm the issue and verify the
fix

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

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

Title:
  logrotate on 20.04 is ancient and misses important bugfixes

Status in logrotate package in Ubuntu:
  New

Bug description:
  Ubuntu focal/20.04 has logrotate version 3.14.0 which is ancient.
  There have been multiple important bugfixes since then
  (https://github.com/logrotate/logrotate/releases).

  Ubuntu hirsute/21.04 does include the latest version, but that isn't
  an LTS version, so is not an option for many of us.

  Please consider adding the latest version to the 20.04 apt repository?

  (I'm aware of workarounds such as installing manually, building from
  source, etc. But like most users I prefer to rely on the apt
  repositories.)

  Thanks!!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1928327/+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 1875671] Re: wayland: desktop folder missing in sidebar

2021-05-13 Thread Sebastien Bacher
Reading their comment they suggest that Gtk is doing the right thing but
gnome-shell is the one setting the key value on wayland and currently
always claiming that desktop isn't handled. The suggestion is that
gnome-shell should be updated, or maybe the desktop extension if it's
technical doable for it to override the value. Reassigning to gnome-
shell as a first step now. Ideally someone would report it upstream on
the shell or desktop icons extension to get their opinion

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Package changed: ubuntu => gnome-shell (Ubuntu)

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

Title:
  wayland: desktop folder missing in sidebar

Status in GTK+:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Using Wayland session nautilus home window does not show Desktop folder in 
sidebar while is dispayed using X11 session.
  see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  Uname: Linux 5.7.0-050700rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:24:45 2020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 
852)'
  InstallationDate: Installed on 2020-04-23 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

2021-05-13 Thread Sebastien Bacher
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
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 Released
Status in evolution-data-server source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

2021-05-12 Thread Sebastien Bacher
@Brian, description updated, thanks for reuploading though as you
mentioned the version used was fine and < to impish so it wouldn't have
created issues going forward.

@sgage, it's being reviewed as indicated by the previous comment

** Description changed:

- I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then
- discovered that Auto-Correct in LibreOffice does not work. Yesterday,
- when I was still running 20.04, Auto-Correct worked fine -- same
- LibreOffice version, same LibreOffice profile, same LibreOffice
- document, and no changes on my part to my LibreOffice settings since I
- installed Ubuntu 21.04.
+ * Impact
+ 
+ The auto-correction in libreoffice is not action as it should
+ 
+ * Test case
+ 
+ see comment 9
+ 
+ * Regression potential
+ 
+ The changes are in the input handling so check that standard input,
+ keyboard layouts, compose and keybinding as worked as expected on
+ different layout and language type, include ibus and chinese.
+ 
+  
+ I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then 
discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I 
was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, 
same LibreOffice profile, same LibreOffice document, and no changes on my part 
to my LibreOffice settings since I installed Ubuntu 21.04.

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

Title:
  Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Hirsute:
  In Progress

Bug description:
  * Impact

  The auto-correction in libreoffice is not action as it should

  * Test case

  see comment 9

  * Regression potential

  The changes are in the input handling so check that standard input,
  keyboard layouts, compose and keybinding as worked as expected on
  different layout and language type, include ibus and chinese.

   
  I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then 
discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I 
was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, 
same LibreOffice profile, same LibreOffice document, and no changes on my part 
to my LibreOffice settings since I installed Ubuntu 21.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1916851] Re: module-echo-cancel fails on first run

2021-05-12 Thread Sebastien Bacher
Thank you for your bug report, the issue has also been reported upstream
on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1195 ,
you might want to add your comments there

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1195
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1195

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

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1195
   Importance: Unknown
   Status: Unknown

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

Title:
  module-echo-cancel fails on first run

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  I have the following in `.config/pulse/default.pa`:

  ```
  .include /etc/pulse/default.pa
  load-module module-echo-cancel aec_method=webrtc 
aec_args="analog_gain_control=0 digital_gain_control=1"
  ```

  After a reboot, there is no echo cancelled device.

  And then I run `systemctl --user restart pulseaudio` and the echo
  cancelled devices appear.

  That's a bit of a hassle.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shahar39906 F pulseaudio
   /dev/snd/controlC1:  shahar39906 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 16:05:48 2021
  InstallationDate: Installed on 2010-10-12 (3788 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago)
  dmi.bios.date: 10/24/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.1a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: X10SRA
  dmi.product.sku: Default string
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862

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

2021-05-12 Thread Sebastien Bacher
@Brian, sorry about that and thanks for reviewed, the description is
updated now.

@Denys, the situation is frustrating and the SRU team is currently
behind on reviews but ranting at the person who is helping things moving
and actually doing reviews is counterproductive since it risks just
being demotivating and result in even less reviews and more delays...

I do plan to raise the SRU team problem though and see which solutions
could be found going forward but that's a topic for another place than
this bug report

-- 
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 Released

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-05-12 Thread Sebastien Bacher
** Description changed:

- There is a recently introduced bug in evolution-data-server which broke
- access to email in iCloud.
+ * Impact
+ 
+ The Icloud service introduced changes that are confusing evolution-data-
+ server which means evolution is now failing to connect to the email
+ server
+ 
+ * Test case
+ 
+ Set up an iCloud account and try to use it for emails in evolution
+ 
+ * Regression potential
+ 
+ The change is in the imapx connection code, it could create problems
+ with other type of servers so we should try to test on different
+ providers.
+ 
+ 
+ -
+ 
  
  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.

-- 
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 Released

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  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 1926316] Re: lxappearance crashes on launch

2021-05-11 Thread Sebastien Bacher
The glib update has been synced to impish,
https://bugs.launchpad.net/ubuntu/+source/glib2.0/2.68.1-2

There is also a SRU in the hirsute queue

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

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

-- 
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 Released

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 1926843] Re: online accounts integration with fb isn't working

2021-05-10 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ 
+ The online accounts setting are proposing a facebook item which isn't
+ working
+ 
+ * Test case
+ 
+ Go to settings -> online account, browse the accounts option proposed,
+ facebook shouldn't be in the list since it doesn't work.
+ 
+ * Regression potential
+ 
+ The change is to disable the facebook provider using the upstream
+ provided build option. Check that facebook isn't listed anymore but that
+ the other providers still are. Since it's a build option change it could
+ fail to build so check for that as well on launchpad.
+ 
+ Since the facebook service currently doesn't consider gnome-online-
+ accounts as a valid client there should be no user with that provider
+ configured. Even if there were since the service isn't working they
+ would see a functional regression.
+ 
+ ---
+ 
  Hi i tryed to use gnome-control-center online-accounts to make easy like
  windows 10 to login to email or add other login so its more easy with ID
  to use pincode or other ID fingerprint and other.
  
  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.
  
  Worst is facebook only little windows with issue with login?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

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

Title:
  online accounts integration with fb isn't working

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

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1926843] Re: online accounts integration with fb isn't working

2021-05-10 Thread Sebastien Bacher
> its because facebook did not want to use it on linux or safety issue?

no, it's the code in gnome-online-accounts which isn't properly
maintained upstream at the moment, they would need to do changes to the
code and follow the registration process for the service

Ideally that would be fixed and enabled, but until that happens it's
less misleading to not propose the option than to have one that isn't
working

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

Title:
  online accounts integration with fb isn't working

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

Bug description:
  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

2021-05-07 Thread Sebastien Bacher
Thanks, the fix is uploaded and waiting for SRU review now

** Changed in: gtk+3.0 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then
  discovered that Auto-Correct in LibreOffice does not work. Yesterday,
  when I was still running 20.04, Auto-Correct worked fine -- same
  LibreOffice version, same LibreOffice profile, same LibreOffice
  document, and no changes on my part to my LibreOffice settings since I
  installed Ubuntu 21.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1926843] Re: online accounts integration with fb isn't working

2021-05-07 Thread Sebastien Bacher
** Changed in: gnome-online-accounts (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  online accounts integration with fb isn't working

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

Bug description:
  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1923564] Re: BlueZ 5.58 release

2021-05-07 Thread Sebastien Bacher
Uploaded

** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  BlueZ 5.58 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  BlueZ 5.58 has been released. We should look at it for the 21.10
  cycle...

  http://www.bluez.org/release-of-bluez-5-58-and-5-57/
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

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

2021-05-07 Thread Sebastien Bacher
The fix is in the newest version
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/3.40.1-1
and has been SRUed to focal waiting for review

** Changed in: evolution-data-server (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
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 Released

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 1926843] Re: online accounts integration with fb isn't working

2021-05-05 Thread Sebastien Bacher
the fact that thunderbird isn't integrated with the GNOME online
accounts is a known issue and a thunderbird missing feature

** Summary changed:

- gnome-control-center online-accounts poor app to add facebook and other
+ online accounts integration with fb isn't working

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1926843] Re: gnome-control-center online-accounts poor app to add facebook and other

2021-05-05 Thread Sebastien Bacher
Thank you for your bug report, the facebook issue is known and reported
upstream on https://gitlab.gnome.org/GNOME/gnome-online-
accounts/-/issues/128

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #128
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/128

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

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

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1254628] Re: update-notifier crashed with SIGSEGV in rate_limiter_free()

2021-05-04 Thread Sebastien Bacher
upstream consider that one fixed and there was no new activity in years,
closing please open a new bug if you still get an issue in the current
serie

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  update-notifier crashed with SIGSEGV in rate_limiter_free()

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

Bug description:
  1)
  patben@esp-patben-amd:~$ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  2)
  patben@esp-patben-amd:~$ apt-cache policy update-notifier
  update-notifier:
Zainstalowana: 0.147.1
Kandydująca:   0.147.1
Tabela wersji:
   *** 0.147.1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.147 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: update-notifier 0.147.1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 25 07:54:33 2013
  ExecutablePath: /usr/bin/update-notifier
  InstallationDate: Installed on 2013-05-28 (180 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: update-notifier
  SegvAnalysis:
   Segfault happened at: 0x7fbf4f501ae4:mov(%rdi),%rdi
   PC (0x7fbf4f501ae4) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: update-notifier
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_file_monitor_emit_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: update-notifier crashed with SIGSEGV in g_file_monitor_emit_event()
  UpgradeStatus: Upgraded to saucy on 2013-10-30 (25 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1254628/+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 1902768] Re: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

2021-05-03 Thread Sebastien Bacher
@Jussi could you check if you have pipewire installed and if you do try
to uninstall it to see if that makes a difference?

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

Title:
  [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In 20/04 sound worked via headphones worked fine. After upgrade no
  sound is heard and the audio output device list only has HDMI and
  S/PDIF as possible choices. Windows 10 on the same machine works
  without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Nov  3 20:39:59 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-09-19 (44 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to groovy on 2020-11-02 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-12-10 (137 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Tags:  groovy
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1004
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1004:bd08/13/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

2021-05-03 Thread Sebastien Bacher
** Tags added: rls-hh-incoming

-- 
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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2021-04-30 Thread 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 1926661] Re: i think gpu driver isn't working well.

2021-04-30 Thread 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

2021-04-30 Thread 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 1892559] Re: [MIR] ccid opensc pcsc-lite

2021-04-30 Thread 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 1926305] Re: 20.04 Online Accounts - Google Shared Drives

2021-04-30 Thread 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

2021-04-30 Thread 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

2021-04-30 Thread 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

2021-04-30 Thread 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 1926509] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.2+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned

2021-04-30 Thread 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

2021-04-30 Thread 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)

2021-04-30 Thread 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.

2021-04-30 Thread 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

2021-04-30 Thread 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 1892559] Re: [MIR] ccid opensc pcsc-lite

2021-04-30 Thread 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

2021-04-30 Thread 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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-04-30 Thread 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

2021-04-30 Thread 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 

  1   2   3   4   5   6   7   8   9   10   >