[Desktop-packages] [Bug 1995050] [NEW] The nautilus window remains dirty when resized in wayland session

[Decio Della Fortuna]

Public bug reported:

The nautilus window remains dirty when resized in wayland session.
In particular, after having enlarged or reduced it, the corners remain dirty.
The enlargement and reduction operations are jerky.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 28 08:36:19 2022
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
 b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1412, 885)'
InstallationDate: Installed on 2022-10-21 (7 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

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


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

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

Title:
  The nautilus window remains dirty when resized in wayland session

Status in nautilus package in Ubuntu:
  New

Bug description:
  The nautilus window remains dirty when resized in wayland session.
  In particular, after having enlarged or reduced it, the corners remain dirty.
  The enlargement and reduction operations are jerky.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 28 08:36:19 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1412, 885)'
  InstallationDate: Installed on 2022-10-21 (7 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995050/+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 1993992] Re: kinetic.xml has wrong filename for a wallpaper

[Tanupy ume]

Bug #1994949 said no only kinetic.xml but also kinetic-wallpapers.xml
if you catch one bug you must serch others

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

Title:
  kinetic.xml has wrong filename for a wallpaper

Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  In the kinetic wallpaper package, the kinetic.xml file that handles
  the rotating background has the wrong filename for
  "/usr/share/backgrounds/Twisted_Gradients_by_Gustavo_Brenner.png". It
  uses ".jpg" instead of the correct ".png" extension.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1993992/+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 1882884] Re: Fingerprint Authentication: Support multi user-login scenario

[prafulla chandra kota]

22.04: FP identify is working fine now from login screen by selecting
respective user and swipe the finger.

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

Title:
  Fingerprint Authentication: Support multi user-login scenario

Status in fprintd package in Ubuntu:
  In Progress
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  FP authentication doesn't work from the login screen when there is another 
user.
  You have to login into any user with a password for first time, then we can 
use FP authentication for our next login attempts.

  Ubuntu version : 20.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1882884/+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 1882878] Re: The user panel let you enroll the same finger several times

[prafulla chandra kota]

Duplicate FP enrollment support is added in latest release 22.04, it is
working fine now, defect can be closed.

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

Title:
  The user panel let you enroll the same finger several times

Status in gnome-control-center:
  Unknown
Status in fprintd package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  We are able to enroll the same finger for all 10 available options.
  (No error like 'Fingerprint is already enrolled' is observed). In
  windows it doesn’t allow to enroll the same finger, it has a duplicate
  check API. Here we have all 10 finger options are shown in GUI itself,
  so whichever finger is enrolled atleast the same finger can be grayed
  out so that user cannot enroll the same finger again.

  The release of Ubuntu: Ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1882878/+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 1882884] Re: Fingerprint Authentication: Support multi user-login scenario

[prafulla chandra kota]

Multi user FP identification is working fine now, defect can be closed.

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

Title:
  Fingerprint Authentication: Support multi user-login scenario

Status in fprintd package in Ubuntu:
  In Progress
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  FP authentication doesn't work from the login screen when there is another 
user.
  You have to login into any user with a password for first time, then we can 
use FP authentication for our next login attempts.

  Ubuntu version : 20.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1882884/+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 1877038] Re: [upstream] Firefox lacks FIDO2 support with Yubikeys

[Bug Watch Updater]

** Bug watch added: github.com/flatpak/flatpak/issues #2764
   https://github.com/flatpak/flatpak/issues/2764

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

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

[Dkeeler]

HI Alfie - bugzilla isn't a discussion forum. You'll probably have more
luck here: https://discourse.mozilla.org/

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

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

[Alfie-fresta]

I'm interested in hearing people's thoughts on adopting FIDO2 platform
APIs on Linux, akin to Windows Hello, or Android's Fido2ApiClient --
which Firefox already delegates to on those platforms.

I've written a FIDO2 (WebAuthn) and FIDO U2F platform library in Rust
[1], for Linux. It's a WiP, but it already supports the main FIDO2
ceremonies, both FIDO2 PIN protocols, and downgrading WebAuthn for U2F
devices (as per specs). I've tested this with as many security keys I
could get my hands on so far [2]. It's designed to have pluggable
transports, currently supporting HID and BLE (via Bluez), and plans for
NFC and caBLE.

As mentioned before, whilst it could be used directly as a library, the
main objective is to provide a backend for new D-Bus platform APIs.
Secondary goals include supporting TPM platform authenticators, and
supporting containerised applications (e.g. Flatpaks[3]), without
requiring access to the USB stack, or BLE adapters.

I'm trying to gauge interest in Firefox delegating U2F and FIDO2 to the
platform. If this sounds feasible, as the next step I will try and reach
out to GNOME shell folks. I reached out earlier to some System76
engineers working on the Cosmic DE, as they may also be interested.


[1] https://github.com/AlfioEmanueleFresta/xdg-credentials-portal
[2] 
https://github.com/AlfioEmanueleFresta/xdg-credentials-portal/wiki/Verified-hardware
[3] https://github.com/flatpak/flatpak/issues/2764

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1877038/+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 1995030] [NEW] Page size setting is just plain wrong

[MR Zenwiz]

Public bug reported:

I have an HP OfficeJet 4654 connected to my Xubuntu 22.04 LTS Jammy
Jellyfish desktop via USB cable. I am running the latest HP-LIP drivers,
and the scanner works relatively well.

However, when I set the page size preference to Automatic (the default),
a letter sized scan on the platen comes out fine. When I set the page
size preference to Letter, the scan comes out legal sized - totally
wrong.

