date:20210706

This bug was fixed in the package llvm-toolchain-12 -
1:12.0.0-3ubuntu1~20.04.3

---
llvm-toolchain-12 (1:12.0.0-3ubuntu1~20.04.3) focal; urgency=medium

  * control, rules: Fix build on riscv64, force gcc version to 10.
(LP: #1925320)

 -- Timo Aaltonen   Wed, 23 Jun 2021 10:43:21 +0300

** Changed in: llvm-toolchain-12 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1925320

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

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

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

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

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

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions

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

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

This bug was fixed in the package reprepro - 5.3.0-1.3~ubuntu20.04

---
reprepro (5.3.0-1.3~ubuntu20.04) focal; urgency=medium

  * Backport Zstd compressed debs support to hirsute. LP: #1933363

reprepro (5.3.0-1.3) experimental; urgency=medium

  * Non-maintainer upload.
  * Add support for Zstd compressed debs. (LP: #1923845)

reprepro (5.3.0-1.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Flush stdout and stderr before execv of an end hook (Closes: #982423)

 -- Dimitri John Ledkov   Wed, 23 Jun 2021
17:01:44 +0100

** Changed in: reprepro (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: reprepro (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archi

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

This bug was fixed in the package reprepro - 5.3.0-1.3~ubuntu21.04

---
reprepro (5.3.0-1.3~ubuntu21.04) hirsute; urgency=medium

  * Backport Zstd compressed debs support to hirsute. LP: #1933363

reprepro (5.3.0-1.3) experimental; urgency=medium

  * Non-maintainer upload.
  * Add support for Zstd compressed debs. (LP: #1923845)

 -- Dimitri John Ledkov   Wed, 23 Jun 2021
17:01:44 +0100

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed a

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

This bug was fixed in the package reprepro - 5.3.0-1.3~ubuntu20.10

---
reprepro (5.3.0-1.3~ubuntu20.10) groovy; urgency=medium

  * Backport Zstd compressed debs support to hirsute. LP: #1933363

reprepro (5.3.0-1.3) experimental; urgency=medium

  * Non-maintainer upload.
  * Add support for Zstd compressed debs. (LP: #1923845)

reprepro (5.3.0-1.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Flush stdout and stderr before execv of an end hook (Closes: #982423)

 -- Dimitri John Ledkov   Wed, 23 Jun 2021
17:01:44 +0100

** Changed in: reprepro (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages

[Desktop-packages] [Bug 1923845] Update Released

2021-07-06 Thread Chris Halse Rogers

The verification of the Stable Release Update for reprepro has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affe

[Desktop-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

2021-07-06 Thread Hui Wang

@Thibaut,

Doesn't matter, Alex already. provided the log.

Please run below commands and test speaker. If those commands don't
work, I will contact realtek (I guess the spk amplifier is an i2s one,
need special initialization).


sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x10
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0f20
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1b
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0e4b
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x33
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8c00
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x35
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8d6a
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x36
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x5737
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x37
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xfe16
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x38
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x7981
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x45
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xd089
//please test if speaker works.

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+subscriptions

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

[Desktop-packages] [Bug 1934836] Re: Gnome control center crashing when setting display positions

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1934836

Title:
Gnome control center crashing when setting display positions

Status in gnome-control-center package in Ubuntu:
Incomplete

Bug description:
From wake the order of the displays has changed and overlapping. The
control center crashes when trying to move them back into the correct
positions.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
Uname: Linux 5.12.9-051209-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 6 18:38:43 2021
InstallationDate: Installed on 2021-06-09 (27 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
RebootRequiredPkgs: evolution-data-server
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934836/+subscriptions

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

[Desktop-packages] [Bug 1934836] [NEW] Gnome control center crashing when setting display positions

2021-07-06 Thread borillionstar

Public bug reported:

>From wake the order of the displays has changed and overlapping. The
control center crashes when trying to move them back into the correct
positions.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
Uname: Linux 5.12.9-051209-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  6 18:38:43 2021
InstallationDate: Installed on 2021-06-09 (27 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
RebootRequiredPkgs: evolution-data-server
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1934836

Title:
  Gnome control center crashing when setting display positions

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  From wake the order of the displays has changed and overlapping. The
  control center crashes when trying to move them back into the correct
  positions.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  Uname: Linux 5.12.9-051209-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  6 18:38:43 2021
  InstallationDate: Installed on 2021-06-09 (27 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: evolution-data-server
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934836/+subscriptions

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

[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time in Xorg sessions

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #398
   https://gitlab.gnome.org/GNOME/mutter/-/issues/398

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

** Summary changed:

- Desktop briefly becomes unresponsive when typing on 2 keyboards at the same 
time in Xorg sessions
+ Desktop briefly becomes unresponsive when receiving a keypress from a 
different device/mapping than the last keypress (in Xorg)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/108

Title:
  Desktop briefly becomes unresponsive when receiving a keypress from a
  different device/mapping than the last keypress (in Xorg)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions

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

[Desktop-packages] [Bug 1934797] Re: Keyboard freeze for several seconds when I switch language (ENG -> ES)

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

The set of bugs related to this are all linked in bug 108 so let's
use that for now.

** This bug has been marked a duplicate of bug 108
   Desktop briefly becomes unresponsive when typing on 2 keyboards at the same 
time in Xorg sessions

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1934797

Title:
  Keyboard freeze for several seconds when I switch language (ENG -> ES)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Something funny is happening with the mapping of my keyboard when I
  switch language. This provokes that the system is frozen for several
  seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  6 08:45:18 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-11-20 (1689 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-04 (274 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934797/+subscriptions

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

[Desktop-packages] [Bug 1934757] Re: [Dell OptiPlex 9010] Pulseaudio does not recognize integrated audio device

> EDIT: oh, it works again. I'll keep track of this issue. Maybe I
should have started pulseaudio by systemd?

Does that mean there is a bug still?

** Summary changed:

- Pulseaudio does not recognize integrated audio device
+ [Dell OptiPlex 9010] Pulseaudio does not recognize integrated audio device

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1934757

Title:
  [Dell OptiPlex 9010] Pulseaudio does not recognize integrated audio
  device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-
  stereo" in "~/.config/pulse/default.pa". It caused pulseaudio to fail
  with this version. I removed the line and run pulseaudio.

  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

  EDIT: oh, it works again. I'll keep track of this issue. Maybe I
  should have started pulseaudio by systemd?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

Thunderbird can take many seconds to start and close, so sometimes it
does really still have some windows half-prepared in memory but not
visible. That strange state might be a contributing factor.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1933996

Title:
  Alt-tab stops switching windows [JS ERROR: TypeError: window is null
  _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When a new Wayland session is created from a login, Alt-tab works as
  expected to change windows.  After sometime Alt-tab fails to do
  anything (super-tab still works to change applications) and the
  following error is created in syslog:

  gnome-shell[18]: JS ERROR: TypeError: window is
  
null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24

  The only workaround I have found is to logout and log back in, however
  after some time the error repeats itself.

  Ubuntu 21.04
  gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 10:53:32 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-11 (230 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions

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

[Desktop-packages] [Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless

Currently bug 1930359 seems to have nothing to do with this fix, based
on the latest comment 8.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1905825

Title:
  [SRU] Disable CRTCs when system becomes headless

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Committed
Status in mutter source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On new Intel SoCs, after all connectors are unplugged and the system becomes 
headless, it cannot detect monitor hotplug event from type-c port.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561

  Based on "drm/i915 Intel GFX Driver, Hotplug" [1]:
  "Finally, the userspace is responsible for triggering a modeset upon 
receiving the hotplug uevent, disabling or enabling the crtc as needed."

  [Test]
  Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor 
back, monitor is blank.
  With the fix applied, the system can detect monitor again.

  [Where problems could occur]
  This fix disables CRTCs when there's no monitor, if driver has trouble 
dealing with it, we may see something break.

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

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

[Desktop-packages] [Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless

And I wasn't planning on SRUing bug 1841774. If anyone needs to then
they can add the info.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1905825

Title:
  [SRU] Disable CRTCs when system becomes headless

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Committed
Status in mutter source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On new Intel SoCs, after all connectors are unplugged and the system becomes 
headless, it cannot detect monitor hotplug event from type-c port.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561

  Based on "drm/i915 Intel GFX Driver, Hotplug" [1]:
  "Finally, the userspace is responsible for triggering a modeset upon 
receiving the hotplug uevent, disabling or enabling the crtc as needed."

  [Test]
  Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor 
back, monitor is blank.
  With the fix applied, the system can detect monitor again.

  [Where problems could occur]
  This fix disables CRTCs when there's no monitor, if driver has trouble 
dealing with it, we may see something break.

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

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

[Desktop-packages] [Bug 1934584] Re: Text and Icons are not shown after resuming from sleep

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

** This bug has been marked a duplicate of bug 1774053
   Missing characters in gnome-shell after lock screen

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1934584

Title:
  Text and Icons are not shown after resuming from sleep

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Sometimes when resuming from sleep, ubuntu (gnome) does not render all
  text and icons. Lots of text from menus are missing.

  I've added a couple of screenshots as an attachment to illustrate.

  This does not happen everywhere, for example, Chrome, Firefox, and
  Nautilus all look ok by themselves.


  System info:
  ```
  # lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1034.35-oem 5.10.41
  Uname: Linux 5.10.0-1034-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  465.31  Thu May 13 22:24:36 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  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 Jul  4 07:55:42 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 465.31, 5.10.0-1033-oem, x86_64: installed
   nvidia, 465.31, 5.10.0-1034-oem, x86_64: installed
   nvidia, 465.31, 5.8.0-59-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:22c0]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0]
  InstallationDate: Installed on 2020-12-15 (200 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20THCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1034-oem 
root=UUID=ea99ef49-df2d-48fa-9558-61bcea3e36cd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET30W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20THCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20THCTO1WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 3
  dmi.product.name: 20THCTO1WW
  dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3
  dmi.product.version: ThinkPad P1 Gen 3
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/gnome-shell/+bug/1934584/+subscriptions

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

[Desktop-packages] [Bug 1934826] [NEW] [LOW] software-properties should use Breeze theme on Kubuntu

2021-07-06 Thread Omer I.S.

Public bug reported:

software-properties should use Breeze (or any theme in use for Plasma desktop) 
theme on Kubuntu.
Currently, software-properties uses Fusion theme instead of Breeze.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [LOW] software-properties should use Breeze theme on Kubuntu

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties should use Breeze (or any theme in use for Plasma 
desktop) theme on Kubuntu.
  Currently, software-properties uses Fusion theme instead of Breeze.

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

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

[Desktop-packages] [Bug 1926462] Re: Typo 'libreoffice-oopslash' in /usr/lib/libreoffice/program/oosplash

2021-07-06 Thread Adolfo Jayme

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1926462

Title:
  Typo 'libreoffice-oopslash' in /usr/lib/libreoffice/program/oosplash

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Affected package: libreoffice-common (1:6.4.7-0ubuntu0.20.04.1, focal-
  updates)

  While investigating the reason for lot of aa messages flooding my
  kernel logs, I noticed a (supposed) typo in the file
  /usr/lib/libreoffice/program/oosplash at line 17. I guess
  'libreoffice-oopslash' should be 'libreoffice-oopslash'.

  It seems that the issue has already been reported one and a half years ago:
  https://listarchives.libreoffice.org/global/users/2019/msg00812.html

  Fix: Edit /usr/lib/libreoffice/program/oosplash, systemctl reload-or-
  restart apparmor.service, aa-remove-unknown to remove libreoffice-
  oopslash aka :-O/

  PS: My initial "issue" that is filling up my /var/log/kern.log
  persists, but this might be a misconfiguration on my side. :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-common 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 28 16:49:54 2021
  InstallationDate: Installed on 2018-12-11 (869 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-10-26 (184 days ago)

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

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

[Desktop-packages] [Bug 1934825] [NEW] [FEATURE REQUEST] RTL interface for software-properties-qt

2021-07-06 Thread Omer I.S.

Public bug reported:

Please add RTL interface for software-properties-qt. This will improve
its usability for users from the middle east.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [FEATURE REQUEST] RTL interface for software-properties-qt

Status in software-properties package in Ubuntu:
  New

Bug description:
  Please add RTL interface for software-properties-qt. This will improve
  its usability for users from the middle east.

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

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

[Desktop-packages] [Bug 1921949] Re: libreoffice-math save icon reset upon arrow action

2021-07-06 Thread Adolfo Jayme

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1921949

Title:
  libreoffice-math save icon reset upon arrow action

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Won't Fix
Status in libreoffice source package in Focal:
  Won't Fix
Status in libreoffice source package in Groovy:
  Fix Committed
Status in libreoffice source package in Hirsute:
  Fix Committed

Bug description:
  The save icon (in libreoffice-math only) will indicate there are
  changes to be saved. However, if you arrow anywhere, it changes the
  save icon to indicate there are no changes needing to be saved.

  You can close the doc in this state and you *will not* be prompted to
  save/discard changes and all changes will be lost.

  Steps to reproduce:
  1. open new math doc
  2. add any equation -> see the save icon indicates there are changes that 
need to be saved.
  3. arrow anywhere -> see the save icon go back to indicating there are no 
changes.

  You can keep making changes to see the save icon indicate there are
  changes. Then arrow to make it go away. You can do this repeatedly.

  This problem manifests itself in:
    - bionic vm with stock 6.0.7-0ubuntu0.18.04.10
    - focal vm with stock 6.4.6-0ubuntu0.20.04.1
    - hirsute vm with 7.1.2~rc2-0ubuntu0.21.04.1~lo4 (provided by the 
prereleases ppa)
    - a debian 10 vm, with stock 6.1.5-3+deb10u7

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1921949/+subscriptions

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

[Desktop-packages] [Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless

2021-07-06 Thread Brian Murray

Given the regression of mutter in bug 1930359 should the SRU of mutter
for Groovy continue to be pursued? If so bug 1841774 is still missing
SRU information.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1905825

Title:
  [SRU] Disable CRTCs when system becomes headless

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Committed
Status in mutter source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On new Intel SoCs, after all connectors are unplugged and the system becomes 
headless, it cannot detect monitor hotplug event from type-c port.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561

  Based on "drm/i915 Intel GFX Driver, Hotplug" [1]:
  "Finally, the userspace is responsible for triggering a modeset upon 
receiving the hotplug uevent, disabling or enabling the crtc as needed."

  [Test]
  Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor 
back, monitor is blank.
  With the fix applied, the system can detect monitor again.

  [Where problems could occur]
  This fix disables CRTCs when there's no monitor, if driver has trouble 
dealing with it, we may see something break.

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

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

[Desktop-packages] [Bug 1933340] Re: merge package with Debian

2021-07-06 Thread Adolfo Jayme

** Tags added: packaging

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1933340

Title:
  merge package with Debian

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  while looking at LP: #1891623, I noticed that the LO packaging wasn't
  merged for a longer time, not importing some fixes from Debian.
  Please merge the package from Debian, and continue to do that on a
  regular basis.

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

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

[Desktop-packages] [Bug 1925798] Update Released

2021-07-06 Thread Brian Murray

The verification of the Stable Release Update for gupnp has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
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 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

This bug was fixed in the package gupnp - 1.2.4-0ubuntu1

---
gupnp (1.2.4-0ubuntu1) focal; urgency=medium

  * New stable update (lp: #1925798)

 -- Sebastien Bacher   Fri, 23 Apr 2021 15:23:07
+0200

** Changed in: gupnp (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
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 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2021-07-06 Thread audrey reed

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

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Triaged
Status in network-manager source package in Precise:
  Incomplete
Status in dnsmasq package in Debian:
  New

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

  nameserver 192.168.0.1
  nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

  server=192.168.0.1
  server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

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

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

[Desktop-packages] [Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

2021-07-06 Thread Mateusz Stachowski

I've checked the latest focal live image and it has the exact same
glitches as my install.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1934783

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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

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

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

This bug was fixed in the package dpkg - 1.20.9ubuntu2

---
dpkg (1.20.9ubuntu2) impish; urgency=medium

  * build: Switch default dpkg-deb compression from xz to zstd. (LP: #1923845)
Keep compressing dpkg.deb with xz to help bootstrapping on non-Ubuntu
systems.

 -- Balint Reczey   Mon, 14 Jun 2021 16:04:10
+0200

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Committed
Status in reprepro source package in Groovy:
  Fix Committed
Status in reprepro source package in Hirsute:
  Fix Committed
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed a

[Desktop-packages] [Bug 1931264] Re: Random, unsolicited (no mouse or keyboard input), scrolling.

2021-07-06 Thread RodHorning

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

** Changed in: ubuntu-gnome
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1931264

Title:
  Random, unsolicited (no mouse or keyboard input), scrolling.

Status in Ubuntu GNOME:
  New

Bug description:
  Web browsers (and I've also noticed this in the text editor) will
  randomly scroll up and/or down.  This occurs without mouse movement or
  keyboard input.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 89.0+build2-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
  Uname: Linux 5.4.0-74-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tscs-admin  137848 F pulseaudio
  BuildID: 20210527174632
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  8 10:30:40 2021
  ExecutablePath: /usr/lib/firefox/firefox
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-08-02 (676 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.1.1 dev eno1 proto static metric 100 
   169.254.0.0/16 dev eno1 scope link metric 1000 
   192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.222 metric 100
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:355
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-07-25 (318 days ago)
  dmi.bios.date: 07/05/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0125.2011.0705.1517
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0125.2011.0705.1517:bd07/05/2011:svnSeneca:pnpro270296:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
  dmi.product.name: pro270296
  dmi.sys.vendor: Seneca

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

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

[Desktop-packages] [Bug 1931264] Re: Random, unsolicited (no mouse or keyboard input), scrolling.

2021-07-06 Thread RodHorning

I have also encountered this issue with Software & Updates

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1931264

Title:
  Random, unsolicited (no mouse or keyboard input), scrolling.

Status in Ubuntu GNOME:
  New

Bug description:
  Web browsers (and I've also noticed this in the text editor) will
  randomly scroll up and/or down.  This occurs without mouse movement or
  keyboard input.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 89.0+build2-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
  Uname: Linux 5.4.0-74-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tscs-admin  137848 F pulseaudio
  BuildID: 20210527174632
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  8 10:30:40 2021
  ExecutablePath: /usr/lib/firefox/firefox
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-08-02 (676 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.1.1 dev eno1 proto static metric 100 
   169.254.0.0/16 dev eno1 scope link metric 1000 
   192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.222 metric 100
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:355
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-07-25 (318 days ago)
  dmi.bios.date: 07/05/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0125.2011.0705.1517
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0125.2011.0705.1517:bd07/05/2011:svnSeneca:pnpro270296:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
  dmi.product.name: pro270296
  dmi.sys.vendor: Seneca

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

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

[Desktop-packages] [Bug 1934797] [NEW] Keyboard freeze for several seconds when I switch language (ENG -> ES)

2021-07-06 Thread Pablo Q

Public bug reported:

Something funny is happening with the mapping of my keyboard when I
switch language. This provokes that the system is frozen for several
seconds.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  6 08:45:18 2021
DisplayManager: gdm3
InstallationDate: Installed on 2016-11-20 (1689 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-10-04 (274 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1934797

Title:
  Keyboard freeze for several seconds when I switch language (ENG -> ES)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Something funny is happening with the mapping of my keyboard when I
  switch language. This provokes that the system is frozen for several
  seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  6 08:45:18 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-11-20 (1689 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-04 (274 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934797/+subscriptions

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

[Desktop-packages] [Bug 1934761] Re: gnome keyboard settings panel enforces single iso-level3-shift key

2021-07-06 Thread Gunnar Hjalmarsson

When switching to g-c-c 40, the MR

https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/910

was included in Ubuntu as patches to avoid a worse regression. Your
example shows that there is room for improvement of that upstream
proposal. Apparently it hasn't been considered carefully enough how that
new Settings -> Keyboard control plays together with using e.g. Tweaks
for setting XKB options.

@Julian: It would be great if you could add your observation to the
upstream MR.

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: impish

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1934761

Title:
  gnome keyboard settings panel enforces single iso-level3-shift key

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  My Unicomp has a right windows key and alt key in swapped positions,
  so I configured right windows key to act as a second Alt_R (well
  ISO_Level3_Shift), using gnome-tweaks, leading to:

  /org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:rwin_switch']

  Opening the keyboard page in gnome settings resets this to

  /org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:ralt_alt', 'lv3:rwin_switch']

  Effectively disabling the Alt Gr (right alt key) from acting as level
  3 shift.

  Enabling right alt explicitly is not better. That sets

  /org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:ralt_switch', 'lv3:rwin_switch']

  and opening the keyboard panel then just deletes the windows key
  switch:

  
  /org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:ralt_switch']

  Not sure if it's a regression, but it's problematic anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934761/+subscriptions

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

[Desktop-packages] [Bug 1934787] Re: Sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental (main)

2021-07-06 Thread Oibaf

I synced it in my PPA:
https://launchpad.net/~oibaf/+archive/ubuntu/test/+packages?field.name_filter=network-manager-openvpn

It works perfectly, now I can import tls-crypt-v2 certificates!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1934787

Title:
  Sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental
  (main)

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  Please sync network-manager-openvpn 1.8.14-1 (main) from Debian
  experimental (main)

  *NOTE: this release properly support tls-crypt-v2 certifcates, which
  current Ubuntu version fail to import!*

  Explanation of the Ubuntu delta and why it can be dropped:
* Cherry-pick two upstream commits (that were released with 1.8.14) to fix
  connecting to some OpenVPN providers when using openvpn >= 2.5.0
  (LP: #1922423)
  - debian/patches/upstream-56bb08f.patch
  - debian/patches/upstream-353a521.patch

  These changes are cherry picked from 1.8.14, so they are already
  included in Debian 1.8.14-1.

  Changelog entries since current impish version 1.8.12-2ubuntu1:

  network-manager-openvpn (1.8.14-1) experimental; urgency=medium

* New upstream version 1.8.14
* Fix capitalization error in package description

   -- Michael Biebl   Tue, 30 Mar 2021 15:13:23 +0200

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

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

[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

2021-07-06 Thread Hans109h

I'll also confirm that I use Thunderbird and have had other strange
issues with Thunderbird windows not closing correctly after messages are
sent.  The application can be completely killed yet Dock still indicates
that there are windows available (but no way to access them).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1933996

Title:
  Alt-tab stops switching windows [JS ERROR: TypeError: window is null
  _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When a new Wayland session is created from a login, Alt-tab works as
  expected to change windows.  After sometime Alt-tab fails to do
  anything (super-tab still works to change applications) and the
  following error is created in syslog:

  gnome-shell[18]: JS ERROR: TypeError: window is
  
null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24

  The only workaround I have found is to logout and log back in, however
  after some time the error repeats itself.

  Ubuntu 21.04
  gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 10:53:32 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-11 (230 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions

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

[Desktop-packages] [Bug 1934787] [NEW] Sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental (main)

2021-07-06 Thread Oibaf

Public bug reported:

Please sync network-manager-openvpn 1.8.14-1 (main) from Debian
experimental (main)

*NOTE: this release properly support tls-crypt-v2 certifcates, which
current Ubuntu version fail to import!*

Explanation of the Ubuntu delta and why it can be dropped:
  * Cherry-pick two upstream commits (that were released with 1.8.14) to fix
connecting to some OpenVPN providers when using openvpn >= 2.5.0
(LP: #1922423)
- debian/patches/upstream-56bb08f.patch
- debian/patches/upstream-353a521.patch

These changes are cherry picked from 1.8.14, so they are already
included in Debian 1.8.14-1.

Changelog entries since current impish version 1.8.12-2ubuntu1:

network-manager-openvpn (1.8.14-1) experimental; urgency=medium

  * New upstream version 1.8.14
  * Fix capitalization error in package description

 -- Michael Biebl   Tue, 30 Mar 2021 15:13:23 +0200

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1934787

Title:
  Sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental
  (main)

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  Please sync network-manager-openvpn 1.8.14-1 (main) from Debian
  experimental (main)

  *NOTE: this release properly support tls-crypt-v2 certifcates, which
  current Ubuntu version fail to import!*

  Explanation of the Ubuntu delta and why it can be dropped:
* Cherry-pick two upstream commits (that were released with 1.8.14) to fix
  connecting to some OpenVPN providers when using openvpn >= 2.5.0
  (LP: #1922423)
  - debian/patches/upstream-56bb08f.patch
  - debian/patches/upstream-353a521.patch

  These changes are cherry picked from 1.8.14, so they are already
  included in Debian 1.8.14-1.

  Changelog entries since current impish version 1.8.12-2ubuntu1:

  network-manager-openvpn (1.8.14-1) experimental; urgency=medium

* New upstream version 1.8.14
* Fix capitalization error in package description

   -- Michael Biebl   Tue, 30 Mar 2021 15:13:23 +0200

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

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

[Desktop-packages] [Bug 1916323] Re: tracker-extract crashed with signal 31 in GI_fstatat64() from _nl_load_domain()

2021-07-06 Thread Bug Watch Updater

** Changed in: tracker-miners (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/1916323

Title:
  tracker-extract crashed with signal 31 in __GI___fstatat64() from
  _nl_load_domain()

Status in tracker-miners package in Ubuntu:
  Fix Released
Status in tracker-miners package in Debian:
  Fix Released

Bug description:
  The error occurred after apt update / apt upgrade.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker-extract 2.3.5-2
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 20 09:35:03 2021
  ExecutablePath: /usr/libexec/tracker-extract
  InstallationDate: Installed on 2020-12-19 (62 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201218)
  ProcCmdline: /usr/libexec/tracker-extract
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs:
   gnome-shell
   libc6
   libc6
   linux-image-5.10.0-14-generic
   linux-base
  Signal: 31
  SourcePackage: tracker-miners
  StacktraceTop:
   __GI___fstatat64 (fd=fd@entry=15, file=file@entry=0x7fd5ac9dbcd6 "", 
buf=buf@entry=0x7fd56ec0f890, flag=flag@entry=4096) at 
../sysdeps/unix/sysv/linux/fstatat64.c:105
   __GI___fstat64 (fd=fd@entry=15, buf=buf@entry=0x7fd56ec0f890) at 
../sysdeps/unix/sysv/linux/fstat64.c:29
   _nl_load_domain (domain_file=0x7fd56000fdc0, 
domainbinding=domainbinding@entry=0x7fd5600107a0) at loadmsgcat.c:805
   _nl_find_domain (dirname=dirname@entry=0x7fd5ac9e3b00 <_nl_default_dirname> 
"/usr/share/locale", locale=locale@entry=0x7fd56ec0f9f0 "de", 
domainname=domainname@entry=0x7fd56ec0fa10 
"LC_MESSAGES/gnome-control-center-2.0.mo", 
domainbinding=domainbinding@entry=0x7fd5600107a0) at finddomain.c:166
   __dcigettext (domainname=, msgid1=, 
msgid2=, plural=, n=, 
category=) at dcigettext.c:702
  Title: tracker-extract crashed with signal 31 in __GI___fstatat64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1916323/+subscriptions

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

[Desktop-packages] [Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

2021-07-06 Thread Timo Aaltonen

hmm so it was impish which was fine, test hirsute too :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1934783

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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

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

[Desktop-packages] [Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

2021-07-06 Thread Timo Aaltonen

please give the latest focal live image a go:

http://cdimages.ubuntu.com/focal/daily-live/current/


since impish live image worked fine according to bug 1925320, I'm hoping this 
one is fine too

** Also affects: mesa (Ubuntu Focal)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1934783

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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

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

Re: [Desktop-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

2021-07-06 Thread Thibaut Soubrié

Hello,

Many thanks for the tool & instruction. However, the RtHDDump.exe generates
an empty file on my end, even if I run the application in admin mode.

Best Regards,
Thibaut

Le mar. 6 juil. 2021 à 02:15, Hui Wang <1918...@bugs.launchpad.net> a
écrit :

> this is the dumptool in the windows.
>
> ** Attachment added: "RtHDDump_V236.zip"
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+attachment/5509207/+files/RtHDDump_V236.zip
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1918458
>
> Title:
>   [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
>   problem, no sound from speakers, headphones ok
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Expect : sound from speaker
>   Instead, obtain : no sound.
>
>
>   Tried various configuration of /etc/modprobe.d/alsa-conf with :
>
>   options snd-hda-intel model= and
>   options snd-intel-dspcfg dsp_driver=3 or 1
>   and systematic reboot.
>
>   Either I get dummy output, or I get proper output detection, alsamixer
>   and pavucontrol seems 100% ok, but no sound comes from the speakers.
>
>   I'm under a dualboot with Windows 10, BIOS fast boot disabled.
>   Ubuntu 20.04.2 LTS
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
>   Uname: Linux 5.8.0-44-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  thibauts   1522 F pulseaudio
>/dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Mar 10 18:10:30 2021
>   InstallationDate: Installed on 2021-03-09 (1 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp
> failed
>   Symptom_Card: Cannon Point-LP High Definition Audio Controller -
> sof-hda-dsp
>   Symptom_Jack: Grey Speaker, Internal
>   Symptom_Type: Only some of outputs are working
>   Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal]
> Playback problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/24/2019
>   dmi.bios.release: 1.4
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: V1.04
>   dmi.board.asset.tag: Default string
>   dmi.board.name: Guinness_WL
>   dmi.board.vendor: WL
>   dmi.board.version: V1.04
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V1.04
>   dmi.ec.firmware.release: 1.6
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
>   dmi.product.family: Swift 5
>   dmi.product.name: Swift SF515-51T
>   dmi.product.sku: 
>   dmi.product.version: V1.04
>   dmi.sys.vendor: Acer
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+subscriptions
>

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_

[Desktop-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack

2021-07-06 Thread Mateusz Stachowski

I've filed a separate bug.

https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1925320

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

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

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

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

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

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions

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

[Desktop-packages] [Bug 1934783] [NEW] Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

2021-07-06 Thread Mateusz Stachowski

Public bug reported:

Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
Unity, Gnome Shell both sessions (X.org and Wayland).

Also most of the programs have glitches. However Firefox seems
unaffected.

CPU:
  Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
  min/max: 2200/3600 MHz
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
  driver: amdgpu v: kernel
  Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
  unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
  OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
  5.4.0-79-generic LLVM 12.0.0)
  v: 4.6 Mesa 21.0.3

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


** Tags: focal

** Attachment added: "Gnome Shell glitches.jpg"
   
https://bugs.launchpad.net/bugs/1934783/+attachment/5509398/+files/Gnome%20Shell%20glitches.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1934783

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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

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

[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu

2021-07-06 Thread koyakun

Thank you for your detailed instructions.

1. There is a /var/crash/_usr_bin_nautilus.1000.crash file. When I run
ubuntu-bug _usr_bin_nautilus.1000.crash, a window opens which says: 'The
application Files has closed unexpectedly. Send problem report to the
developers? ExecutablePath /usr/bin/nautilus...' However, after I click
'Send', a bug report browser window does not open.

2. Here is the link for '2021-07-06 20:07 2021-07-06 11:07 UTC Crash nautilus':
https://errors.ubuntu.com/oops/1b360ac0-de4f-11eb-9cf8-fa163e6cac46

3. After commenting out line 23 ("'problem_types': ['Bug', 'Package'],") in 
'/etc/apport/crashdb.conf', the bug report browser window opened, so I was able 
to file the bug report, which is here:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934779

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1934579

Title:
  Nautilus crashes when opening places from the dock contextmenu

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 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/ubuntu/+source/nautilus/+bug/1934579/+subscriptions

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

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

2021-07-06 Thread Raph

I have two computers both on Ubuntu 21.04 Wayland and Thunderbird
1:78.11.0+build1-0ubuntu0.21.04.2, and strangely this bug only affects
one of my computer...

I don't know if any additional information from those two machine can
help identifying the bug origin ? or maybe it's already identified ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1932328

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" do 
not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

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

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

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

BTW adding the section to 70-wacom.conf only worked with a fresh install
of Ubuntu 20.04

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1926860

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in xf86-input-wacom package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1926860/+subscriptions

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

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

** Also affects: xf86-input-wacom (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1926860

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in xf86-input-wacom package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1926860/+subscriptions

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

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Pen is now recognized like before in 18.04
It is also working. 


** Attachment added: "Bildschirmfoto von 2021-07-06 13-31-52.png"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+attachment/5509380/+files/Bildschirmfoto%20von%202021-07-06%2013-31-52.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1926860

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in xf86-input-wacom package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1926860/+subscriptions

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

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Tablet is not recognized yet. 
However the the pen can be tested.

** Attachment added: "Bildschirmfoto von 2021-07-06 13-32-13.png"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+attachment/5509381/+files/Bildschirmfoto%20von%202021-07-06%2013-32-13.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1926860

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in xf86-input-wacom package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1926860/+subscriptions

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

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

So it looks like this has to do with the Wacom driver. I am able to get
it to work again but without being able to configure the tablet itself.
However the pen is recognized and working fine.

What I did is specifically add my tablet to the file
/usr/share/X11/xorg.conf.d/70-wacom.conf by adding this section:

Section "InputClass"
Identifier "XP Pen Star 03"
MatchUSBID "5543:0081"
MatchProduct "TABLET 1060N"
MatchDevicePath "/dev/input/event*"
MatchIsTablet "true"
Driver "wacom"
EndSection

This recognizes the pen and also makes the pen come up in the ubuntu
settings under "Wacom Tablet" (see screenshots for details.

Now the question is how can I get the tablet to com up in the settings as well?
And how can it be done so it works out of the box?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1926860

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in xf86-input-wacom package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1926860/+subscriptions

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

[Desktop-packages] [Bug 1931547] Re: DisplayLink displays are black after Mesa update

2021-07-06 Thread Timo Aaltonen

1.20.12 should arrive soon, but I'll include the patch in the meantime

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1931547

Title:
  DisplayLink displays are black after Mesa update

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged
Status in xorg-server source package in Focal:
  Confirmed
Status in xorg-server source package in Hirsute:
  Confirmed
Status in xorg-server source package in Impish:
  Triaged

Bug description:
  Please incorporate xorg-server fix for issue:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183

  It was already merged in to xserver master and xserver-1.20-branch branches.
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683

  This is reported by our users reports on Ubuntu 20.10  with Xserver-1.20.9
  and on Ubuntu 21.04 with XServer-1.20.11

  
  If it is required i am willing to help with anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1931547/+subscriptions

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

[Desktop-packages] [Bug 1934757] Re: Pulseaudio does not recognize integrated audio device

2021-07-06 Thread Jarno Suni

** Description changed:

+ I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo"
+ in "~/.config/pulse/default.pa". It caused pulseaudio to fail with this
+ version. I removed the line and run pulseaudio.
+ 
  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)
  
- EDIT: oh, it works again. I'll keep track of this issue.
+ EDIT: oh, it works again. I'll keep track of this issue. Maybe I should
+ have started pulseaudio by systemd?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1934757

Title:
  Pulseaudio does not recognize integrated audio device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-
  stereo" in "~/.config/pulse/default.pa". It caused pulseaudio to fail
  with this version. I removed the line and run pulseaudio.

  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

  EDIT: oh, it works again. I'll keep track of this issue. Maybe I
  should have started pulseaudio by systemd?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1934757] Re: Pulseaudio does not recognize integrated audio device

2021-07-06 Thread Jarno Suni

** Description changed:

  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)
+ 
+ EDIT: oh, it works again. I'll keep track of this issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1934757

Title:
  Pulseaudio does not recognize integrated audio device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-
  stereo" in "~/.config/pulse/default.pa". It caused pulseaudio to fail
  with this version. I removed the line and run pulseaudio.

  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

  EDIT: oh, it works again. I'll keep track of this issue. Maybe I
  should have started pulseaudio by systemd?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1934761] [NEW] gnome keyboard settings panel enforces single iso-level3-shift key

2021-07-06 Thread Julian Andres Klode

Public bug reported:

My Unicomp has a right windows key and alt key in swapped positions, so
I configured right windows key to act as a second Alt_R (well
ISO_Level3_Shift), using gnome-tweaks, leading to:

/org/gnome/desktop/input-sources/xkb-options
  ['caps:none', 'lv3:rwin_switch']

Opening the keyboard page in gnome settings resets this to

/org/gnome/desktop/input-sources/xkb-options
  ['caps:none', 'lv3:ralt_alt', 'lv3:rwin_switch']

Effectively disabling the Alt Gr (right alt key) from acting as level 3
shift.

Enabling right alt explicitly is not better. That sets

/org/gnome/desktop/input-sources/xkb-options
  ['caps:none', 'lv3:ralt_switch', 'lv3:rwin_switch']

and opening the keyboard panel then just deletes the windows key switch:


/org/gnome/desktop/input-sources/xkb-options
  ['caps:none', 'lv3:ralt_switch']

Not sure if it's a regression, but it's problematic anyway.

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- gnome keyboard settings always set lv3:ralt_alt xkb option when  
lv3:rwin_switch is set
+ gnome keyboard settings enforces single iso-level3-shift key

** Summary changed:

- gnome keyboard settings enforces single iso-level3-shift key
+ gnome keyboard settings panel enforces single iso-level3-shift key

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1934761

Title:
  gnome keyboard settings panel enforces single iso-level3-shift key

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  My Unicomp has a right windows key and alt key in swapped positions,
  so I configured right windows key to act as a second Alt_R (well
  ISO_Level3_Shift), using gnome-tweaks, leading to:

  /org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:rwin_switch']

  Opening the keyboard page in gnome settings resets this to

  /org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:ralt_alt', 'lv3:rwin_switch']

  Effectively disabling the Alt Gr (right alt key) from acting as level
  3 shift.

  Enabling right alt explicitly is not better. That sets

  /org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:ralt_switch', 'lv3:rwin_switch']

  and opening the keyboard panel then just deletes the windows key
  switch:

  
  /org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:ralt_switch']

  Not sure if it's a regression, but it's problematic anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934761/+subscriptions

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

[Desktop-packages] [Bug 1924689] Re: When changing screen scale in GNOME Xorg, gnome-initial-setup's window shadow should not be glitched

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1924689

Title:
  When changing screen scale in GNOME Xorg, gnome-initial-setup's window
  shadow should not be glitched

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-initial-setup package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Ubuntu release:
  Ubuntu 20.04.2 LTS

  Issue description:
  When the gnome-initial-setup launched, if user changes the scale 200 -> 400 
or 100 -> 200.
  There is some garbage on the edge of the window.

  The issue is not seen if we login in wayland session.

  A video is attached.

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

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

[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

2021-07-06 Thread Frank Sokolic

I can also confirm that this issue only happens when I have Thunderbird
open. On my system, Thunderbird opens messages in a new message window
and this is when the problem seems to occur, although it doesn't happen
every time.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1933996

Title:
  Alt-tab stops switching windows [JS ERROR: TypeError: window is null
  _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When a new Wayland session is created from a login, Alt-tab works as
  expected to change windows.  After sometime Alt-tab fails to do
  anything (super-tab still works to change applications) and the
  following error is created in syslog:

  gnome-shell[18]: JS ERROR: TypeError: window is
  
null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24

  The only workaround I have found is to logout and log back in, however
  after some time the error repeats itself.

  Ubuntu 21.04
  gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 10:53:32 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-11 (230 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions

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

[Desktop-packages] [Bug 1934757] [NEW] Pulseaudio does not recognize integrated audio device

2021-07-06 Thread Jarno Suni

Public bug reported:

Unrecognized device:
Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Jul  6 12:16:50 2021
InstallationDate: Installed on 2019-12-05 (578 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
dmi.bios.date: 06/28/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A30
dmi.board.name: 051FJ8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 9010
dmi.product.sku: OptiPlex 9010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal regression-update

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1934757

Title:
  Pulseaudio does not recognize integrated audio device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1868332] Re: Scrolling jumps after switching windows

2021-07-06 Thread Wallace

Seems a xorg issue. Changing to wayland can temporarily avoid this issue

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1868332

Title:
  Scrolling jumps after switching windows

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The bug has to do with mouse scrolling and switching windows; I do not
  know which package it is part of.

  The problem arises when I have two windows of two different
  applications open, such as Google Chrome and a text editor. To
  reproduce the error, I have Google Chrome open initially, then I
  switch tabs (using the shortcut Alt-Tab) to the text editor, then
  scroll around on the text editor. When I Alt-Tab back to Google
  Chrome, my first scroll leads to the page jumping by a large amount
  either up or down before resuming regular mouse scrolling. It is only
  this initial scroll after switching tabs that jumps like this. It also
  happens regardless of whether I use a mouse or the touch pad.

  I also notice, given the same scenario, if I scroll up on the text
  editor, the Google Chrome initial scroll jump will be upward. If I
  scroll down on the text editor, the Chrome jump will be downward. If I
  scroll a lot in the text editor, the Chrome jump will be large. If I
  scroll a small amount in the text editor, the Chrome jump will be
  small.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 17:17:39 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9]
  InstallationDate: Installed on 2020-01-26 (54 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 1WU65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1924689] Re: When changing screen scale in GNOME Xorg, gnome-initial-setup's window shadow should not be glitched

2021-07-06 Thread Yao Wei

Reported to upstream with stripped test case:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1875

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1875
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1875

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1924689

Title:
  When changing screen scale in GNOME Xorg, gnome-initial-setup's window
  shadow should not be glitched

Status in OEM Priority Project:
  New
Status in gnome-initial-setup package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Ubuntu release:
  Ubuntu 20.04.2 LTS

  Issue description:
  When the gnome-initial-setup launched, if user changes the scale 200 -> 400 
or 100 -> 200.
  There is some garbage on the edge of the window.

  The issue is not seen if we login in wayland session.

  A video is attached.

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

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

[Desktop-packages] [Bug 1933168] Re: Show Applications button does not bring up application after setting show-favorites to false

2021-07-06 Thread Sebastien Bacher

** Tags added: rls-ff-incoming

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1933168

Title:
  Show Applications button does not bring up application after setting
  show-favorites to false

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Confirmed

Bug description:
  [Description]
  This happens on Ubuntu 20.04 LTS.  Show Applications icon does not bring up 
application list, if show-favorites is set to false for Ubuntu-dock.  Same 
problem happens if user manually removes all favorite icons from dock.

  [Impact]

   * When users don't want to see favorite app icons on dock, but only
  see opened apps, they use gsettings to hide favorites, Show
  Applications icon will not work correctly.

   * Issue seems to be fixed in latest Ubuntu release already, and since
  Ubuntu 20.04 is an LTS release, it's worth investigating if fix can be
  applied.

   * Users can have more freedom to customize their Ubuntu desktop to
  meet their needs.

   * Error message:
  gnome-shell[2110]: JS ERROR: TypeError: 
Main.overview.viewSelector._activePage is null
  
_onShowAppsButtonToggled@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1912:25

  [Test Plan - Reproduce steps]

   * Set show-favorites to false by following command:
  gsettings set org.gnome.shell.extensions.dash-to-dock show-favorites false

   * Log out/in or reboot

   * Click on show applications button

   * Observe it does not bring up applications

  [Expect results]
  Show Applications button can bring up application

  [Actual results]
  Show Applications button does not do anything, applications won't show up

  [Environment]
  OS: Ubuntu 20.04.2 LTS
  Gnome-shell version: 3.36.7-0ubuntu0.20.04.1
  gnome-shell-extension-ubuntu-dock version: 68ubuntu1~20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1933168/+subscriptions

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

[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

2021-07-06 Thread Florian

Not sure whether the upstream issue, which is several months old, is the
same. The present one seems to have kicked in for several users at the
same time at the end of June 2021.

It looks like it is somehow connected to Thunderbird.

Also see this comment, for one way of reproducing it:
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1934527/comments/4

I can also confirm that it does not seem to occur if Thunderbird isn't
running at all.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1933996

Title:
  Alt-tab stops switching windows [JS ERROR: TypeError: window is null
  _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When a new Wayland session is created from a login, Alt-tab works as
  expected to change windows.  After sometime Alt-tab fails to do
  anything (super-tab still works to change applications) and the
  following error is created in syslog:

  gnome-shell[18]: JS ERROR: TypeError: window is
  
null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24

  The only workaround I have found is to logout and log back in, however
  after some time the error repeats itself.

  Ubuntu 21.04
  gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 10:53:32 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-11 (230 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions

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

[Desktop-packages] [Bug 1934527] Re: Window switching with Alt-Tab stops working after a while

2021-07-06 Thread Krzysztof Raczkowski

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

I've noticed, that problems start just after I create a new message in
Thunderbird and press Send button. Message is sent, its windows is
closed, and from this time dock and alt+tab is broken.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1934527

Title:
  Window switching with Alt-Tab stops working after a while

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 21.04,since around 01 July 2021, Alt-Tab works as usual for
  a while after logging in, but then stops entirely (that is, it does
  nothing; the switcher overlay fails to appear, and switching between
  windows does not work). I made _no_ configuration change, and Alt-Tab
  continues to be configured in the keyboard shortcuts settings as
  usual.

  This has been described by other users here:
  https://askubuntu.com/questions/1349544/alttab-stops-working-after-a
  -while-in-ubuntu-21-04

  There seems to be some possible connection to Thunderbird in
  particular, and the fact that in the left-hand-side launcher (?) /
  favourites of the Ubuntu desktop, the Thunderbird icon starts behaving
  strangely, e.g. does not show the open Thunderbird windows when
  clicking on it ... while other applications work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934527/+subscriptions

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

[Desktop-packages] [Bug 1934584] Re: Text and Icons are not shown after resuming from sleep

** Tags added: suspend-resume

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1934584

Title:
  Text and Icons are not shown after resuming from sleep

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Sometimes when resuming from sleep, ubuntu (gnome) does not render all
  text and icons. Lots of text from menus are missing.

  I've added a couple of screenshots as an attachment to illustrate.

  This does not happen everywhere, for example, Chrome, Firefox, and
  Nautilus all look ok by themselves.


  System info:
  ```
  # lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1034.35-oem 5.10.41
  Uname: Linux 5.10.0-1034-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  465.31  Thu May 13 22:24:36 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  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 Jul  4 07:55:42 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 465.31, 5.10.0-1033-oem, x86_64: installed
   nvidia, 465.31, 5.10.0-1034-oem, x86_64: installed
   nvidia, 465.31, 5.8.0-59-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:22c0]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0]
  InstallationDate: Installed on 2020-12-15 (200 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20THCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1034-oem 
root=UUID=ea99ef49-df2d-48fa-9558-61bcea3e36cd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET30W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20THCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20THCTO1WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 3
  dmi.product.name: 20THCTO1WW
  dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3
  dmi.product.version: ThinkPad P1 Gen 3
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/gnome-shell/+bug/1934584/+subscriptions

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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1934589] Re: No log in button

I can't find any existing requests for this feature. Please also open an
issue upstream at:

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues

for the developers to see.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1934589

Title:
  No log in button

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Can't believe You did it on purpose so reporting it as a bug.

  There is no log in button after entering the password on the login
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934589/+subscriptions

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

[Desktop-packages] [Bug 1934589] Re: No log in button

Oh sorry. There's no login button in the standard theme either. Only a
back button.

As a workaround you can just press Enter instead.

** Changed in: ubuntu
   Importance: Undecided => Wishlist

** Changed in: ubuntu
   Status: Invalid => Triaged

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1934589

Title:
  No log in button

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Can't believe You did it on purpose so reporting it as a bug.

  There is no log in button after entering the password on the login
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934589/+subscriptions

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

[Desktop-packages] [Bug 1934584] Re: Text and Icons are not shown after resuming from sleep

** Tags added: nvidia

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: hybrid multi-gpu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1934584

Title:
  Text and Icons are not shown after resuming from sleep

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Sometimes when resuming from sleep, ubuntu (gnome) does not render all
  text and icons. Lots of text from menus are missing.

  I've added a couple of screenshots as an attachment to illustrate.

  This does not happen everywhere, for example, Chrome, Firefox, and
  Nautilus all look ok by themselves.


  System info:
  ```
  # lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1034.35-oem 5.10.41
  Uname: Linux 5.10.0-1034-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  465.31  Thu May 13 22:24:36 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  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 Jul  4 07:55:42 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 465.31, 5.10.0-1033-oem, x86_64: installed
   nvidia, 465.31, 5.10.0-1034-oem, x86_64: installed
   nvidia, 465.31, 5.8.0-59-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:22c0]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0]
  InstallationDate: Installed on 2020-12-15 (200 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20THCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1034-oem 
root=UUID=ea99ef49-df2d-48fa-9558-61bcea3e36cd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET30W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20THCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20THCTO1WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 3
  dmi.product.name: 20THCTO1WW
  dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3
  dmi.product.version: ThinkPad P1 Gen 3
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/gnome-shell/+bug/1934584/+subscriptions

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

[Desktop-packages] [Bug 1934589] [NEW] No log in button