[Desktop-packages] [Bug 1945817] Re: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

[carnage-mode]

Sorry for not being able to reply :)

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

Title:
  Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

Status in language-selector package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  Description of problem:

  Abyssinica SIL is an old font. It's barely legible and breaks in most
  apps. Noto Serif Ethiopic, on the other hand, is a modern and well
  designed font.

  Noto Serif Ethiopic is distributed with the Open Font License, so
  packaging it won't be a problem.

  Link
  
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amharic=Ethi

  Version: 20.04.3

  How reproducible:
  always

  Steps to Reproduce:
  1. Pretty much using the the Amharic language anywhere on Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1945817/+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 1945817] Re: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

[carnage-mode]

@gunnarhj it will be helpful 100%. You can change it

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

Title:
  Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

Status in language-selector package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  Description of problem:

  Abyssinica SIL is an old font. It's barely legible and breaks in most
  apps. Noto Serif Ethiopic, on the other hand, is a modern and well
  designed font.

  Noto Serif Ethiopic is distributed with the Open Font License, so
  packaging it won't be a problem.

  Link
  
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amharic=Ethi

  Version: 20.04.3

  How reproducible:
  always

  Steps to Reproduce:
  1. Pretty much using the the Amharic language anywhere on Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1945817/+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 1084643] Re: Colour casting on black text using the default renderer pdftops (workaround: use gs)

[Launchpad Bug Tracker]

[Expired for poppler (Ubuntu) because there has been no activity for 60
days.]

** Changed in: poppler (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Colour casting on black text using the default renderer pdftops
  (workaround: use gs)

Status in poppler package in Ubuntu:
  Expired

Bug description:
  For some time now (I think the bug is not specific to Ubuntu 12.10 but
  also present in 12.04), I am having trouble when printing black text
  with an HP Color LaserJet CP1515n, that worked fine on previous Ubuntu
  releases and from other Operating Systems. The output is kind of ok,
  but black text does has a slight red cast, making it look fuzzy. The
  problem exists when printing from LibreOffice, Firefox and Evince.

  Trying different settings and drivers to debug the problem, I came to
  the conclusion that the problem is on the pdftops default renderer. On
  LibreOffice, I went to File - Printer Settings - Properties - Device -
  Printer Language Type and chose Postscript (Level from driver). For
  Firefox and Evince I just used this command from the command line:

  $ lpadmin -p "HP-Color-LaserJet-cp1515n" -o pdftops-renderer-
  default=gs

  (use "pdftops-renderer-default=pdftops" to restore the default)

  Using this settings (gs), the printing results are fine.

  
  $ dpkg -l poppler-utils hplip  cups
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  cups   1.6.1-0ubunt amd64Common UNIX Printing System(tm) -
  ii  hplip  3.12.6-3ubun amd64HP Linux Printing and Imaging Sys
  ii  poppler-utils  0.20.4-0ubun amd64PDF utilities (based on Poppler)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1084643/+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 1182814] Re: [saucy] usb-modeswitch-data bad packaging forces removal of usb-modeswitch

[Launchpad Bug Tracker]