Also, when I use the page size preference of Automatic (the default), a
scan of a letter-sized sheet using the feeder comes out legal sized.
However, if I scan the same sheet with the page size preference set to
Letter, it comes out fine.

This means I have to remember or check what my last page size preference
is set to to scan the right sized output depending on whether the scan
is on the platen or through the feeder.

This is so unbelievably bad user-friendliness I can't even describe it
further.

1) marbase 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 
GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

2) simple-scan 42.0

3) When the page size preference is set to Automatic, I expect it to
produce a scan of a size that automatically matches the actual size of
the page scanned whether I use the platen or the sheet feeder. When I
set the preference to Letter, I expect the scan to be letter-sized
whether I use the platen or the sheet feeder.

4) See above and the attached files showing textually and graphically
what happened.

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Zip file containing debug logs, sample scans, screenshot, 
all showing the bugs"
   
https://bugs.launchpad.net/bugs/1995030/+attachment/5627327/+files/SimpleScanBugFiles%2Czip

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

Title:
  Page size setting is just plain wrong

Status in simple-scan package in Ubuntu:
  New

Bug description:
  I have an HP OfficeJet 4654 connected to my Xubuntu 22.04 LTS Jammy
  Jellyfish desktop via USB cable. I am running the latest HP-LIP
  drivers, and the scanner works relatively well.

  However, when I set the page size preference to Automatic (the
  default), a letter sized scan on the platen comes out fine. When I set
  the page size preference to Letter, the scan comes out legal sized -
  totally wrong.

  Also, when I use the page size preference of Automatic (the default),
  a scan of a letter-sized sheet using the feeder comes out legal sized.
  However, if I scan the same sheet with the page size preference set to
  Letter, it comes out fine.

  This means I have to remember or check what my last page size
  preference is set to to scan the right sized output depending on
  whether the scan is on the platen or through the feeder.

  This is so unbelievably bad user-friendliness I can't even describe it
  further.

  1) marbase 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 
x86_64 GNU/Linux
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

  2) simple-scan 42.0

  3) When the page size preference is set to Automatic, I expect it to
  produce a scan of a size that automatically matches the actual size of
  the page scanned whether I use the platen or the sheet feeder. When I
  set the preference to Letter, I expect the scan to be letter-sized
  whether I use the platen or the sheet feeder.

  4) See above and the attached files showing textually and graphically
  what happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1995030/+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 1995015] Re: Logitech Brio LED doesn't light up with 22.10

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

Title:
  Logitech Brio LED doesn't light up with 22.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The LED light on my Logitech Brio webcam no longer lights up when the
  camera is active.

  When I exit an app that uses camera, the LED will illuminate for about
  a half second before turning off again.

  This behavior began after upgrading from Ubuntu 22.04 to 22.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brett  2437 F wireplumber
   /dev/snd/pcmC0D0c:   brett  2434 F...m pipewire
   /dev/snd/controlC1:  brett  2437 F wireplumber
   /dev/snd/seq:brett  2434 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 27 12:42:56 2022
  InstallationDate: Installed on 2021-12-16 (314 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-10-22 (5 days ago)
  dmi.bios.date: 09/13/2022
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0Y4GNJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd09/13/2022:br1.15:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA02:cvnDellInc.:ct10:cvr:sku096D:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1995015/+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 1977499] Re: BUG IN UBUNTU 22.10 KINETIC KUDU: Audio Does Not Work Properly And Video Playback Is Very Laggy

[Launchpad Bug Tracker]

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

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

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

Title:
  BUG IN UBUNTU 22.10 KINETIC KUDU: Audio Does Not Work Properly And
  Video Playback Is Very Laggy

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had recently upgraded from Ubuntu 22.04 LTS Jammy Jellyfish To Ubuntu 22.10 
Kinetic Kudu (Development Branch) and i found 2 NEW Problems with it...
  1) Audio does not work at all
  2) Video playback is very laggy and not as smooth as before
  When i played a video,The playback was so laggy making me want to smash the 
screen and there was no audio at all like seriously,I am seeing this problem 
ever since I've upgraded to Ubuntu 22.10 Kinetic Kudu (Development 
Branch),Please Ubuntu Team fix this problem!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rasth   F pipewire-media-
   /dev/snd/seq:rasth  1110 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  3 05:52:08 2022
  InstallationDate: Installed on 2022-06-03 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220602)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1977499/+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 1995015] [NEW] Logitech Brio LED doesn't light up with 22.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The LED light on my Logitech Brio webcam no longer lights up when the
camera is active.

When I exit an app that uses camera, the LED will illuminate for about a
half second before turning off again.

This behavior began after upgrading from Ubuntu 22.04 to 22.10.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  brett  2437 F wireplumber
 /dev/snd/pcmC0D0c:   brett  2434 F...m pipewire
 /dev/snd/controlC1:  brett  2437 F wireplumber
 /dev/snd/seq:brett  2434 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 27 12:42:56 2022
InstallationDate: Installed on 2021-12-16 (314 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to kinetic on 2022-10-22 (5 days ago)
dmi.bios.date: 09/13/2022
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 0Y4GNJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd09/13/2022:br1.15:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA02:cvnDellInc.:ct10:cvr:sku096D:
dmi.product.family: XPS
dmi.product.name: XPS 13 9300
dmi.product.sku: 096D
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug kinetic wayland-session
-- 
Logitech Brio LED doesn't light up with 22.10
https://bugs.launchpad.net/bugs/1995015
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 1994993] Re: GDM won't start after update, systemctl start gdm just hangs indefinitely, using nvidia-drivers-520

[Paul White]

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

** Tags added: jammy

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

Title:
  GDM won't start after update, systemctl start gdm just hangs
  indefinitely, using nvidia-drivers-520

Status in gdm3 package in Ubuntu:
  New

Bug description:
  After an update on 2022-10-27 after 12 days of uptime, GDM stopped
  working. The gdm3 package is at 42.0-1ubuntu7, though downgrading to
  42.0-1ubuntu6 didn't help.

  Running systemctl start gdm in the terminal would just hang until I
  hit ctrl+c.

  LightDM works (though I'd strongly prefer using GDM)

  Running on Nvidia Titan RTX, nvidia-
  driver-520=520.56.06-0ubuntu0.22.04.1

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ uname -a
  Linux thor 5.15.0-52-lowlatency #58-Ubuntu SMP PREEMPT Thu Oct 13 12:37:18 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1994993/+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 1994993] [NEW] GDM won't start after update, systemctl start gdm just hangs indefinitely, using nvidia-drivers-520

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After an update on 2022-10-27 after 12 days of uptime, GDM stopped
working. The gdm3 package is at 42.0-1ubuntu7, though downgrading to
42.0-1ubuntu6 didn't help.

Running systemctl start gdm in the terminal would just hang until I hit
ctrl+c.

LightDM works (though I'd strongly prefer using GDM)

Running on Nvidia Titan RTX, nvidia-
driver-520=520.56.06-0ubuntu0.22.04.1

$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

$ uname -a
Linux thor 5.15.0-52-lowlatency #58-Ubuntu SMP PREEMPT Thu Oct 13 12:37:18 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

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

-- 
GDM won't start after update, systemctl start gdm just hangs indefinitely, 
using nvidia-drivers-520
https://bugs.launchpad.net/bugs/1994993
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gdm3 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 1884299] Re: Snaps don't run with NFS home on AutoFS

[Santiago Castro]

** Summary changed:

- Chromium snap won't run with nfs home drive
+ Snaps don't run with NFS home on AutoFS

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

Title:
  Snaps don't run with NFS home on AutoFS

Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  My physical computer lab uses AutoFS home drives (per
  https://help.ubuntu.com/community/Autofs#Wildcard_characters).   If
  any user tries to run chromium browser, it fails.

  I assume it is related to these:
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
  But that says a fix was released, but seems toi only work for NFS home drives
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873
  That ones is reported as a dupe but it's not, AutoFS home drives still don't 
work.

  $ chromium -v
  cannot create user data directory: /home/test.student2/snap/chromium/1193: 
Stale file handle

  $ tail -f /var/log/syslog
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 
audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 
audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS

  $ apt policy chromium-browser
  chromium-browser:
    Installed: 81.0.4044.129-0ubuntu0.20.04.1
    Candidate: 81.0.4044.129-0ubuntu0.20.04.1
    Version table:
   *** 81.0.4044.129-0ubuntu0.20.04.1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Athos Ribeiro]

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

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

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

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1995000] [NEW] gnome-shell is logging excessively to rsyslogd

[Hagan Franks]

Public bug reported:

I think this is related/already known:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868

Seeing the same logs posted by Kirill:

Nov 26 04:07:11 ulegion gnome-shell[3001]: The offending callback was 
SourceFunc().
Nov 26 04:07:11 ulegion gnome-shell[3001]: == Stack trace for context 
0x561e0c0b71c0 ==
Nov 26 04:07:11 ulegion gnome-shell[3001]: Attempting to run a JS callback 
during garbage collection. This is most likely caused by destroying a Clutter 
actor or GTK widget with ::destroy si

I was low on disk space, making this problem worse. However I've seen
this happen before with plenty of disk space just not to the degree I
couldn't use gnome (100%+ CPU). I'm currently using ubuntu 22.04.01 LTS.
But this is an upgrade from 18.04 LTS so perhaps a config/plugin carrier
over I need to remove. Don't need this solved but reporting in case it
helps narrow  the issue.

Release: 22.04.01 LTS
Package ver: 42.4-0ubuntu0.22.04.1
Expectation: CPU usage < 10%, not log errors excessively to rsyslogd
Issue: excessive logging (like 10-100 lines/sec) when an app or plugin crashed?

Thanks!