[Expired for usb-modeswitch-data (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: usb-modeswitch-data (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [saucy] usb-modeswitch-data bad packaging forces removal of usb-
  modeswitch

Status in One Hundred Papercuts:
  Expired
Status in usb-modeswitch-data package in Ubuntu:
  Expired

Bug description:
  Ubuntu saucy has usb-modeswitch-data-20120815-1.
  Attempting to upgrade to the latest version usb-modeswitch-data-20121109-3 is 
impossible because of bad packaging which forces removal of usb-modeswitch!!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1182814/+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 1182814] Re: [saucy] usb-modeswitch-data bad packaging forces removal of usb-modeswitch

[Launchpad Bug Tracker]

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  [saucy] usb-modeswitch-data bad packaging forces removal of usb-
  modeswitch

Status in One Hundred Papercuts:
  Expired
Status in usb-modeswitch-data package in Ubuntu:
  Expired

Bug description:
  Ubuntu saucy has usb-modeswitch-data-20120815-1.
  Attempting to upgrade to the latest version usb-modeswitch-data-20121109-3 is 
impossible because of bad packaging which forces removal of usb-modeswitch!!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1182814/+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 1540941] Re: character map font viewer package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/securi

[Launchpad Bug Tracker]

[Expired for adwaita-icon-theme (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: adwaita-icon-theme (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  character map  font viewer package adwaita-icon-theme 3.18.0-2ubuntu1
  failed to install/upgrade: trying to overwrite
  '/usr/share/icons/Adwaita/256x256/status/security-low.png', which is
  also in package adwaita-icon-theme-full 3.18.0-2ubuntu1

Status in One Hundred Papercuts:
  Expired
Status in adwaita-icon-theme package in Ubuntu:
  Expired

Bug description:
  no further information

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: adwaita-icon-theme 3.18.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  2 11:03:53 2016
  DuplicateSignature:
   Unpacking adwaita-icon-theme (3.18.0-2ubuntu2) over (3.18.0-2ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/adwaita-icon-theme_3.18.0-2ubuntu2_all.deb (--unpack):
trying to overwrite 
'/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in 
package adwaita-icon-theme-full 3.18.0-2ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in 
package adwaita-icon-theme-full 3.18.0-2ubuntu1
  InstallationDate: Installed on 2016-02-02 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160201)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: adwaita-icon-theme
  Title: package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: 
trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', 
which is also in package adwaita-icon-theme-full 3.18.0-2ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1540941/+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 1540941] Re: character map font viewer package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/securi

[Launchpad Bug Tracker]

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  character map  font viewer package adwaita-icon-theme 3.18.0-2ubuntu1
  failed to install/upgrade: trying to overwrite
  '/usr/share/icons/Adwaita/256x256/status/security-low.png', which is
  also in package adwaita-icon-theme-full 3.18.0-2ubuntu1

Status in One Hundred Papercuts:
  Expired
Status in adwaita-icon-theme package in Ubuntu:
  Expired

Bug description:
  no further information

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: adwaita-icon-theme 3.18.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  2 11:03:53 2016
  DuplicateSignature:
   Unpacking adwaita-icon-theme (3.18.0-2ubuntu2) over (3.18.0-2ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/adwaita-icon-theme_3.18.0-2ubuntu2_all.deb (--unpack):
trying to overwrite 
'/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in 
package adwaita-icon-theme-full 3.18.0-2ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in 
package adwaita-icon-theme-full 3.18.0-2ubuntu1
  InstallationDate: Installed on 2016-02-02 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160201)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: adwaita-icon-theme
  Title: package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: 
trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', 
which is also in package adwaita-icon-theme-full 3.18.0-2ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1540941/+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 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3

[Launchpad Bug Tracker]

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  when gcc and g++ are set to v4.8 instead of default v5.3

Status in One Hundred Papercuts:
  Expired
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Expired

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1591785/+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 1583881] Re: package texlive-latex-base-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in p

[Launchpad Bug Tracker]

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  package texlive-latex-base-doc (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/doc/texlive-
  doc/latex/url/url.tex.gz', which is also in package texlive-latex-
  recommended-doc 2013.20140215-1

Status in One Hundred Papercuts:
  Expired
Status in texlive-base package in Ubuntu:
  Expired

Bug description:
  This is occurred after upgrading to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: texlive-latex-base-doc (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 11:06:01 2016
  ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
  InstallationDate: Installed on 2015-12-26 (145 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: texlive-base
  Title: package texlive-latex-base-doc (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1583881/+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 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-361 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-361 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  when gcc and g++ are set to v4.8 instead of default v5.3

Status in One Hundred Papercuts:
  Expired
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Expired

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1591785/+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 1583881] Re: package texlive-latex-base-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in p

[Launchpad Bug Tracker]

[Expired for texlive-base (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: texlive-base (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package texlive-latex-base-doc (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/doc/texlive-
  doc/latex/url/url.tex.gz', which is also in package texlive-latex-
  recommended-doc 2013.20140215-1

Status in One Hundred Papercuts:
  Expired
Status in texlive-base package in Ubuntu:
  Expired

Bug description:
  This is occurred after upgrading to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: texlive-latex-base-doc (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 11:06:01 2016
  ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
  InstallationDate: Installed on 2015-12-26 (145 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: texlive-base
  Title: package texlive-latex-base-doc (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1583881/+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 1916341] Re: poppler-utils/pdfimages list function names the wrong color in output table

[Launchpad Bug Tracker]

[Expired for poppler (Ubuntu) because there has been no activity for 60
days.]

** Changed in: poppler (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  poppler-utils/pdfimages list function names the wrong color in output
  table

Status in poppler package in Ubuntu:
  Expired

Bug description:
  When running:

  $ pdfimages -list grayscale-document.pdf

  the output is:

  ```
 page   num  type   width height color comp bpc  enc interp  object ID 
x-ppi y-ppi size ratio
 

1 0 image2556  3288  rgb 3   8  jpeg   no 7  0   
301   300  200K 0.8%
2 1 image2556  3288  rgb 3   8  jpeg   no12  0   
301   300  275K 1.5%
3 2 image2556  3288  rgb 3   8  jpeg   no17  0   
301   300  395K 0.8%
4 3 image2556  3288  rgb 3   8  jpeg   no22  0   
301   300  583K 2.8%
5 4 image2556  3288  rgb 3   8  jpeg   no27  0   
301   300  317K 1.3%
  ...
  ```

  "rgb" is incorrect, which is evident after running: 'pdfimages -all -f
  1 -l 1 grayscale-document.pdf foo && identify -format "%[type]"
  foo-000.jpg', which correctly outputs "Grayscale".

  Strangely, when "pdfimages -list" is fed a bilevel document, it states
  that every page has color "gray".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1916341/+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 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables

[Gunnar Hjalmarsson]

Sponsored to impish and hirsute.

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: gnome-terminal (Ubuntu)
 Assignee: Iain Lane (laney) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: gnome-terminal (Ubuntu Hirsute)
   Status: Confirmed => In Progress

** Changed in: gnome-terminal (Ubuntu Hirsute)
 Assignee: Iain Lane (laney) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Opening new tab in gnome-terminal launched from nautilus loses most
  environment variables

Status in GNOME Terminal:
  Unknown
Status in gnome-terminal package in Ubuntu:
  Fix Committed
Status in gnome-terminal source package in Hirsute:
  In Progress

Bug description:
  [Impact]

  If you launch gnome-terminal by right clicking a directory in
  Nautilus, selecting "Open in Terminal", you get a fully functional
  terminal window.

  If you then press the new tab button, or ctrl-shift-t to open a new
  terminal tab, you will find that most environment variables have
  become unset, and you see the text:

  To run a command as administrator (user "root"), use "sudo ".
  See "man sudo_root" for details.

  Comparing printenv between:

  Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
  Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/

  Most commands won't run in the new terminal tab, due to $HOME and
  $USER not being set.

  Note, if you launch gnome-terminal from gnome-shell or the dock, and
  create a new tab, everything works perfectly. Is something wrong with
  the Nautilus option for "Open in Terminal"?

  [Testcase]

  1. Launch Nautilus to home directory
  2. Right click > "Open in Terminal"
  3. Run "printenv" to see full list of env variables
  4. Click new tab button, or ctrl-shift-t
  5. Run "printenv" see the lack of env variables

  I have a test package available in the below ppa:

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

  The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
  reverted.

  If you install this package, environment variables will be set
  correctly.

  [Where problems could occur]

  I think there is some risk with re-instating a commit which has been
  reverted, and users could run into similar issues as found in the
  upstream bug.

  We do have some supporting evidence that the commit isn't too harmful,
  since it is applied to Groovy currently, things work as intended
  there, and users haven't complained about the issues in the upstream
  bug applying to Groovy.

  If a regression were to occur, then launching a new gnome-terminal or
  opening a new tab could land the user with a terminal with little to
  no environment variables set. A workaround will be to launch gnome-
  terminal from gnome-shell overview.

  [Other info]

  Focal and Groovy have the following commit applied:

  commit fd5ac772154426e2da5afd633b336414bca33be9
  Author: Christian Persch 
  Date:   Mon Mar 23 09:57:56 2020 +0100
  Subject: screen: Use clean env when creating new tab
  Link: 
https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9

  This was then reverted in 3.38.1 due to the upstream bug:

  https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253

  The reverted commit is:

  commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
  Author: Christian Persch 
  Date:   Thu Sep 17 17:10:47 2020 +0200
  Subject: Revert "screen: Use clean env when creating new tab"
  Link: 
https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac

  This revert seems to have broken Hirsute. If we revert the revert,
  that is, apply the commit again, things work as intended.

  To fix this, we need to re-apply
  fd5ac772154426e2da5afd633b336414bca33be9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1922839/+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 1946175] [NEW] gnome disk cannot read SMART data (and self tests) from nvme

[gdp77]

Public bug reported:

It is impossible to select "SMART data and self test" option for nvme
disks. Nvme disks are becoming more common and this functionality should
be added.

I was able to read smart data from my nvme SSD using HDSentinel (linux
version). So it certainly can be done.

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

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

Title:
  gnome disk cannot read SMART data (and self tests) from nvme

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  It is impossible to select "SMART data and self test" option for nvme
  disks. Nvme disks are becoming more common and this functionality
  should be added.

  I was able to read smart data from my nvme SSD using HDSentinel (linux
  version). So it certainly can be done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1946175/+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 1946131] Re: Corruption of display data

[Daniel van Vugt]

Thanks for the bug report. Please attach a photo of the problem. Does it
occur in GNOME or just XFCE?

Also the attached Dependencies.txt seems to show a lot of packages
including graphics packages are from "unknown" origin and don't match
what should be in Ubuntu 21.10. If you can then I would recommend
reinstalling the OS and avoiding all PPAs.

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

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

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

Title:
  Corruption of display data

Status in Ubuntu:
  Incomplete

Bug description:
  Text information and some graphics show artifacts (lines) cancelling
  the text and makes typing almost impossible.  Would like to get a
  screenshot but as soon as the focus goes to another window, the
  artifacts are cleared.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct  5 13:58:10 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.26, 5.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic 
root=UUID=d98fe1f8-02f6-4dda-932a-de98459ddf61 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z170X-Gaming 3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1946131/+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 1946153] Re: [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No sound at all

[Daniel van Vugt]

Please try enabling the newer kernel version available for 20.04:

  sudo apt install linux-generic-hwe-20.04

and then reboot.

** Summary changed:

- [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all
+ [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No sound at all

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

Title:
  [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No
  sound at all

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  laptop is connected to a thinkpad thunderbolt 3 dock, sound worked
  while connect until the latest update a few days ago on 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct  5 16:22:29 2021
  InstallationDate: Installed on 2019-10-18 (717 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET47W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1946153/+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 1946049] Re: Caps LED ON but caps lock is disabled after logout

[Daniel van Vugt]

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

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

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

Title:
  Caps LED ON but caps lock is disabled after logout

Status in GNOME Shell:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  [Summary]
  The Caps LED is on but the caps lock is disable (typing in lowercase) in gdm 
login screen after user login/out twice.

  [Steps to reproduce]
  1. Install Ubuntu 20.04.3
  2. Login and press "Caps lock" button
  3. Make sure the typing output is in uppercase
  4. Logout, back to gdm login screen
  5. Input the password which is in lowercase but the "Caps LED" keeps ON

  ---

  When user login to gnome, the caps lock will be turned off even if the caps 
lock is ON in gdm.
  It looks to me that when initialing a gnome session, it will call 
`state-changed` to make the Caps lock turns off.
  If so, then we could make sure the logout action calls `state-changed` as 
well.

  ---

  $ dpkg -l | grep 'gdm\|gnome-shell\|gdk'
  ii  gdm3   3.36.3-0ubuntu0.20.04.4
   amd64GNOME Display Manager
  ii  gir1.2-gdkpixbuf-2.0:amd64 2.40.0+dfsg-3ubuntu0.2 
   amd64GDK Pixbuf library - GObject-Introspection
  ii  gir1.2-gdm-1.0:amd64   3.36.3-0ubuntu0.20.04.4
   amd64GObject introspection data for the GNOME Display Manager
  ii  gnome-shell3.36.9-0ubuntu0.20.04.2
   amd64graphical shell for the GNOME desktop
  ii  gnome-shell-common 3.36.9-0ubuntu0.20.04.2
   all  common files for the GNOME graphical shell
  ii  gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.2  
   all  AppIndicator/KStatusNotifierItem support for GNOME Shell
  ii  gnome-shell-extension-desktop-icons20.04.0-3~ubuntu20.04.3
   all  desktop icon support for GNOME Shell
  ii  gnome-shell-extension-ubuntu-dock  68ubuntu1~20.04.1  
   all  Ubuntu Dock for GNOME Shell
  ii  libgdk-pixbuf2.0-0:amd64   2.40.0+dfsg-3ubuntu0.2 
   amd64GDK Pixbuf library
  ii  libgdk-pixbuf2.0-bin   2.40.0+dfsg-3ubuntu0.2 
   amd64GDK Pixbuf library (thumbnailer)
  ii  libgdk-pixbuf2.0-common2.40.0+dfsg-3ubuntu0.2 
   all  GDK Pixbuf library - data files
  ii  libgdm13.36.3-0ubuntu0.20.04.4
   amd64GNOME Display Manager (shared library)
  ii  yaru-theme-gnome-shell 20.04.11.1 
   all  Yaru GNOME Shell desktop theme from the Ubuntu Community

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

[Daniel van Vugt]

It might be less contentious to just delete the Focal task.

-- 
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:
  Won't Fix

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 1945992] Re: Onscreen keyboard is to big in 200% scale

[Daniel van Vugt]

Thanks. That's not the GNOME onscreen keyboard so can you tell us which
package you installed to get that keyboard?

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Onscreen keyboard is to big in 200% scale

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  Tags:  focal
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

[Daniel van Vugt]

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

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

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

Bug description:
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1945817] Re: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

[Gunnar Hjalmarsson]

Hey @carnage-mode, where did you go? ;)

I have looked a bit more into this, and my understanding is that there
are two packages — fonts-sil-abyssinica and fonts-freefont-ttf — with
fonts which can render Amharic and which are installed by default on
Ubuntu.

But only by installing fonts-noto-core, without uninstalling any of the
others, I notice a significant difference at e.g.

since it makes use of "Noto Sans Ethiopic".

Final freeze for Ubuntu 21.10 is tomorrow, but if you confirm very soon
that it would be helpful, I can change it so that fonts-noto-core is
automatically installed if you install the Amharic language. If you
would like to see more extensive tweaks, it will need to be discussed
further after the Ubuntu 21.10 release.

Let me know.

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

Title:
  Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

Status in language-selector package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  Description of problem:

  Abyssinica SIL is an old font. It's barely legible and breaks in most
  apps. Noto Serif Ethiopic, on the other hand, is a modern and well
  designed font.

  Noto Serif Ethiopic is distributed with the Open Font License, so
  packaging it won't be a problem.

  Link
  
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amharic=Ethi

  Version: 20.04.3

  How reproducible:
  always

  Steps to Reproduce:
  1. Pretty much using the the Amharic language anywhere on Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1945817/+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 1946168] [NEW] Loss of focus when an application goes full screen

[Javier Blanco]

Public bug reported:

In the last Gnome Shell, when a window switches to fullscreen, it loses
the focus because the desktop is relaunched.

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Loss of focus when an application goes full screen

Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New

Bug description:
  In the last Gnome Shell, when a window switches to fullscreen, it
  loses the focus because the desktop is relaunched.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1946168/+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 1946159] [NEW] Games (eg. splitgate) keeps minimizing to dash when Desktop Icons NG is enabled

[Nicolás Abel Carbone]

Public bug reported:

Steps to reproduce:

* Open a game (splitgate shows the problem, it is free-to-play on Steam)
* Alt-tab out of the game
* Try to come back to the game

Result: The games gains focus for only a second and then is again
minimized to dash.

The problem goes away if the default Desktop Icons NG extension is
disabled.

I am running Ubuntu 21.10 beta using Mesa on a Radeon 5500XT, using
Wayland.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell-extension-desktop-icons-ng 20-0ubuntu1
Uname: Linux 5.14.9-xanmod2 x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  5 20:16:12 2021
InstallationDate: Installed on 2020-11-04 (335 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-shell-extension-desktop-icons-ng
UpgradeStatus: Upgraded to impish on 2021-10-03 (2 days ago)

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish third-party-packages wayland-session

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

Title:
  Games (eg. splitgate) keeps minimizing to dash when Desktop Icons NG
  is enabled

Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  * Open a game (splitgate shows the problem, it is free-to-play on Steam)
  * Alt-tab out of the game
  * Try to come back to the game

  Result: The games gains focus for only a second and then is again
  minimized to dash.

  The problem goes away if the default Desktop Icons NG extension is
  disabled.

  I am running Ubuntu 21.10 beta using Mesa on a Radeon 5500XT, using
  Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-desktop-icons-ng 20-0ubuntu1
  Uname: Linux 5.14.9-xanmod2 x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  5 20:16:12 2021
  InstallationDate: Installed on 2020-11-04 (335 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-desktop-icons-ng
  UpgradeStatus: Upgraded to impish on 2021-10-03 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1946159/+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 1946156] [NEW] [snap] Chromium hangs and is unstable in reproducible ways

[Abonnementspaul]

Public bug reported:

As described on this issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=1256489

Briefly, moving around selected text from the browser and opening
comboboxes are very prone to make the browser freeze for a minute or so.

The binaries distributed by Canonical via Snap do not behave as
expected. Google Chrome builds and AppImage Chromium builds do. This
issue did not occur weeks ago.

I believe the issue comes from the build from Canonical. Issue
reproduced with Snap builds from Stable and Beta channels.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [snap] Chromium hangs and is unstable in reproducible ways

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  As described on this issue:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1256489

  Briefly, moving around selected text from the browser and opening
  comboboxes are very prone to make the browser freeze for a minute or
  so.

  The binaries distributed by Canonical via Snap do not behave as
  expected. Google Chrome builds and AppImage Chromium builds do. This
  issue did not occur weeks ago.

  I believe the issue comes from the build from Canonical. Issue
  reproduced with Snap builds from Stable and Beta channels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1946156/+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 1946153] [NEW] [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all

[Richard Albright]

Public bug reported:

laptop is connected to a thinkpad thunderbolt 3 dock, sound worked while
connect until the latest update a few days ago on 20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Uname: Linux 5.4.0-88-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Tue Oct  5 16:22:29 2021
InstallationDate: Installed on 2019-10-18 (717 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET47W (1.34 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QTCTO1WW
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.modalias: 
dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P1 Gen 2
dmi.product.name: 20QTCTO1WW
dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
dmi.product.version: ThinkPad P1 Gen 2
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  laptop is connected to a thinkpad thunderbolt 3 dock, sound worked
  while connect until the latest update a few days ago on 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct  5 16:22:29 2021
  InstallationDate: Installed on 2019-10-18 (717 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET47W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1946153/+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 1946143] Re: Apply upstream patches to display 5G NSA status

[Ubuntu Foundations Team Bug Bot]

The attachment "libqmi_1-1.28.6-2-focal.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Apply upstream patches to display 5G NSA status

Status in OEM Priority Project:
  New
Status in libqmi package in Ubuntu:
  New

Bug description:
  [Impact]

  The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. 
(LP#1937012)
  The 5G NSA status is supported in the libqmi version 1.30.2.

  The requested upstream patches are listed as below:
  * 5G NSA status patches

https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a
 

  * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected

https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Verify if the field “5G NSA Available: ” can be displayed via executing:

$ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy 
--nas-get-system-info
...
5G NSA Available: 'no'
...

  
  [Where problems could occur]

  The requested upstream patches are for displaying the status information of 
5G NSA network.
  This should not affect existing generic functions.

  
  [Other Info]

  The latest version of libqmi suit can display the 5G NSA status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1945700] Re: [DisplayLink] Settings for multiple displays do not persist

[bartgenuit]

Interestingly, the problem disappears when using Xorg, so it seems to be
only with Wayland.

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

Title:
  [DisplayLink] Settings for multiple displays do not persist

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

Bug description:
  Hi, I'd like to report the following bug. I'm trying to setup multiple
  displays, but whatever settings I try to set, after pressing 'Apply'
  and 'Keep Settings', they revert back to the previous settings.

  I have one built-in laptop display (D1) and one external display (D2),
  connected via a USB-C dock using DisplayLink and HDMI. Display Mode is
  set to 'Join Displays'.

  It seems whatever settings I change, they don't persist. I tried the 
following settings:
  - Change the primary display from (D1) to (D2). Reverts back to (D1) being 
the primary.
  - Change the order of the displays to match my physical setup (D2 on the 
left, D1 on the right). Reverts back to D1 on the left, D2 on the right.
  - Change the order of the displays putting D1 on top of D2. Reverts back to 
D1 on the left, D2 on the right.
  - Change the refresh rate of D2 from 60 Hz to 50 Hz. Reverts back to 60 Hz.

  If you need any further information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 22:27:20 2021
  InstallationDate: Installed on 2021-09-28 (2 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  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/1945700/+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 1946143] Re: Apply upstream patches to display 5G NSA status

[Jerry Lee]

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

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

Title:
  Apply upstream patches to display 5G NSA status

Status in OEM Priority Project:
  New
Status in libqmi package in Ubuntu:
  New

Bug description:
  [Impact]

  The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. 
(LP#1937012)
  The 5G NSA status is supported in the libqmi version 1.30.2.

  The requested upstream patches are listed as below:
  * 5G NSA status patches

https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a
 

  * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected

https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Verify if the field “5G NSA Available: ” can be displayed via executing:

$ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy 
--nas-get-system-info
...
5G NSA Available: 'no'
...

  
  [Where problems could occur]

  The requested upstream patches are for displaying the status information of 
5G NSA network.
  This should not affect existing generic functions.

  
  [Other Info]

  The latest version of libqmi suit can display the 5G NSA status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.

[Jerry Lee]

** Changed in: oem-priority
 Assignee: (unassigned) => Jerry Lee (jerry-lee-tpe)

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  Apply upstream patches to fix problems for Foxconn and Quectel modems.

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
  * for Foxconn T99W175
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9

**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware 
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot 
  7. Verify if the upgraded modem firmware is still working

  
  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems and the status 
information.
  This should not affect existing generic functions and other modems.

  
  [Other Info]

  The firmware and the upgrading application can be downloaded from the 
following link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1946143] [NEW] Apply upstream patches to display 5G NSA status

[Jerry Lee]

Public bug reported:

[Impact]

The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. 
(LP#1937012)
The 5G NSA status is supported in the libqmi version 1.30.2.

The requested upstream patches are listed as below:
* 5G NSA status patches
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a
 

* qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f
 


[Test Plan]

1. Install the Ubuntu image.
2. Boot and login the system.
3. Verify if the field “5G NSA Available: ” can be displayed via executing:

  $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy 
--nas-get-system-info
  ...
5G NSA Available: 'no'
  ...


[Where problems could occur]

The requested upstream patches are for displaying the status information of 5G 
NSA network.
This should not affect existing generic functions.


[Other Info]

The latest version of libqmi suit can display the 5G NSA status.

** Affects: oem-priority
 Importance: Critical
 Assignee: Jerry Lee (jerry-lee-tpe)
 Status: New

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


** Tags: oem-priority

** Package changed: libqmi (Ubuntu) => oem-priority

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

Title:
  Apply upstream patches to display 5G NSA status

Status in OEM Priority Project:
  New
Status in libqmi package in Ubuntu:
  New

Bug description:
  [Impact]

  The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. 
(LP#1937012)
  The 5G NSA status is supported in the libqmi version 1.30.2.

  The requested upstream patches are listed as below:
  * 5G NSA status patches

https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a
 

  * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected

https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Verify if the field “5G NSA Available: ” can be displayed via executing:

$ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy 
--nas-get-system-info
...
5G NSA Available: 'no'
...

  
  [Where problems could occur]

  The requested upstream patches are for displaying the status information of 
5G NSA network.
  This should not affect existing generic functions.

  
  [Other Info]

  The latest version of libqmi suit can display the 5G NSA status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1942951] Re: devhelp doesn't display any help pages

[Sebastien Bacher]

The Debian bug suggests it's due to user config and moving
~/.local/share/mime away workaround the issue, lowering the importance
since it's not impacting most users

** Changed in: webkit2gtk (Ubuntu)
   Importance: High => Low

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

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

Title:
  devhelp doesn't display any help pages

Status in webkit2gtk package in Ubuntu:
  Triaged
Status in webkit2gtk package in Debian:
  Incomplete

Bug description:
  webkit2gtk 2.33.3-1ubuntu3

  Test Case
  -
  1. sudo apt install devhelp libgtk-3-doc
  2. Open devhelp and click the GTK+ 3 Reference Manual link in the left 
sidebar.
  3. The manual should show in the main view area.

  What Happens
  
  The main viewing area stays blank.

  Other Info
  --
  I manually installed webkit2gtk from Ubuntu 21.04 and Devhelp worked normally 
again.
  The Epiphany web browser works fine with the broken webkit2gtk version.
  Ubuntu's packaging diverges slightly from Debian's. The changelog mentions 
some dependency changes and disabling lto.
  I haven't done any further investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1942951/+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 1945061] Re: gdm3 crashed with SIGSEGV in ensure_display_for_seat()

[Sebastien Bacher]

Reported upstream as https://gitlab.gnome.org/GNOME/gdm/-/issues/739 now

** Changed in: gdm3 (Ubuntu)
   Importance: Medium => High

** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #739
   https://gitlab.gnome.org/GNOME/gdm/-/issues/739

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

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

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

Title:
  gdm3 crashed with SIGSEGV in ensure_display_for_seat()

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/131b21d4843931d315a4548121d7d352cfd1e3a8

  ---

  no time for handling, hope everything required in automatically
  attached files

  ubuntu impish proposed

  i5 + amd 6000 (radeon) in hp g6 notebook

  switched from wayland to xorg by adjusting gdm config file

  reason for editing config file: want to try out to switch gpu for
  ui/games

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gdm3 41~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Sep 25 17:42:29 2021
  ExecutablePath: /usr/sbin/gdm3
  ProcCmdline: /usr/sbin/gdm3
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x5638df1e412a:mov(%r15),%rcx
   PC (0x5638df1e412a) ok
   source "(%r15)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdm3
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gdm3 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T17:42:14.958231
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1945061/+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 1945871] Re: Right-clicking in Chrome's "Save As" dialog crashes xdg-desktop-portal-gtk

[Launchpad Bug Tracker]

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

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Status: New => Confirmed

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

Title:
  Right-clicking in Chrome's "Save As" dialog crashes xdg-desktop-
  portal-gtk

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: Ubuntu 21.04
  xdg-desktop-portal-gtk version: 1.8.0-1
  google-chrome-stable version: 94.0.4606.61-1

  Reproduction:

  1. Open Google Chrome - this has been occurring for several months, so 
different versions, but currently the one I have installed is: 94.0.4606.61 
(Official Build) (64-bit)
  2. Right-click on any page, click "Save As" (or download a file, which opens 
the same dialog)

  Expected behavior: A context menu with items such as "Open With File 
Manager", "Rename", etc.
  Actual behavior: "Save As" dialog is closed, and apport is triggered for 
/usr/libexec/xdg-desktop-portal-gtk (I *think* I attached a stack trace here).

  Other apps (firefox, gedit) work as expected here, the problem appears
  specific to Chrome - but Chrome isn't crashing - xdg-desktop-portal-
  gtk is. Therefore I'm starting by filing a bug report here.

  Unfortunately Chrome isn't reporting anything to stdout/stderr about
  this (only some unrelated messages about bluetooth).

  Note: I've attached /var/crash/_usr_libexec_xdg-desktop-portal-
  gtk.1000.crash. However, /var/crash/_usr_libexec_xdg-desktop-portal-
  gtk.1000.uploaded exists, with contents
  68511cc2-2374-11ec-b3f5-fa163e6cac46. I don't see that this actually
  opened a bug anywhere though.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xdg-desktop-portal-gtk 1.8.0-1
  ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  2 18:06:52 2021
  InstallationDate: Installed on 2019-06-25 (829 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xdg-desktop-portal-gtk
  UpgradeStatus: Upgraded to hirsute on 2021-07-30 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1945871/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

[Sebastien Bacher]

Reported upstream now as
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1281

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

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

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

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1946140] Re: /usr/libexec/xdg-desktop-portal-gtk:11:gdk_window_set_transient_for:popover_realize:popover_realize:_gtk_window_add_popover:gtk_popover_update_relative_to

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1945871
   Right-clicking in Chrome's "Save As" dialog crashes xdg-desktop-portal-gtk

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

Title:
  /usr/libexec/xdg-desktop-portal-
  
gtk:11:gdk_window_set_transient_for:popover_realize:popover_realize:_gtk_window_add_popover:gtk_popover_update_relative_to

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1946140/+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 1946140] [NEW] /usr/libexec/xdg-desktop-portal-gtk:11:gdk_window_set_transient_for:popover_realize:popover_realize:_gtk_window_add_popover:gtk_popover_update_relative_to

[errors.ubuntu.com bug bridge]

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

Public bug reported:

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

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic eoan focal groovy hirsute impish

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

Title:
  /usr/libexec/xdg-desktop-portal-
  
gtk:11:gdk_window_set_transient_for:popover_realize:popover_realize:_gtk_window_add_popover:gtk_popover_update_relative_to

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1946140/+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 1936679] Re: ubuntu-drivers --gpgpu is not installing -server packages

[Jeff Lane]

This is still broken as of 1:0.8.6.3~0.18.04.2

$ ubuntu-drivers --gpgpu devices
This is gpgpu mode
== /sys/devices/pci:c9/:c9:02.0/:ca:00.0/:cb:01.0/:cd:00.0 
==
modalias : pci:v10DEd20B5sv10DEsd1533bc03sc02i00
vendor   : NVIDIA Corporation
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-470 - distro non-free recommended
driver   : xserver-xorg-video-nouveau - distro free builtin

This system has 8x A100 compute GPUs, is running Ubuntu Server, and I
specified --gpgpu because I want the server compute drivers.  But U/D is
still insisting on installing the desktop graphics driver instead

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

Title:
  ubuntu-drivers --gpgpu is not installing -server packages

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Discovered while testing the ubuntu-drivers-common package in
  -proposed for bug LP:1898601

  While waiting on bionic to deploy for verification, something was
  bugging me about Focal verification from the other day so I re-
  deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from
  proposed.  What I missed when verifying the other day was that it
  actually isn't installing the -server package on my server in gpgpu
  mode.  After chatting a bit with Alberto, --gpgpu is supposed to
  install the nvidia-driver-VER-server package. Instead, the version in
  -proposed is actually installing nvidia-driver-VER which is incorrect.

  Attached is a tarball from a fresh focal install that includes the
  output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
  --gpgpu debug' after installing the driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1936679/+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 1936679] Re: ubuntu-drivers --gpgpu is not installing -server packages

[Jeff Lane]

$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.8.6.3~0.18.04.2
  Candidate: 1:0.8.6.3~0.18.04.2
  Version table:
 *** 1:0.8.6.3~0.18.04.2 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:0.5.2 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

Title:
  ubuntu-drivers --gpgpu is not installing -server packages

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Discovered while testing the ubuntu-drivers-common package in
  -proposed for bug LP:1898601

  While waiting on bionic to deploy for verification, something was
  bugging me about Focal verification from the other day so I re-
  deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from
  proposed.  What I missed when verifying the other day was that it
  actually isn't installing the -server package on my server in gpgpu
  mode.  After chatting a bit with Alberto, --gpgpu is supposed to
  install the nvidia-driver-VER-server package. Instead, the version in
  -proposed is actually installing nvidia-driver-VER which is incorrect.

  Attached is a tarball from a fresh focal install that includes the
  output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
  --gpgpu debug' after installing the driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1936679/+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 1946131] [NEW] Corruption of display data

[bmarsh]

Public bug reported:

Text information and some graphics show artifacts (lines) cancelling the
text and makes typing almost impossible.  Would like to get a screenshot
but as soon as the focus goes to another window, the artifacts are
cleared.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Oct  5 13:58:10 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.26, 5.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic 
root=UUID=d98fe1f8-02f6-4dda-932a-de98459ddf61 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2015
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-Gaming 3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z170X-Gaming 3
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

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

Title:
  Corruption of display data

Status in xorg package in Ubuntu:
  New

Bug description:
  Text information and some graphics show artifacts (lines) cancelling
  the text and makes typing almost impossible.  Would like to get a
  screenshot but as soon as the focus goes to another window, the
  artifacts are cleared.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct  5 13:58:10 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.26, 5.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic 
root=UUID=d98fe1f8-02f6-4dda-932a-de98459ddf61 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Desktop-packages] [Bug 1946130] Re: Opening a new tab changes environment

[Goyo]

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

** This bug has been marked a duplicate of bug 1922839
   Opening new tab in gnome-terminal launched from nautilus loses most 
environment variables

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

Title:
  Opening a new tab changes environment

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. Open the file manager
  2. Right click -> Open in Terminal
  3. In the terminal type "echo $USER", then press enter. The user name is 
printed in the line below.
  5. Right click in the terminal, select New Tab.
  6. In the terminal type "echo $USER", then press enter. An empty line is 
printed.

  Expected result: in step 6 the user name should be printed.

  There are many other environment variables affected. As a result many
  programs can't be executed or don't behave properly in the second tab.

  When the terminal is launched from the dash, new tabs work as
  expected. Only terminals launched from nautilus are affected. I tried
  to file this against nautilus-extension-gnome-terminal but launchpad
  tells me the package does not exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-terminal 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Oct  5 19:31:06 2021
  InstallationDate: Installed on 2020-05-05 (518 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1946130/+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 1938605] Re: Gnome Terminal "Copy As HTML" produces HTML containing depreciated features

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome Terminal "Copy As HTML" produces HTML containing depreciated
  features

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  If you highlight text in gnome-terminal and right-click it, you get a
  "Copy as HTML" option. The HTML that gnome-terminal generates when
  using that feature contains  tags. font tags were depreciated in
  HTML 4.01, and made obsolete entirely in HTML 5. (See:
  https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font).

  Attached is a sample of the HTML generated by gnome-terminal.

  The correct behavior would be to include style info such as font
  colors inside the "style" attribute of a  tag, rather than using
   tags. That is to say,

  

  should be replaced by

  ,

  and

  

  should be replaced by

  

  This bug exists in gnome terminal through version 3.38.1-1ubuntu1, and
  it exists in Ubuntu 21.04 as well as in prior versions of Ubuntu.

  I've attached both a copy of the output of Copy As HTML, containing
  the deprecated  tag. Below is a fixed version of this output
  that doesn't rely on the  tag:

  alecto@styx:~$ ls apps
  Bitwarden-1.27.1-x86_64_a6df18330216c2546e435c5a9c5df432.AppImage
  gitkraken
  session-desktop-linux-x86_64-1.6.7_18e4489c1ba2c40986ad03ca6522e187.AppImage
  sources
  alecto@styx:~$
  

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

[Seth Arnold]

Now that the security team has some new hires, we're looking at reviving
this series of tasks. Looking through the bug I have come up with the
following outstanding items:

- Add a .symbols file to opensc
- try to add vsmartcard-vpicc + vsmartcard-vpcd autopkgtests
- a formal list of 'supported cards' that we will test with and expect to work
- try to address the awkward path of libraries, /lib/pam_pkcs11/
- make pcscd not run as root 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930530

Did I overlook anything?

Thanks

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

Title:
  [MIR] ccid opensc pcsc-lite

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

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

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

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

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

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

  Has a debian/watch file.
  Quilt packaging.

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

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

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

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

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

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

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

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

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

  Quilt packaging.

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1946130] [NEW] Opening a new tab changes environment

[Goyo]

Public bug reported:

Steps to reproduce

1. Open the file manager
2. Right click -> Open in Terminal
3. In the terminal type "echo $USER", then press enter. The user name is 
printed in the line below.
5. Right click in the terminal, select New Tab.
6. In the terminal type "echo $USER", then press enter. An empty line is 
printed.

Expected result: in step 6 the user name should be printed.

There are many other environment variables affected. As a result many
programs can't be executed or don't behave properly in the second tab.

When the terminal is launched from the dash, new tabs work as expected.
Only terminals launched from nautilus are affected. I tried to file this
against nautilus-extension-gnome-terminal but launchpad tells me the
package does not exist.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-terminal 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Oct  5 19:31:06 2021
InstallationDate: Installed on 2020-05-05 (518 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  Opening a new tab changes environment

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. Open the file manager
  2. Right click -> Open in Terminal
  3. In the terminal type "echo $USER", then press enter. The user name is 
printed in the line below.
  5. Right click in the terminal, select New Tab.
  6. In the terminal type "echo $USER", then press enter. An empty line is 
printed.

  Expected result: in step 6 the user name should be printed.

  There are many other environment variables affected. As a result many
  programs can't be executed or don't behave properly in the second tab.

  When the terminal is launched from the dash, new tabs work as
  expected. Only terminals launched from nautilus are affected. I tried
  to file this against nautilus-extension-gnome-terminal but launchpad
  tells me the package does not exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-terminal 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Oct  5 19:31:06 2021
  InstallationDate: Installed on 2020-05-05 (518 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1946130/+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 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

[Mattia Rizzolo]

** Also affects: gtk+3.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gtk+3.0 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** No longer affects: gtk+3.0 (Ubuntu Hirsute)

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

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

Title:
  GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-
  daemon.plugins.xsettings' does not contain a key named 'antialiasing'

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Focal:
  Confirmed

Bug description:
  Applications running with GTK < 3.24.26 crash when running under GNOME
  40. This was fixed in GTK 3.24.26 by MR
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3219

  Please package either current GTK 3 (3.24.28) or include the given MR
  in the current build.

  Thanks!

  Example crash:

  ```
  Starting program: /home/mjog/Projects/GNOME/geary/+build/test/test-client
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffeb8a7640 (LWP 58239)]
  [New Thread 0x7fffeb086640 (LWP 58240)]
  [New Thread 0x7fffea839640 (LWP 58241)]

  (test-client:58235): GLib-GIO-ERROR **: 10:42:55.448: Settings schema
  'org.gnome.settings-daemon.plugins.xsettings' does not contain a key
  named 'antialiasing'

  Thread 1 "test-client" received signal SIGTRAP, Trace/breakpoint trap.
  0x774a5ea7 in g_log_structured_array () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x774a5ea7 in g_log_structured_array ()
  at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x774a62b9 in g_log_default_handler () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x774a64fe in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x774a67b3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x7735d9d1 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #5  0x7735e030 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #6  0x773625d1 in g_settings_get_enum () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #7  0x710d90ea in update_xft_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:404
  #8  0x710d3c7d in init_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:828
  #9  _gdk_wayland_screen_new (display=0x55a8a0e0)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:1320
  #10 _gdk_wayland_display_open (display_name=)
  at wayland/../../../../../gdk/wayland/gdkdisplay-wayland.c:617
  #11 0x71072635 in gdk_display_manager_open_display
  (manager=, name=0x0) at 
../../../../gdk/gdkdisplaymanager.c:462
  #12 0x76d011fb in gtk_init_check (argc=, 
argv=)
  at ../../../../gtk/gtkmain.c:1110
  #13 gtk_init_check (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1102
  #14 0x76d0122d in gtk_init (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1167
  #15 0x555b4854 in _vala_main (args=0x7fffdda8, args_length1=1)
  at ../test/test-client.vala:32
  #16 0x555b5213 in main (argc=1, argv=0x7fffdda8) at 
../test/test-client.vala:9
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libgtk-3-0 3.24.25-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr  4 11:11:05 2021
  InstallationDate: Installed on 2018-08-13 (964 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to hirsute on 2021-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1922464/+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 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.

[Ubuntu Foundations Team Bug Bot]

The attachment "modemmanager_1-1.16.6-3-focal.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Apply upstream patches to fix problems for Foxconn and Quectel modems.

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
  * for Foxconn T99W175
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9

**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware 
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot 
  7. Verify if the upgraded modem firmware is still working

  
  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems and the status 
information.
  This should not affect existing generic functions and other modems.

  
  [Other Info]

  The firmware and the upgrading application can be downloaded from the 
following link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1943406] Re: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_wins

[Per-Inge]

Updated and tested.
There is no crash at logout or restart

Den tis 5 okt. 2021 kl 17:05 skrev Launchpad Bug Tracker <
1943...@bugs.launchpad.net>:

> This bug was fixed in the package gnome-shell - 40.5-1ubuntu2
>
> ---
> gnome-shell (40.5-1ubuntu2) impish; urgency=medium
>
>   [ Daniel van Vugt ]
>   * debian/patches: Avoid full meta context finalization.
> To workaround (prevent) shutdown crashes (LP: #1936826, #1942031,
> #1942121,
> LP: #1943406, #1944054, #1945010, #1945116, #1944388)
>
>  -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
> 04:52:11 +0200
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: Confirmed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1944583).
> https://bugs.launchpad.net/bugs/1943406
>
> Title:
>   [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in
>   release_expired_buffers_locked() from pb_cache_add_buffer() from
>   pb_destroy() from pb_reference_with_winsys() from
>   radeon_bo_reference()
>
> Status in Mutter:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding gnome-shell.  This problem was most recently seen with package
> version 40.2-1ubuntu6, the problem page at
> https://errors.ubuntu.com/problem/17edbc90dd7001a4a55edc878d9b3719dd3a4815
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker and are a software
> developer, you can request it at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1943406/+subscriptions
>
>

-- 
Skickat från min Sony Xperia eller 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/1943406

Title:
  [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in
  release_expired_buffers_locked() from pb_cache_add_buffer() from
  pb_destroy() from pb_reference_with_winsys() from
  radeon_bo_reference()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1943406/+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 1944388] Re: gnome-shell crashed with SIGSEGV in [strlen() from] g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach()

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.5-1ubuntu2

---
gnome-shell (40.5-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/patches: Avoid full meta context finalization.
To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121,
LP: #1943406, #1944054, #1945010, #1945116, #1944388)

 -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
04:52:11 +0200

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in [strlen() from] g_strdup() from
  g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from
  g_list_foreach()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell crashed with SIGSEGV in g_strdup()

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 21 02:58:40 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_error_copy () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0
   g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0
  Title: gnome-shell crashed with SIGSEGV in g_strdup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1944388/+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 1942121] Re: gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from st_focus_manager_remove_group()

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.5-1ubuntu2

---
gnome-shell (40.5-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/patches: Avoid full meta context finalization.
To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121,
LP: #1943406, #1944054, #1945010, #1945116, #1944388)

 -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
04:52:11 +0200

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from
  g_hash_table_lookup() from st_focus_manager_remove_group()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  This error occurred when I started the system.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 30 15:48:50 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-08-19 (10 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210819)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_hash_table_lookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942121/+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 1936826] Re: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199]

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.5-1ubuntu2

---
gnome-shell (40.5-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/patches: Avoid full meta context finalization.
To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121,
LP: #1943406, #1944054, #1945010, #1945116, #1944388)

 -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
04:52:11 +0200

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  [st-focus-manager.c:199]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae

  ---

  Testing daily Ubuntu Impish ISO 2021-07-19

  Test machine : Dell [Latitude] 7280 (i5-7300U,

  Received the error message - Ubuntu has experienced an internal error
  ...do you want to send ...etc, etc.

  This bug occurred when I was scrolling up and down on the "Settings"
  app and selected "Appearance".

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 19 12:15:54 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2021-07-19 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  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/gnome-shell/+bug/1936826/+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 1944054] Re: [vmwgfx] gnome-shell crashed with SIGSEGV in list_del() from destroy_buffer_locked() from release_expired_buffers_locked() from pb_cache_add_buffer()

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.5-1ubuntu2

---
gnome-shell (40.5-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/patches: Avoid full meta context finalization.
To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121,
LP: #1943406, #1944054, #1945010, #1945116, #1944388)

 -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
04:52:11 +0200

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [vmwgfx] gnome-shell crashed with SIGSEGV in list_del() from
  destroy_buffer_locked() from release_expired_buffers_locked() from
  pb_cache_add_buffer()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/6806a5df1c7ea13bfc98612aea6b83d9a93f1603

  ---

  this happens after start ubuntu21.10 during the login process of gnome

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 18 15:35:16 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2021-09-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210914)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
  Title: gnome-shell crashed with SIGSEGV
  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/gnome-shell/+bug/1944054/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscre

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.5-1ubuntu2

---
gnome-shell (40.5-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/patches: Avoid full meta context finalization.
To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121,
LP: #1943406, #1944054, #1945010, #1945116, #1944388)

 -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
04:52:11 +0200

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension()
  from InitDisplayInfoEntry() from __glXLookupDisplay() from
  CommonMakeCurrent() from cogl_onscreen_glx_dispose() from
  g_object_unref() from clutter_stage_view_finalize()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1942031/+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 1943406] Re: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys()

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.5-1ubuntu2

---
gnome-shell (40.5-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/patches: Avoid full meta context finalization.
To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121,
LP: #1943406, #1944054, #1945010, #1945116, #1944388)

 -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
04:52:11 +0200

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in
  release_expired_buffers_locked() from pb_cache_add_buffer() from
  pb_destroy() from pb_reference_with_winsys() from
  radeon_bo_reference()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1943406/+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 1945010] Re: [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from mm_buffer_destroy() from pb_destroy()

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.5-1ubuntu2

---
gnome-shell (40.5-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/patches: Avoid full meta context finalization.
To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121,
LP: #1943406, #1944054, #1945010, #1945116, #1944388)

 -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
04:52:11 +0200

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from
  mm_buffer_destroy() from pb_destroy()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b

  ---

  gnome-shell crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 25 01:54:33 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945010/+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 1945116] Re: [i915] gnome-shell crashed with SIGSEGV in old_intel_region_release() from old_intel_miptree_release() from intel_free_texture_image_buffer()

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.5-1ubuntu2

---
gnome-shell (40.5-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/patches: Avoid full meta context finalization.
To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121,
LP: #1943406, #1944054, #1945010, #1945116, #1944388)

 -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
04:52:11 +0200

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

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

Title:
  [i915] gnome-shell crashed with SIGSEGV in old_intel_region_release()
  from old_intel_miptree_release() from
  intel_free_texture_image_buffer()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  gnome-shell crashed with SIGSEGV. on login to unity session this error
  report was generated.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep 26 21:35:14 2021
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1630503878
  InstallationDate: Installed on 2021-09-26 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210924)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/anubhav
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
  Title: gnome-shell crashed with SIGSEGV
  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/gnome-shell/+bug/1945116/+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 1946056] Re: Bluetooth sound card not detected, buletooth wont turn on

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth sound card not detected, buletooth wont turn on

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  i turned on bluetooth 
  but it doesn't turn on even after enabling the top right corner button of 
turning on.
  no devices are shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kashmiri   1466 F pulseaudio
   /dev/snd/controlC1:  kashmiri   1466 F pulseaudio
   /dev/snd/pcmC1D0p:   kashmiri   1466 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  5 10:49:05 2021
  InstallationDate: Installed on 2021-09-19 (16 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2014
  dmi.bios.release: 15.17
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 77.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 77.37
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd08/07/2014:br15.17:efr77.37:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097510405F1620180:skuJ3Z06PA#ABG:rvnHewlett-Packard:rn227E:rvr77.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.sku: J3Z06PA#ABG
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1946056/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp

[Mario Limonciello]

Verified on YC with the following combination all from -proposed:

# dpkg -l | grep "linux-firmware\|linux-image-5.14.0-1005-oem\|21.0.3-0ubuntu0."
ii  libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3
 amd64free implementation of the EGL API -- Mesa vendor library
ii  libgbm1:amd64  21.0.3-0ubuntu0.3~20.04.3
 amd64generic buffer management API -- runtime
ii  libgl1-mesa-dri:amd64  21.0.3-0ubuntu0.3~20.04.3
 amd64free implementation of the OpenGL API -- DRI modules
ii  libglapi-mesa:amd6421.0.3-0ubuntu0.3~20.04.3
 amd64free implementation of the GL API -- shared library
ii  libglx-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3
 amd64free implementation of the OpenGL API -- GLX vendor library
ii  linux-firmware 1.187.19 
 all  Firmware for Linux kernel drivers
ii  linux-image-5.14.0-1005-oem5.14.0-1005.5
 amd64Signed kernel image oem

** 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1945227

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

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

[Sebastien Bacher]

let's be realistic while it would be nice to fix we don't have the
resources to commit to it, we could still help uploading if someone want
to work on cherry picking a fix though

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

** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal)
   Status: Incomplete => Won't Fix

-- 
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:
  Won't Fix

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 1931958] Re: 0~git20200629+e7aa92a-8 is FTFBS

[Sebastien Bacher]

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  0~git20200629+e7aa92a-8 is FTFBS

Status in gstreamer1.0 package in Ubuntu:
  Invalid
Status in libcamera package in Ubuntu:
  Fix Released

Bug description:
  Fails to build due to gstreamer using deprecated g_memdup:

  /usr/include/gstreamer-1.0/gst/base/gstbytereader.h: In function ‘guint8* 
gst_byte_reader_dup_data_unchecked(GstByteReader*, guint)’:
  /usr/include/gstreamer-1.0/gst/base/gstbytereader.h:365:41: error: ‘void* 
g_memdup(gconstpointer, guint)’ is deprecated: Use 'g_memdup2' instead 
[-Werror=deprecated-declarations]
365 |   return (guint8 *) g_memdup (data, size);
| ^
  In file included from /usr/include/glib-2.0/glib.h:82,
   from /usr/include/gstreamer-1.0/gst/gst.h:27,
   from ../src/gstreamer/gstlibcamerasrc.h:12,
   from ../src/gstreamer/gstlibcamerasrc.cpp:34:
  /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
257 | gpointer  g_memdup (gconstpointer mem,

  Fixed in gstreamer upstream:
  
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/b16e96dd878e0c5e7baeb8fad62ca43de1f66982

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1931958/+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 1945992] Re: Onscreen keyboard is to big in 200% scale

[Jacek Wróbel]

This is screenshot of my screen in 200% scale.

** Attachment added: "200%.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+attachment/5530720/+files/200%25.png

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

Title:
  Onscreen keyboard is to big in 200% scale

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  Tags:  focal
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+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 1945992] Re: Onscreen keyboard is to big in 200% scale

[Jacek Wróbel]

This is 100% scale

** Attachment added: "100%.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+attachment/5530721/+files/100%25.png

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

Title:
  Onscreen keyboard is to big in 200% scale

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  Tags:  focal
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+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 1945992] Re: Onscreen keyboard is to big in 200% scale

[Jacek Wróbel]

apport information

** Tags added: apport-collected

** Description changed:

  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.20
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-09-26 (8 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
+ RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
+ Tags:  focal
+ Uname: Linux 5.11.0-37-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Onscreen keyboard is to big in 200% scale

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  Tags:  focal
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+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 1945992] monitors.xml.txt

[Jacek Wróbel]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1945992/+attachment/5530715/+files/monitors.xml.txt

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

Title:
  Onscreen keyboard is to big in 200% scale

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  Tags:  focal
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

[Jacek Wróbel]

apport information

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

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

Title:
  Onscreen keyboard is to big in 200% scale

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  Tags:  focal
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

[Jacek Wróbel]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1945992/+attachment/5530714/+files/ShellJournal.txt

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

Title:
  Onscreen keyboard is to big in 200% scale

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  Tags:  focal
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

[Jacek Wróbel]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1945992/+attachment/5530712/+files/GsettingsChanges.txt

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

Title:
  Onscreen keyboard is to big in 200% scale

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I use computer in 200% screen scale. In this scale onscreen keyboard is to 
big so it is useless because there are invisible space, Alt and Ctrl keys. When 
the screen is in 100% scale keyboard is in proper size.
  Moreover there is no possibility to use diacritical marks using onscreen 
keyboard. Diacritical marks are displayed well but when pressed there is no 
effect.
  I tried to check it with different kernels but either on 5.4.0-42 or on 
5.11.0-37 the issue occurs.
  Device: ThinkPad X1 carbon 3 gen.
  System: Ubuntu 20.04.3 gnome-shell x11 window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  Tags:  focal
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+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 1946099] [NEW] Stuck on the Ubuntu Single Sign-On Account | Connecting....

[Amit Nikhade]

Public bug reported:

After making a fresh Ubuntu installation it showed me the windows to
connect the online cloud accounts, as soon as I clicked on Ubuntu single
sign on it pop up the small sized windows to enter the credentials and
when I entered the mail Id and password and clicked on connect. After
this step it keeps connecting forever and it not even gets connected and
neither it gets cancelled by clicking the cancel button.. I tried
installing Ubuntu several time the problem still exist and I haven't
found any solution for that yet. Hope it gets solved soon. Thanks.

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

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

Title:
  Stuck on the Ubuntu Single Sign-On Account | Connecting

Status in gnome-software package in Ubuntu:
  New

Bug description:
  After making a fresh Ubuntu installation it showed me the windows to
  connect the online cloud accounts, as soon as I clicked on Ubuntu
  single sign on it pop up the small sized windows to enter the
  credentials and when I entered the mail Id and password and clicked on
  connect. After this step it keeps connecting forever and it not even
  gets connected and neither it gets cancelled by clicking the cancel
  button.. I tried installing Ubuntu several time the problem still
  exist and I haven't found any solution for that yet. Hope it gets
  solved soon. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1946099/+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 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.

[Jerry Lee]

The .debdiff file “modemmanager_1-1.16.6-3-hirsute.debdiff” is attached
for hirsute(21.04).

The pre-built package :  https://launchpad.net/~jerry-lee-
tpe/+archive/ubuntu/packages/+packages

** Patch added: "modemmanager_1-1.16.6-3-hirsute.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946096/+attachment/5530707/+files/modemmanager_1-1.16.6-3~hirsute.debdiff

** Package changed: modemmanager (Ubuntu) => oem-priority

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

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

Title:
  Apply upstream patches to fix problems for Foxconn and Quectel modems.

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
  * for Foxconn T99W175
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9

**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware 
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot 
  7. Verify if the upgraded modem firmware is still working

  
  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems and the status 
information.
  This should not affect existing generic functions and other modems.

  
  [Other Info]

  The firmware and the upgrading application can be downloaded from the 
following link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.

[Jerry Lee]

The .debdiff file “modemmanager_1-1.16.6-3-focal.debdiff” is attached
for focal(20.04).

The pre-built package : https://launchpad.net/~jerry-lee-
tpe/+archive/ubuntu/packages/+packages

** Patch added: "modemmanager_1-1.16.6-3-focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946096/+attachment/5530706/+files/modemmanager_1-1.16.6-3-focal.debdiff

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

Title:
  Apply upstream patches to fix problems for Foxconn and Quectel modems.

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
  * for Foxconn T99W175
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9

**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware 
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot 
  7. Verify if the upgraded modem firmware is still working

  
  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems and the status 
information.
  This should not affect existing generic functions and other modems.

  
  [Other Info]

  The firmware and the upgrading application can be downloaded from the 
following link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1946098] [NEW] Update to 91.2.0 in impish

[Olivier Tilloy]

Public bug reported:

impish currently has thunderbird 1:91.1.2+build1-0ubuntu1, which at the
time of filing this bug is the latest stable release (so all is good).

There is a new release candidate, 91.2.0+build1
(https://ftp.mozilla.org/pub/thunderbird/candidates/91.2.0-candidates/build1/)
which, if everything goes fine, will become a release before impish is
released.

I intend to upload that RC to impish-proposed, so I'm filing this bug
for the release team to decide whether it's worth accepting in the
release, or leaving it out as a 0-day SRU.

** Affects: thunderbird (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress

** Changed in: thunderbird (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

** Changed in: thunderbird (Ubuntu)
   Status: New => In Progress

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

Title:
  Update to 91.2.0 in impish

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  impish currently has thunderbird 1:91.1.2+build1-0ubuntu1, which at
  the time of filing this bug is the latest stable release (so all is
  good).

  There is a new release candidate, 91.2.0+build1
  (https://ftp.mozilla.org/pub/thunderbird/candidates/91.2.0-candidates/build1/)
  which, if everything goes fine, will become a release before impish is
  released.

  I intend to upload that RC to impish-proposed, so I'm filing this bug
  for the release team to decide whether it's worth accepting in the
  release, or leaving it out as a 0-day SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1946098/+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 1940631] Re: Keep thunderbird 91 in impish-proposed until a point release enables profile upgrades

[Olivier Tilloy]

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

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

Title:
  Keep thunderbird 91 in impish-proposed until a point release enables
  profile upgrades

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Thunderbird 91 was released on August 11. According to the release
  notes (https://www.thunderbird.net/en-
  US/thunderbird/91.0/releasenotes/):

« Thunderbird version 91.0 is only offered as direct download from
  thunderbird.net and not as an upgrade from Thunderbird version 78 or
  earlier. A future release will provide updates from earlier versions.
  »

  To follow upstream's lead on safe upgrades, let's keep 91 in impish-
  proposed for now, until a later point release enables upgrades,
  hopefully before final freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1940631/+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 1946079] Re: ppmraw device no longer produces output (regression)

[Bill Yikes]

Upstream report:

https://bugs.ghostscript.com/show_bug.cgi?id=704500

** Bug watch added: Ghostscript (AFPL) Bugzilla #704500
   http://bugs.ghostscript.com/show_bug.cgi?id=704500

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

Title:
  ppmraw device no longer produces output (regression)

Status in ghostscript package in Ubuntu:
  New

Bug description:
  In version 9.26, the following command worked as expected -- it
  produces a ppm file:

$ gs -sDEVICE=ppmraw -q -r600 -sPAPERSIZE=a4 -dFIXEDMEDIA
  -sPageList=4 -o /tmp/raster.ppm vector.pdf

  But in ghostscript version 9.53.3, that command produces no PPM file,
  and the terminal output is empty. That is, there is no error, warning,
  or indication of progress.

  FWIW, the PDF in my tests was produced by LaTeX.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1946079/+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 1946096] [NEW] Apply upstream patches to fix problems for Foxconn and Quectel modems.

[Jerry Lee]

Public bug reported:

[Impact]

The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
* Foxconn SDX55 T99W175 5G sub6 PCIE Modem
* Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

The requested upstream patches are listed as below:
* for Quectel EM160 4G
  ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
* for Foxconn T99W175
  ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
  
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
  ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
  ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
  ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 


[Test Plan]

1. Install the Ubuntu image.
2. Boot and login the system.
3. Prepare the modem’s firmware and install the firmware upgrading application 
provided by Foxconn and Quectel
4. Using the firmware upgrading application to upgrade the modem’s firmware 
5. Verify if the modem’s firmware upgrading is successful
6. Reboot 
7. Verify if the upgraded modem firmware is still working


[Where problems could occur]

The requested upstream patches are for these 2 specific modems and the status 
information.
This should not affect existing generic functions and other modems.


[Other Info]

The firmware and the upgrading application can be downloaded from the following 
link:
* LP#1943774 for Quectel modems
* LP#1943780 for Foxconn modems

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


** Tags: oem-priority

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

Title:
  Apply upstream patches to fix problems for Foxconn and Quectel modems.

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
  * for Foxconn T99W175
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9

**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware 
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot 
  7. Verify if the upgraded modem firmware is still working

  
  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems and the status 
information.
  This should not affect existing generic functions and other modems.

  
  [Other Info]

  The firmware and the upgrading application can be downloaded from the 
following link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946096/+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 1771880] Re: Seahorse unable to import pkcs12 certificates

[Meluco]

I can't undestand why this bug still unatended.

Certificates and signing is a common practice for today. This bug
affects any application who searchs for certificates on operating system
storage.

Install the same certificate many times in multiple applications
increase probabilities for vulnerabilities impacts and private key
leaks.

It impacts in user experience too, and make hard to handle digital
identities in Ubuntu for personal and SOHO users.

Finally, it impacts Ubuntu image.
less deb
Please, considere to change priority for this bug.


** Attachment added: "Import disabled"
   
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880/+attachment/5530692/+files/Captura%20de%20pantalla%20de%202021-10-05%2013-20-04.png

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  New
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in seahorse package in Ubuntu:
  Triaged
Status in gnome-keyring package in Fedora:
  New
Status in seahorse package in Fedora:
  Unknown

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/1771880/+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 1946049] Re: Caps LED ON but caps lock is disabled after logout

[jeremyszu]

@Daniel,

I'm not quite sure it's related to gnome-shell.
I just shared what I found here and could be solved by gnome-shell.
If upstream things there is the other appropriate place to fix then I can 
create the other thread on that project.

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4667
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4667

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

Title:
  Caps LED ON but caps lock is disabled after logout

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  The Caps LED is on but the caps lock is disable (typing in lowercase) in gdm 
login screen after user login/out twice.

  [Steps to reproduce]
  1. Install Ubuntu 20.04.3
  2. Login and press "Caps lock" button
  3. Make sure the typing output is in uppercase
  4. Logout, back to gdm login screen
  5. Input the password which is in lowercase but the "Caps LED" keeps ON

  ---

  When user login to gnome, the caps lock will be turned off even if the caps 
lock is ON in gdm.
  It looks to me that when initialing a gnome session, it will call 
`state-changed` to make the Caps lock turns off.
  If so, then we could make sure the logout action calls `state-changed` as 
well.

  ---

  $ dpkg -l | grep 'gdm\|gnome-shell\|gdk'
  ii  gdm3   3.36.3-0ubuntu0.20.04.4
   amd64GNOME Display Manager
  ii  gir1.2-gdkpixbuf-2.0:amd64 2.40.0+dfsg-3ubuntu0.2 
   amd64GDK Pixbuf library - GObject-Introspection
  ii  gir1.2-gdm-1.0:amd64   3.36.3-0ubuntu0.20.04.4
   amd64GObject introspection data for the GNOME Display Manager
  ii  gnome-shell3.36.9-0ubuntu0.20.04.2
   amd64graphical shell for the GNOME desktop
  ii  gnome-shell-common 3.36.9-0ubuntu0.20.04.2
   all  common files for the GNOME graphical shell
  ii  gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.2  
   all  AppIndicator/KStatusNotifierItem support for GNOME Shell
  ii  gnome-shell-extension-desktop-icons20.04.0-3~ubuntu20.04.3
   all  desktop icon support for GNOME Shell
  ii  gnome-shell-extension-ubuntu-dock  68ubuntu1~20.04.1  
   all  Ubuntu Dock for GNOME Shell
  ii  libgdk-pixbuf2.0-0:amd64   2.40.0+dfsg-3ubuntu0.2 
   amd64GDK Pixbuf library
  ii  libgdk-pixbuf2.0-bin   2.40.0+dfsg-3ubuntu0.2 
   amd64GDK Pixbuf library (thumbnailer)
  ii  libgdk-pixbuf2.0-common2.40.0+dfsg-3ubuntu0.2 
   all  GDK Pixbuf library - data files
  ii  libgdm13.36.3-0ubuntu0.20.04.4
   amd64GNOME Display Manager (shared library)
  ii  yaru-theme-gnome-shell 20.04.11.1 
   all  Yaru GNOME Shell desktop theme from the Ubuntu Community

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946049/+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 1946082] Re: gnome-shell crashed with SIGSEGV in __pthread_kill_internal()

[Daniel van Vugt]

I'm not sure that's the right bug ID. Can you please tell us the
contents of /var/lib/whoopsie/whoopsie-id  on this machine?

Also if you are experiencing gnome-shell bugs of any sort then it's a
good idea to disable all non-Ubuntu extensions in the 'Extensions' app
and then log in again. Because extensions cause so many bugs, that's
always the first thing to try.

** Information type changed from Public to Private

** This bug is no longer a duplicate of bug 1942121
   gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from 
g_hash_table_lookup() from st_focus_manager_remove_group()

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

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

Title:
  gnome-shell crashed with SIGSEGV in __pthread_kill_internal()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This every time happens when:
  1- Start pc
  2- Session goes into Wayland without having selected it
  3- click on Firefox icon in the apps bar

  Then the pc freezes, the only way to recover is by a hard reset.

  Now I'm disabling Wayland for good and defaulting to Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  5 10:14:18 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-07-23 (74 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __pthread_kill_internal (signo=11, threadid=) at 
pthread_kill.c:45
   __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
pthread_kill.c:62
   __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
  Title: gnome-shell crashed with SIGSEGV in __pthread_kill_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946082/+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 1946079] Re: ppmraw device no longer produces output (regression)

[Till Kamppeter]

This is an upstream bug in Ghostscript, please report it on

https://bugs.ghostscript.com/

including the Ghostscript command line and the input file. Please also
post a link to that bug report here.

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

Title:
  ppmraw device no longer produces output (regression)

Status in ghostscript package in Ubuntu:
  New

Bug description:
  In version 9.26, the following command worked as expected -- it
  produces a ppm file:

$ gs -sDEVICE=ppmraw -q -r600 -sPAPERSIZE=a4 -dFIXEDMEDIA
  -sPageList=4 -o /tmp/raster.ppm vector.pdf

  But in ghostscript version 9.53.3, that command produces no PPM file,
  and the terminal output is empty. That is, there is no error, warning,
  or indication of progress.

  FWIW, the PDF in my tests was produced by LaTeX.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1946079/+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 1946082] Re: gnome-shell crashed with SIGSEGV in __pthread_kill_internal()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1942121, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1946082/+attachment/5530662/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1946082/+attachment/5530664/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1946082/+attachment/5530668/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1946082/+attachment/5530669/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1946082/+attachment/5530670/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1946082/+attachment/5530673/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1946082/+attachment/5530674/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1942121
   gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from 
g_hash_table_lookup() from st_focus_manager_remove_group()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in __pthread_kill_internal()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This every time happens when:
  1- Start pc
  2- Session goes into Wayland without having selected it
  3- click on Firefox icon in the apps bar

  Then the pc freezes, the only way to recover is by a hard reset.

  Now I'm disabling Wayland for good and defaulting to Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  5 10:14:18 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-07-23 (74 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __pthread_kill_internal (signo=11, threadid=) at 
pthread_kill.c:45
   __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
pthread_kill.c:62
   __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
  Title: gnome-shell crashed with SIGSEGV in __pthread_kill_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946082/+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 1946079] [NEW] ppmraw device no longer produces output (regression)

[Bill Yikes]

Public bug reported:

In version 9.26, the following command worked as expected -- it produces
a ppm file:

  $ gs -sDEVICE=ppmraw -q -r600 -sPAPERSIZE=a4 -dFIXEDMEDIA -sPageList=4
-o /tmp/raster.ppm vector.pdf

But in ghostscript version 9.53.3, that command produces no PPM file,
and the terminal output is empty. That is, there is no error, warning,
or indication of progress.

FWIW, the PDF in my tests was produced by LaTeX.

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

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

Title:
  ppmraw device no longer produces output (regression)

Status in ghostscript package in Ubuntu:
  New

Bug description:
  In version 9.26, the following command worked as expected -- it
  produces a ppm file:

$ gs -sDEVICE=ppmraw -q -r600 -sPAPERSIZE=a4 -dFIXEDMEDIA
  -sPageList=4 -o /tmp/raster.ppm vector.pdf

  But in ghostscript version 9.53.3, that command produces no PPM file,
  and the terminal output is empty. That is, there is no error, warning,
  or indication of progress.

  FWIW, the PDF in my tests was produced by LaTeX.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1946079/+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 1946078] [NEW] package libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller av

[napoléon]

Public bug reported:

Bonjour,je sais que  ma version est beaucoup trop ancienne,j'ustement a
chaque fois que j'utilise la ligne de commande je ne peux rien faire a
chaque fois le ( package lib tracker-sparql) m'en empéche, j'aimerai
comprendre ?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-210-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
Date: Tue Oct  5 10:32:41 2021
DpkgHistoryLog:
 Start-Date: 2021-10-05  10:32:33
 Commandline: apt install grub
 Requested-By: thomas (1000)
 Install: libc6-i386:amd64 (2.23-0ubuntu11.3, automatic), grub:amd64 
(0.97-29ubuntu68)
 Remove: grub2-common:amd64 (2.02~beta2-36ubuntu3.32), grub-pc:amd64 
(2.02~beta2-36ubuntu3.32), grub-gfxpayload-lists:amd64 (0.7)
ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  le 
réinstaller avant de tenter de le configurer.
InstallationDate: Installed on 2018-09-14 (1116 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.7
 apt  1.2.35
SourcePackage: tracker
Title: package libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 failed to 
install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

** Description changed:

  Bonjour,je sais que  ma version est beaucoup trop ancienne,j'ustement a
  chaque fois que j'utilise la ligne de commande je ne peux rien faire a
  chaque fois le ( package lib tracker-sparql) m'en empéche, j'aimerai
  comprendre ?
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
  Uname: Linux 4.4.0-210-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: amd64
  Date: Tue Oct  5 10:32:41 2021
  DpkgHistoryLog:
-  Start-Date: 2021-10-05  10:32:33
-  Commandline: apt install grub
-  Requested-By: thomas (1000)
-  Install: libc6-i386:amd64 (2.23-0ubuntu11.3, automatic), grub:amd64 
(0.97-29ubuntu68)
-  Remove: grub2-common:amd64 (2.02~beta2-36ubuntu3.32), grub-pc:amd64 
(2.02~beta2-36ubuntu3.32), grub-gfxpayload-lists:amd64 (0.7)
+  Start-Date: 2021-10-05  10:32:33
+  Commandline: apt install grub
+  Requested-By: thomas (1000)
+  Install: libc6-i386:amd64 (2.23-0ubuntu11.3, automatic), grub:amd64 
(0.97-29ubuntu68)
+  Remove: grub2-common:amd64 (2.02~beta2-36ubuntu3.32), grub-pc:amd64 
(2.02~beta2-36ubuntu3.32), grub-gfxpayload-lists:amd64 (0.7)
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2018-09-14 (1116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.7
-  apt  1.2.35
+  dpkg 1.18.4ubuntu1.7
+  apt  1.2.35
  SourcePackage: tracker
  Title: package libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 failed to 
install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 failed to
  install/upgrade: le paquet est dans un état vraiment incohérent; vous
  devriez  le réinstaller avant de tenter de le configurer.

Status in tracker package in Ubuntu:
  New

Bug description:
  Bonjour,je sais que  ma version est beaucoup trop ancienne,j'ustement
  a chaque fois que j'utilise la ligne de commande je ne peux rien faire
  a chaque fois le ( package lib tracker-sparql) m'en empéche, j'aimerai
  comprendre ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
  Uname: Linux 4.4.0-210-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: amd64
  Date: Tue Oct  5 10:32:41 2021
  DpkgHistoryLog:
   Start-Date: 2021-10-05  10:32:33
   Commandline: apt install grub
   Requested-By: thomas (1000)
   Install: libc6-i386:amd64 (2.23-0ubuntu11.3, automatic), grub:amd64 
(0.97-29ubuntu68)
   Remove: grub2-common:amd64 (2.02~beta2-36ubuntu3.32), grub-pc:amd64 
(2.02~beta2-36ubuntu3.32), grub-gfxpayload-lists:amd64 (0.7)
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2018-09-14 (1116 days ago)
  

[Desktop-packages] [Bug 1945227] Re: drm/amdgpu: Add support for Yellow Carp

[Andy Whitcroft]

Hello Timo, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.19 in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: linux-firmware (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1858168] Re: Ubuntu 19.10 after updating the "Other Software" tab in "Software & Updates" the "cache refresh" hangs

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Ubuntu 19.10 after updating the "Other Software" tab in "Software &
  Updates" the "cache refresh" hangs

Status in software-properties package in Ubuntu:
  Won't Fix

Bug description:
  Running the command from a terminal window The following messages are
  logged when the hang occurs:

  simon@Ubuntu-2600K:~$ sudo software-properties-gtk
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.Error: pk-client-error-quark: W: Skipping acquire of 
configured file 'main/binary-i386/Packages' as repository 
'http://packages.microsoft.com/repos/vscode stable InRelease' doesn't support 
architecture 'i386'
  E: The repository 
'http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu eoan 
Release' does not have a Release file.
  W: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  W: See apt-secure(8) manpage for repository creation and user configuration 
details.
   (319)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

  I note similar issues reported for other functions however, these seem
  to have been resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1858168/+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 1946056] Re: Bluetooth sound card not detected, buletooth wont turn on

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Bluetooth sound card not detected, buletooth wont turn on

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i turned on bluetooth 
  but it doesn't turn on even after enabling the top right corner button of 
turning on.
  no devices are shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kashmiri   1466 F pulseaudio
   /dev/snd/controlC1:  kashmiri   1466 F pulseaudio
   /dev/snd/pcmC1D0p:   kashmiri   1466 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  5 10:49:05 2021
  InstallationDate: Installed on 2021-09-19 (16 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2014
  dmi.bios.release: 15.17
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 77.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 77.37
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd08/07/2014:br15.17:efr77.37:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097510405F1620180:skuJ3Z06PA#ABG:rvnHewlett-Packard:rn227E:rvr77.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.sku: J3Z06PA#ABG
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1946056/+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 1946056] [NEW] Bluetooth sound card not detected, buletooth wont turn on

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

i turned on bluetooth 
but it doesn't turn on even after enabling the top right corner button of 
turning on.
no devices are shown.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kashmiri   1466 F pulseaudio
 /dev/snd/controlC1:  kashmiri   1466 F pulseaudio
 /dev/snd/pcmC1D0p:   kashmiri   1466 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  5 10:49:05 2021
InstallationDate: Installed on 2021-09-19 (16 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2014
dmi.bios.release: 15.17
dmi.bios.vendor: Insyde
dmi.bios.version: F.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 227E
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 77.25
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 77.37
dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd08/07/2014:br15.17:efr77.37:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097510405F1620180:skuJ3Z06PA#ABG:rvnHewlett-Packard:rn227E:rvr77.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.sku: J3Z06PA#ABG
dmi.product.version: 097510405F1620180
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug focal
-- 
Bluetooth sound card not detected, buletooth wont turn on
https://bugs.launchpad.net/bugs/1946056
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-driver in Ubuntu.

-- 
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 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()

[Daniel van Vugt]

Only tracking in
https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95
now, which only affects focal and later.


** Description changed:

  https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d
  https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95
- https://errors.ubuntu.com/problem/73a2092e4c2d306d8a8e329a29a0f6ffd9a2dfeb
  
  ---
  
  Todays update had a kernal and   my gnome shell update. Happened when I
  rebooted.  I now have a black screen and no panel. Icons are all that
  shows up on desktop.
  
  ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul  3 12:46:31 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: gnome-shell --sm-client-id 
102c52716a25d9b2dd1495780366603150001329
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9bec254d5c 
:  movzbl 0x14(%rax),%edx
   PC (0x7f9bec254d5c) ok
   source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_theme_get_custom_stylesheets () from 
/usr/lib/gnome-shell/libgnome-shell.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

- https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d
  https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95
  
  ---
  
  Todays update had a kernal and   my gnome shell update. Happened when I
  rebooted.  I now have a black screen and no panel. Icons are all that
  shows up on desktop.
  
  ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul  3 12:46:31 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: gnome-shell --sm-client-id 
102c52716a25d9b2dd1495780366603150001329
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9bec254d5c 
:  movzbl 0x14(%rax),%edx
   PC (0x7f9bec254d5c) ok
   source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_theme_get_custom_stylesheets () from 
/usr/lib/gnome-shell/libgnome-shell.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Tags added: hirsute impish

** Tags removed: bionic

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

Title:
  gnome-shell crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a() from g_object_ref() from
  st_theme_get_custom_stylesheets()

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95

  ---

  Todays update had a kernal and   my gnome shell update. Happened when
  I rebooted.  I now have a black screen and no panel. Icons are all
  that shows up on desktop.

  ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul  3 12:46:31 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: 

[Desktop-packages] [Bug 1886405] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_unload_stylesheet:ffi_call_unix64:ffi_call_int

[Daniel van Vugt]

No crashes since 3.36 so consider it fixed.

** This bug is no longer a duplicate of bug 1702151
   gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a() from g_object_ref() from 
st_theme_get_custom_stylesheets()

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

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

Title:
  /usr/bin/gnome-
  
shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_unload_stylesheet:ffi_call_unix64:ffi_call_int

Status in gnome-shell package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886405/+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 1759167] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_get_custom_stylesheets:ffi_call_unix64:ffi_call

[Daniel van Vugt]

No crashes since 3.36 so consider it fixed.

Although bug 1702151 is still open.

** This bug is no longer a duplicate of bug 1702151
   gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a() from g_object_ref() from 
st_theme_get_custom_stylesheets()

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

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

Title:
  /usr/bin/gnome-
  
shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_get_custom_stylesheets:ffi_call_unix64:ffi_call

Status in gnome-shell package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759167/+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 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta

[Daniel van Vugt]

If the problem is that you get a session different to what you expected
then please:

1. Reboot.

2. Log in.

3. If the session type is not what you expected then run:

   journalctl -b0 > wrongsession.txt

   and attach the resulting text file here.

4. If the session type is what you expected then goto 1.


** Changed in: gdm3 (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  [nvidia] gdm3 do not connect to the right session on 21.10 beta

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  I've updated to 21.10 beta to test wayland for nvidia successfully.

  Even when the dot is for "ubuntu with wayland" choice, gdm3 launch X11
  session

  I have to select "ubuntu with wayland" to have the wayland session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+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 1727716] Re: 17.10 sticky keys doesn t work

[Daniel van Vugt]

Fixed in 3.28 onward

** Bug watch added: bugzilla.gnome.org/ #788564
   https://bugzilla.gnome.org/show_bug.cgi?id=788564

** Changed in: gnome-shell
   Importance: Medium => Unknown

** Changed in: gnome-shell
   Status: Fix Released => Unknown

** Changed in: gnome-shell
 Remote watch: GNOME Bug Tracker #788564 => bugzilla.gnome.org/ #788564

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  17.10 sticky keys doesn t work

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  hi

  I upgraded my system to 17.10 but now sticky keys doesn t work altough
  I reopen it in typing asist.

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1727716/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscre

[Daniel van Vugt]

https://salsa.debian.org/gnome-team/gnome-shell/-/commit/6e18ad3e36

https://launchpadlibrarian.net/562041828/gnome-
shell_40.5-1ubuntu2_source.changes

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension()
  from InitDisplayInfoEntry() from __glXLookupDisplay() from
  CommonMakeCurrent() from cogl_onscreen_glx_dispose() from
  g_object_unref() from clutter_stage_view_finalize()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1942031/+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 1936826] Re: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199]

[Daniel van Vugt]

https://salsa.debian.org/gnome-team/gnome-shell/-/commit/6e18ad3e36

https://launchpadlibrarian.net/562041828/gnome-
shell_40.5-1ubuntu2_source.changes

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  [st-focus-manager.c:199]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae

  ---

  Testing daily Ubuntu Impish ISO 2021-07-19

  Test machine : Dell [Latitude] 7280 (i5-7300U,

  Received the error message - Ubuntu has experienced an internal error
  ...do you want to send ...etc, etc.

  This bug occurred when I was scrolling up and down on the "Settings"
  app and selected "Appearance".

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 19 12:15:54 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2021-07-19 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  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/gnome-shell/+bug/1936826/+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 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  Desktop icons vanishing when in Activities Overview is jarring and
  looks ugly

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Desktop icons vanishing and reappearing when in Activities Overview is
  jarring and looks ugly.

  Suggestions:

* Don't hide them in AO, because they will be well shaded anyway; or

* Fade them out and in smoothly.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-desktop-icons 19.01.4-1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 11 14:24:42 2019
  InstallationDate: Installed on 2019-05-02 (162 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847712/+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 1942121] Re: gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from st_focus_manager_remove_group()

[Daniel van Vugt]

https://salsa.debian.org/gnome-team/gnome-shell/-/commit/6e18ad3e36

https://launchpadlibrarian.net/562041828/gnome-
shell_40.5-1ubuntu2_source.changes

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from
  g_hash_table_lookup() from st_focus_manager_remove_group()

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  This error occurred when I started the system.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 30 15:48:50 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-08-19 (10 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210819)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_hash_table_lookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  separator:

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