-Hagan

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Oct 27 09:57:05 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-07 (1238 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-07-13 (105 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  gnome-shell is logging excessively to rsyslogd

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I think this is related/already known:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868

  Seeing the same logs posted by Kirill:

  Nov 26 04:07:11 ulegion gnome-shell[3001]: The offending callback was 
SourceFunc().
  Nov 26 04:07:11 ulegion gnome-shell[3001]: == Stack trace for context 
0x561e0c0b71c0 ==
  Nov 26 04:07:11 ulegion gnome-shell[3001]: Attempting to run a JS callback 
during garbage collection. This is most likely caused by destroying a Clutter 
actor or GTK widget with ::destroy si

  I was low on disk space, making this problem worse. However I've seen
  this happen before with plenty of disk space just not to the degree I
  couldn't use gnome (100%+ CPU). I'm currently using ubuntu 22.04.01
  LTS. But this is an upgrade from 18.04 LTS so perhaps a config/plugin
  carrier over I need to remove. Don't need this solved but reporting in
  case it helps narrow  the issue.

  Release: 22.04.01 LTS
  Package ver: 42.4-0ubuntu0.22.04.1
  Expectation: CPU usage < 10%, not log errors excessively to rsyslogd
  Issue: excessive logging (like 10-100 lines/sec) when an app or plugin 
crashed?

  Thanks!

  -Hagan

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 27 09:57:05 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-07 (1238 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-07-13 (105 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995000/+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 1994435] Re: Proprietary NVIDIA drivers stopped working as of 10/24/22 update

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  Proprietary NVIDIA drivers stopped working as of 10/24/22 update

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

Bug description:
  Ubuntu Release: 22.04.1.LTS

  Problem:

  On 10/24/22, I installed the latest Ubuntu 22.04.1 LTS updates. I
  don't know what was updated, but many of the packages had "oem" or
  "oracle" in their names, which I don't remember seeing before. Before
  updating, I had a NVIDIA driver from the "Software &
  Updates/Additional Drivers" list installed and I was using X11. I
  don't remember the driver version number, but it was the highest.
  After updating, Settings/About/Graphics changed from a GeForce RTX
  2080 Ti to "llvmpipe (LLVM 13.0.1, 256 bits)". Windowing system was
  still X11. My three-monitor setup reverted to one monitor, and the
  display was of low resolution. I tried proprietary NVIDIA drivers 515,
  510, and 470, but none restored the system to three monitors and high
  resolution. However, the Nouveau driver did restore the system.
  Settings/About/Graphics changed to NV162.

  Work-Around:

  I am now using the driver installed via "sudo sh NVIDIA-
  Linux-x86_64-515.76.run", from NVIDIA's website.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1994435/+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 1993992] Re: kinetic.xml has wrong filename for a wallpaper

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Confirmed

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

Title:
  kinetic.xml has wrong filename for a wallpaper

Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  In the kinetic wallpaper package, the kinetic.xml file that handles
  the rotating background has the wrong filename for
  "/usr/share/backgrounds/Twisted_Gradients_by_Gustavo_Brenner.png". It
  uses ".jpg" instead of the correct ".png" extension.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1993992/+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 1993992] Re: kinetic.xml has wrong filename for a wallpaper

[Hans Joachim Desserud]

** Tags added: kinetic

** Tags added: bitesize string-fix

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

Title:
  kinetic.xml has wrong filename for a wallpaper

Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  In the kinetic wallpaper package, the kinetic.xml file that handles
  the rotating background has the wrong filename for
  "/usr/share/backgrounds/Twisted_Gradients_by_Gustavo_Brenner.png". It
  uses ".jpg" instead of the correct ".png" extension.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1993992/+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 1994949] Re: ubuntu-wallpapers package kinetic 22.10

[Hans Joachim Desserud]

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

** This bug has been marked a duplicate of bug 1993992
   kinetic.xml has wrong filename for a wallpaper

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

Title:
  ubuntu-wallpapers package kinetic 22.10

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  kinetic-wallpapers.xml
  kinetic.xml

  wrong)Twisted_Gradients_by_Gustavo_Brenner.jpg
  right)Twisted_Gradients_by_Gustavo_Brenner.png
  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1994949/+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 1993907] Re: nautilus freezes randomly

[Mariano Draghi]

Unfortunately, after several hours/days, the issue reappears. It's as if
when Tracker3 is doing some more heavy reindexing in the background,
when the laptop is not in use, it hangs.

In my case the issue is definetely with Tracker3; Nautilus hanging is a
side effect of not being able to communicate with Tracker (although it
should handle it more gracefully, for sure!).

When tracker3 hangs, checking its status with

  tracker3 daemon

gives a timeout error after several seconds.

Whenever I face the issue, I'm doing a

  tracker3 daemon -k

to kill the daemon, followed by a

  tracker3 daemon -s

to start it again.

That works, without having to reset the index completely... until
tracker3 hangs again.

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

Title:
  nautilus freezes randomly

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  nautilus becomes unresponsive and "files" is not responding sign
  appears at random

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 15:39:58 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-05-13 (161 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993907/+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 185928] Re: Pressing Space key should toggle play/pause (pause when playing; play when paused)

[Roger Peppe]

I can't believe this hasn't been fixed yet.

Other music player apps (e.g. Spotify) use space for pause without
apparent issue. The space bar is the largest affordance on a keyboard
and play/pause is the most common action in a music player (and often
the one with most urgency attached), so it makes sense to use it in this
way. As things are currently (v3.4.4, October 2022), I can't even use
tab to select the play/pause button, so the argument about accessibility
appears spurious in practice.

At the very least, there could be a preferences option to enable
play/pause on space.

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

Title:
  Pressing Space key should toggle play/pause (pause when playing; play
  when paused)

Status in One Hundred Papercuts:
  Invalid
Status in Rhythmbox:
  Invalid
Status in Totem:
  Invalid
Status in rhythmbox package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: rhythmbox

  1. Linux tavla 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 
GNU/Linux
   DISTRIB_ID=Ubuntu 
   DISTRIB_RELEASE=7.10
   DISTRIB_CODENAME=gutsy
   DISTRIB_DESCRIPTION="Ubuntu 7.10"

  2. rhythmbox 0.11.2-0ubuntu4

  3.
  Pressing Space, Rhythmbox starts playing the current track from the 
beginning. That is, it restarts playing the track.
  By normal convension Space should act as a play/pause button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/185928/+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 1993867] Re: Telegram sometimes start endless use 100% CPU

[vodopad27]

Fixed after upgrading to new version. I added this repo:
https://launchpad.net/~atareao/+archive/ubuntu/telegram


4.1.1 buggy and unusable for me.

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

Title:
  Telegram sometimes start endless use 100% CPU

Status in libvpx package in Ubuntu:
  New
Status in telegram-desktop package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04 all was fine.

  After upgrade to Ubuntu 22.10 Telegram was also updated. And
  sometimes, randomly, TG starts to use 100% CPU.

  Nothing on logs. But in starce i see a lot of these messages:
  [pid 33581] poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, 
events=POLLIN}, {fd=14, events=POLLIN}, {fd=19, events=POLLIN}, {fd=51, 
events=POLLIN}], 6, 8) = 0 (Timeout)

  
  PSA. Thousand messages.

  In normal state, when TG use 0-2% CPU, i see same messages. So, not
  related with bug.

  Please, ask me additional information, i can provide any logs.

  Today this bug occurs two times.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: telegram-desktop 4.1.1+ds-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 01:53:36 2022
  InstallationDate: Installed on 2018-05-02 (1633 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: telegram-desktop
  UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1993867/+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 1993867] Re: Telegram sometimes start endless use 100% CPU

[vodopad27]

Another steps to reproduce:
1) Download archive
2) Unpack
3) Send gif to user\group


** Attachment added: "tild3265-6134-4566-b564-383630646239__photo.zip"
   
https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1993867/+attachment/5627283/+files/tild3265-6134-4566-b564-383630646239__photo.zip

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

Title:
  Telegram sometimes start endless use 100% CPU

Status in libvpx package in Ubuntu:
  New
Status in telegram-desktop package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04 all was fine.

  After upgrade to Ubuntu 22.10 Telegram was also updated. And
  sometimes, randomly, TG starts to use 100% CPU.

  Nothing on logs. But in starce i see a lot of these messages:
  [pid 33581] poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, 
events=POLLIN}, {fd=14, events=POLLIN}, {fd=19, events=POLLIN}, {fd=51, 
events=POLLIN}], 6, 8) = 0 (Timeout)

  
  PSA. Thousand messages.

  In normal state, when TG use 0-2% CPU, i see same messages. So, not
  related with bug.

  Please, ask me additional information, i can provide any logs.

  Today this bug occurs two times.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: telegram-desktop 4.1.1+ds-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 01:53:36 2022
  InstallationDate: Installed on 2018-05-02 (1633 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: telegram-desktop
  UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1993867/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Vladimir]

What the fuck? Can't resolve problem from 2013? Have a fresh install
ubuntu 22.04 and cant setup ctrl-alt-etc keyboard layout switch? Need to
use tweaks, google, etc Ubuntu user friendly?

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in GNOME Settings Daemon:
  Unknown
Status in System76:
  New
Status in Ubuntu Flashback:
  New
Status in Ubuntu GNOME:
  Fix Released
Status in Ubuntu GNOME Flashback:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-control-center package in ALT Linux:
  Unknown
Status in gnome-control-center package in Baltix:
  Confirmed
Status in gnome-control-center package in Gentoo Linux:
  Unknown
Status in gnome-control-center package in Mandriva:
  Unknown

Bug description:
  [Impact]

  Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift,
  etc. Shift, Caps Lock keys are just ignored in settings.

  [Test Case]

  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a combination of two modifier keys such as Ctrl+Shift
  -> the UI should reflect the new keys

  - add at least two input sources through gnome-control-center's text entry
    settings
  - press and release Ctrl+Shift
  -> the current input source should change

  [Regression Potential]

  That UI was not working before, it should only be an improvement (some
  key combos are not working as expected, that's another issue and
  shouldn't be mixed with this one)

  The input switching shortcut might capture other non-modifier
  shortcuts, but users will need to consider this when choosing their
  switching shortcut anyways. For users this bug affects, this
  represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  You can use the tag keyboard-layout-switching-hotkeys to find related bugs.
  
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys

  For using layout switching hotkeys in Unity Greeter, see bug 1245137.
  For using layout switching hotkeys in GNOME lockscreen, see bug 1244548.
  For using layout switching hotkeys in GNOME FlashBack sessions, see bug 
1687466 (at least ).

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+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 1969891] Re: Firefox snap can't be added to Dock favorites

[Robert]

Hey all,

I have the same issue.

My favourites setting lists the following:

:~$ gsettings get org.gnome.shell favorite-apps
['org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'virt-manager.desktop', 'libreoffice-calc.desktop', 
'signal-desktop_signal-desktop.desktop', 'firefox_firefox.desktop', 
'vivaldi-stable.desktop']


Please let me know if you require any further information as this is 
surprisingly annoying!

Thanks!

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

Title:
  Firefox snap can't be added to Dock favorites

Status in firefox package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  After upgrading from 21.10 to 22.04 the old Firefox was removed from
  my Dock favorites. I readded Firefox to my favorites which adds the
  Firefox icon to the favorites as expected.

  However, clicking on it will open the Firefox snap on the bottom of
  the Dock. So now I have 2 Firefox symbols in my Dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.17.0-4.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 08:49:32 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-05-31 (325 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969891/+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 1993125] Re: /usr/bin/gjs-console:6:g_assertion_message:g_assertion_message_expr:gsk_renderer_dispose:g_object_unref:g_object_unref

[Brian Murray]

This is the top crasher for Kinetic.

** Tags added: rls-kk-incoming

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

Title:
  /usr/bin/gjs-
  
console:6:g_assertion_message:g_assertion_message_expr:gsk_renderer_dispose:g_object_unref:g_object_unref

Status in GNOME Characters:
  New
Status in gjs package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gjs.  This problem was most recently seen with package version 1.74.0-1, the 
problem page at 
https://errors.ubuntu.com/problem/770ae17730a5918adba8afcbe5b510c35baffb39 
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/gnome-characters/+bug/1993125/+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 1992279] Re: package libreoffice-ogltrans 1:7.3.6-0ubuntu0.22.04.1 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libreoffice-ogltrans 1:7.3.6-0ubuntu0.22.04.1 failed to
  install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor

Status in libreoffice package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-ogltrans 1:7.3.6-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct  8 19:19:11 2022
  ErrorMessage: bağımlılık sorunları - yapılandırılmadan bırakılıyor
  InstallationDate: Installed on 2022-10-08 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: libreoffice
  Title: package libreoffice-ogltrans 1:7.3.6-0ubuntu0.22.04.1 failed to 
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1992279/+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 1994067] Re: "Windows 11 Pro" and "Ubuntu 22.04.1 LTS" are installed and up to date on the laptop. There is no hardware problem with the laptop. No sound from operating system

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  "Windows 11 Pro" and "Ubuntu 22.04.1 LTS" are installed and up to date
  on the laptop. There is no hardware problem with the laptop. No sound
  from operating system "Ubuntu 22.04.1 LTS". But the sound comes from
  the operating system "Windows 11 Pro" without any problems.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  "Windows 11 Pro" and "Ubuntu 22.04.1 LTS" are installed and up to date
  on the laptop. There is no hardware problem with the laptop. No sound
  from operating system "Ubuntu 22.04.1 LTS". But the sound comes from
  the operating system "Windows 11 Pro" without any problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  muhammed   1749 F pulseaudio
   /dev/snd/controlC1:  muhammed   1749 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 22:46:37 2022
  InstallationDate: Installed on 2022-10-19 (5 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2021
  dmi.bios.release: 87.176
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: TN1V7.10_Monster
  dmi.board.asset.tag: Board Asset Tag
  dmi.board.name: Huma H5 V3.2
  dmi.board.vendor: Monster
  dmi.board.version: V20
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Monster
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 6.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrTN1V7.10_Monster:bd12/28/2021:br87.176:efr6.6:svnMONSTER:pnHumaH5V3.2:pvrV10:rvnMonster:rnHumaH5V3.2:rvrV20:cvnMonster:ct10:cvrChassisVersion:skuH5V32TN1156MSCD:
  dmi.product.family: HUMA
  dmi.product.name: Huma H5 V3.2
  dmi.product.sku: H5V32TN1156MSCD
  dmi.product.version: V10
  dmi.sys.vendor: MONSTER
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2022-10-24T22:36:17.567999

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1994067/+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 1993892] Re: Window area is unusable

[Delany]

Disabling extensions resolved the issue.
I assume it was https://extensions.gnome.org/extension/5177/vertical-workspaces/

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

Title:
  Window area is unusable

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The window area becomes unusable without warning and the same visual
  artefacts are seen (see attached). The system taskbar is still
  responsive, so I can logout/login, which resolves the issues
  temporarily.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 16:10:38 2022
  DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081]
  InstallationDate: Installed on 2022-10-14 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Intel(R) Client Systems NUC10i5FNH
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)
  dmi.bios.date: 04/09/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0052.2021.0409.1144
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i5FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M38063-307
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.9
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN:
  dmi.product.family: FN
  dmi.product.name: NUC10i5FNH
  dmi.product.sku: BXNUC10i5FNHN
  dmi.product.version: M38014-308
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993892/+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 1994960] [NEW] FP identify fails when continuous lock and unlock is perfomed on DELL laptop

[prafulla chandra kota]

Public bug reported:

FP identify fails when continuous lock and unlock is perfomed on DELL
laptop

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: fprintd 1.94.2-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.0.0-9005.5+exp.12-oem 6.0.0
Uname: Linux 6.0.0-9005-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 27 16:03:09 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X46
InstallationDate: Installed on 2022-10-27 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
SourcePackage: fprintd
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  FP identify fails when continuous lock and unlock is perfomed on DELL
  laptop

Status in fprintd package in Ubuntu:
  New

Bug description:
  FP identify fails when continuous lock and unlock is perfomed on DELL
  laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.2-1ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-9005.5+exp.12-oem 6.0.0
  Uname: Linux 6.0.0-9005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 27 16:03:09 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X46
  InstallationDate: Installed on 2022-10-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  SourcePackage: fprintd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1994960/+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 1994962] [NEW] FP identify is failed when Suspend is invoked after doing WIN+L operation

[prafulla chandra kota]

Public bug reported:

FP identify is failed when Suspend is invoked after doing WIN+L
operation

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: fprintd 1.94.2-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.0.0-9005.5+exp.12-oem 6.0.0
Uname: Linux 6.0.0-9005-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 27 16:07:38 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X46
InstallationDate: Installed on 2022-10-27 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
SourcePackage: fprintd
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  FP identify is failed when Suspend is invoked after doing WIN+L
  operation

Status in fprintd package in Ubuntu:
  New

Bug description:
  FP identify is failed when Suspend is invoked after doing WIN+L
  operation

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.2-1ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-9005.5+exp.12-oem 6.0.0
  Uname: Linux 6.0.0-9005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 27 16:07:38 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X46
  InstallationDate: Installed on 2022-10-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  SourcePackage: fprintd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1994962/+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 1994959] [NEW] "Switch input sources individually for each window" does not remember the input source

[DEXTER]

Public bug reported:

When using:
Settings->keyboard->Input Source Switching->Switch input sources individually 
for each window

and set an input source for a window, then if I close the window and
reopen it, it does not remember what input source was set to it, I have
to set it every time.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 27 11:41:16 2022
InstallationDate: Installed on 2022-10-14 (12 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1994959/+attachment/5627260/+files/ProcEnviron.txt

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

Title:
  "Switch input sources individually for each window" does not remember
  the input source

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

Bug description:
  When using:
  Settings->keyboard->Input Source Switching->Switch input sources individually 
for each window

  and set an input source for a window, then if I close the window and
  reopen it, it does not remember what input source was set to it, I
  have to set it every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 27 11:41:16 2022
  InstallationDate: Installed on 2022-10-14 (12 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.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/1994959/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

[Sergiu]

After closed this app https://github.com/ThePBone/GalaxyBudsClient , it
took about 2 days to increase memory usage to 400MB

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

Title:
  gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Incomplete

Bug description:
  over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled 
extensions:
  gnome-extensions list --enabled
  ubuntu-appindicat...@ubuntu.com
  ubuntu-d...@ubuntu.com

  other info: 
  lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 22:35:24 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-07-03 (93 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1991709/+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 1994697] Re: 1440x900 (3:2) resolution mismatch

[Xargon]

** Summary changed:

- 1400x900 (3:2) resolution mismatch
+ 1440x900 (3:2) resolution mismatch

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

Title:
  1440x900 (3:2) resolution mismatch

Status in xorg package in Ubuntu:
  New

Bug description:
  The listed resolution 1440x900 (3:2) it's not correct: my monitor is 16:10 
and I can see black bars.
  I suppose the real resolution is 1440x960 (3:2), but the actual 1440x900 
(16:10) is missing.

  I updated some packages today and the issue came after reboot:

  2022-10-26 16:48:06 upgrade google-chrome-stable:amd64 106.0.5249.119-1 
107.0.5304.68-1
  2022-10-26 16:48:14 upgrade tzdata:all 2022c-0ubuntu0.22.04.0 
2022e-0ubuntu0.22.04.0
  2022-10-26 16:48:14 upgrade alsa-ucm-conf:all 1.2.6.3-1ubuntu1 
1.2.6.3-1ubuntu1.1
  2022-10-26 16:48:14 upgrade docker-ce-cli:amd64 5:20.10.20~3-0~ubuntu-jammy 
5:20.10.21~3-0~ubuntu-jammy
  2022-10-26 16:48:18 upgrade docker-ce:amd64 5:20.10.20~3-0~ubuntu-jammy 
5:20.10.21~3-0~ubuntu-jammy
  2022-10-26 16:48:20 upgrade docker-ce-rootless-extras:amd64 
5:20.10.20~3-0~ubuntu-jammy 5:20.10.21~3-0~ubuntu-jammy
  2022-10-26 16:48:20 upgrade docker-compose-plugin:amd64 2.12.0~ubuntu-jammy 
2.12.2~ubuntu-jammy
  2022-10-26 16:48:21 upgrade docker-scan-plugin:amd64 0.17.0~ubuntu-jammy 
0.21.0~ubuntu-jammy
  2022-10-26 16:48:22 upgrade fwupd:amd64 1.7.5-3 1.7.9-1~22.04.1
  2022-10-26 16:48:22 upgrade libfwupdplugin5:amd64 1.7.5-3 1.7.9-1~22.04.1
  2022-10-26 16:48:22 upgrade libfwupd2:amd64 1.7.5-3 1.7.9-1~22.04.1
  2022-10-26 16:48:22 upgrade gdb:amd64 12.0.90-0ubuntu1 12.1-0ubuntu1~22.04
  2022-10-26 16:48:22 upgrade grub-efi-amd64:amd64 2.06-2ubuntu7 2.06-2ubuntu10
  2022-10-26 16:48:22 upgrade grub-efi-amd64-signed:amd64 1.180+2.06-2ubuntu7 
1.182~22.04.1+2.06-2ubuntu10
  2022-10-26 16:48:22 upgrade grub-efi-amd64-bin:amd64 2.06-2ubuntu7 
2.06-2ubuntu10
  2022-10-26 16:48:22 upgrade linux-firmware:all 
20220329.git681281e4-0ubuntu3.5 20220329.git681281e4-0ubuntu3.6
  2022-10-26 16:48:26 upgrade qemu-system-gui:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-block-extra:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-system-x86:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-system-common:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-utils:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-system-data:all 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:27 upgrade snapd:amd64 2.57.4+22.04 2.57.5+22.04
  2022-10-26 16:48:27 upgrade teamviewer:amd64 15.34.4 15.35.5
  2022-10-26 16:48:34 upgrade xserver-common:all 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:34 upgrade xserver-xephyr:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:35 upgrade xserver-xorg-legacy:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:35 upgrade xserver-xorg-core:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:35 upgrade sssd:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade python3-sss:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-proxy:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-krb5:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-ad:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-ldap:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-ipa:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-krb5-common:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-ad-common:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-common:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade libnss-sss:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libpam-sss:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libsss-certmap0:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libsss-nss-idmap0:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libsss-idmap0:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libipa-hbac0:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade ovmf:all 2022.02-3 2022.02-3ubuntu0.22.04.1

  I suppose this bug is here:

  2022-10-26 16:48:34 upgrade xserver-common:all 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:34 upgrade xserver-xephyr:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:35 upgrade xserver-xorg-legacy:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:35 upgrade xserver-xorg-core:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2

  lsb_release -rd

[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action

[Julian Alarcon]

I still have the same issue installing Youtube Music Web app
(https://music.youtube.com/) in Ubuntu 22.04.

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

Title:
  [snap] doesn't properly save desktop files for "create shortcuts"
  action

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  For chrome apps, the create shortcuts action should create desktop
  files but it doesn't.  I suspect it has something to do with paths.

  
  
  tracking:candidate
  installed:   62.0.3202.94 (123) 246MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1985856] Re: Update Mutter to 42.5

[Roman Shipovskij]

There is a new bugfix release 42.6 in the stable 42 series.

https://gitlab.gnome.org/GNOME/mutter/-/blob/42.6/NEWS

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

Title:
  Update Mutter to 42.5

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+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 1994949] [NEW] ubuntu-wallpapers package kinetic 22.10

[Tanupy ume]

Public bug reported:

kinetic-wallpapers.xml
kinetic.xml

wrong)Twisted_Gradients_by_Gustavo_Brenner.jpg
right)Twisted_Gradients_by_Gustavo_Brenner.png
:-)

** Affects: ubuntu-wallpapers (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ubuntu-wallpapers package kinetic 22.10

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  kinetic-wallpapers.xml
  kinetic.xml

  wrong)Twisted_Gradients_by_Gustavo_Brenner.jpg
  right)Twisted_Gradients_by_Gustavo_Brenner.png
  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1994949/+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 1993809] Re: Update gnome-shell to 42.5

[Roman Shipovskij]

There is a new bugfix release 42.6 in the stable 42 series.

https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.6/NEWS

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

Title:
  Update gnome-shell to 42.5

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS

  The version currently in Ubuntu 22.04.1 LTS is 42.4

  Test Case
  -
  Complete all the test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  I also cherry-picked a fix from kinetic:
  gsettings org.gnome.settings-daemon.peripherals.mouse
  no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop 
trying to report customizations for that gsettings schema.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993809/+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 1994941] Re: I locked computer after night I am trying to turn on by open lid and am see dark srceen. keyboard does not respond, can connect only by ssh from other pc.

[Alex]

sudo gdm3 restart
from ssh is solve the problem, but I lose open applications

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

Title:
  I locked computer after night  I am trying to turn on by open lid and
  am see dark srceen. keyboard does not respond,  can connect only by
  ssh from other pc.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I locked computer. After night  I am trying to turn on by open lid and
  I am see dark srceen. keyboard does not respond,  can connect only by
  ssh from other pc.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 27 14:33:47 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-10 (17 days ago)
  InstallationMedia: Ubuntu 20.04.4 2022.08.10 LTS "Custom Focal Fossa" 
(20220810)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-10-10 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994941/+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 1994941] [NEW] I locked computer after night I am trying to turn on by open lid and am see dark srceen. keyboard does not respond, can connect only by ssh from other pc.

[Alex]

Public bug reported:

I locked computer. After night  I am trying to turn on by open lid and I
am see dark srceen. keyboard does not respond,  can connect only by ssh
from other pc.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Oct 27 14:33:47 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-10-10 (17 days ago)
InstallationMedia: Ubuntu 20.04.4 2022.08.10 LTS "Custom Focal Fossa" (20220810)
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-10-10 (16 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  I locked computer after night  I am trying to turn on by open lid and
  am see dark srceen. keyboard does not respond,  can connect only by
  ssh from other pc.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I locked computer. After night  I am trying to turn on by open lid and
  I am see dark srceen. keyboard does not respond,  can connect only by
  ssh from other pc.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 27 14:33:47 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-10 (17 days ago)
  InstallationMedia: Ubuntu 20.04.4 2022.08.10 LTS "Custom Focal Fossa" 
(20220810)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-10-10 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994941/+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 1994939] [NEW] It is not possible to add IPsec/IKEv2 (strongswan) vpn connection

[Decio Della Fortuna]

Public bug reported:

It is not possible to add  IPsec/IKEv2 (strongswan) vpn connection, the system 
freezes and then show "Error unable to load vpn connection editor".
The package network-manager-strongswan and relative addon and libraries are 
installed.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: network-manager-gnome 1.28.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 27 08:59:35 2022
InstallationDate: Installed on 2022-10-21 (6 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
IpRoute:
 default via 192.168.128.1 dev enp0s31f6 proto dhcp src 192.168.128.101 metric 
100 
 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
 172.16.175.0/24 dev vmnet1 proto kernel scope link src 172.16.175.1 
 172.16.249.0/24 dev vmnet8 proto kernel scope link src 172.16.249.1 
 192.168.128.0/24 dev enp0s31f6 proto kernel scope link src 192.168.128.101 
metric 100
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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

** Attachment added: "Schermata del 2022-10-27 09-10-06.png"
   
https://bugs.launchpad.net/bugs/1994939/+attachment/5627177/+files/Schermata%20del%202022-10-27%2009-10-06.png

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

Title:
  It is not possible to add  IPsec/IKEv2 (strongswan) vpn connection

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

Bug description:
  It is not possible to add  IPsec/IKEv2 (strongswan) vpn connection, the 
system freezes and then show "Error unable to load vpn connection editor".
  The package network-manager-strongswan and relative addon and libraries are 
installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager-gnome 1.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 27 08:59:35 2022
  InstallationDate: Installed on 2022-10-21 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  IpRoute:
   default via 192.168.128.1 dev enp0s31f6 proto dhcp src 192.168.128.101 
metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   172.16.175.0/24 dev vmnet1 proto kernel scope link src 172.16.175.1 
   172.16.249.0/24 dev vmnet8 proto kernel scope link src 172.16.249.1 
   192.168.128.0/24 dev enp0s31f6 proto kernel scope link src 192.168.128.101 
metric 100
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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