[Desktop-packages] [Bug 1965897] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) from meta_window_actor_queue_destroy() from meta_compositor_real_remove_window() from

[Daniel van Vugt]

Yes all the remaining crashes in gnome-shell 42.2 are from mutter 42.0
or 41.1. So the fix is indeed in mutter 42.2.

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Fix Released

** Tags added: fixed-in-42.2 fixed-upstream

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_get_window_type(window=NULL) from
  meta_window_actor_queue_destroy() from
  meta_compositor_real_remove_window() from meta_window_unmanage() from
  meta_display_unmanage_windows()

Status in GNOME Shell:
  New
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/0f9ebdf291c30c238c6f29d22b7d503ef8910bdd

  ---

  Crashed after I tried to restart the shell with the 'r' command.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 10:59:42 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-02-25 (24 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/bin/gnome-shell
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
  UpgradeStatus: Upgraded to jammy on 2022-03-14 (7 days ago)
  UserGroups: sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1965897/+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 1915681] Re: Error in freeze/thaw accounting, GNOME Shell crashed with signal 5, resource:///org/gnome/shell/ui/windowManager.js:1384

[Daniel van Vugt]

Seems the above confusion no longer applies. All instances of this crash
appear to have stopped around 21.04.

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

Title:
  Error in freeze/thaw accounting, GNOME Shell crashed with signal 5,
  resource:///org/gnome/shell/ui/windowManager.js:1384

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: Error in freeze/thaw accounting
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: GNOME Shell crashed with signal 5
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: == Stack trace for context 
0x561dd4480270 ==
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: #0   561dd96ccf18 i   
resource:///org/gnome/shell/ui/windowManager.js:1384 (1c61e18d03d0 @ 589)
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: #1   7ffc72c53090 b   
self-hosted:850 (22fd89d4e5b0 @ 454)

  Taken from https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1897765/comments/38

  This crash will also show up in the existing error buckets from bug
  1897765:

  https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915681/+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 1902237] Re: nvidia-340 revision number is empty

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-340 revision number is empty

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Error while installing nvidia-340 package

  in french :
  dpkg: erreur: mauvaise syntaxe de la version « - »: revision number is empty

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nvidia-340 340.108-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 30 14:01:44 2020
  InstallationDate: Installed on 2019-09-27 (399 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: nvidia-graphics-drivers-340
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1902237/+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 1980080] Re: Unable to eject SDcard -getting remounted immediately

[Daniel van Vugt]

** Tags removed: impish
** Tags added: jammy

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

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

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

Title:
  Unable to eject SDcard -getting remounted immediately

Status in gvfs package in Ubuntu:
  New

Bug description:
  THe problem is on Dell XPS13 9310 and built-in microSD card reader(without 
adapter). When I plug the card it's visiible in file manager, with little 
'eject' icon. I can read/write to it. After finishing and using eject button. 
THe card it's still present in gnome along with 'eject' button. But when 
clicking eject it says 'No object for D-bus interface' and both the device and 
partition blockdevices are still present. 
  I can't also eject from command line:
  nusch@xps13:~$ LANG="en" eject -v /dev/mmcblk0
  eject: device name is `/dev/mmcblk0'
  eject: /dev/mmcblk0: not mounted
  eject: /dev/mmcblk0: is whole-disk device
  eject: /dev/mmcblk0: trying to eject using CD-ROM eject command
  eject: CD-ROM eject command failed
  eject: /dev/mmcblk0: trying to eject using SCSI commands
  eject: not an sg device, or old sg driver
  eject: SCSI eject failed
  eject: /dev/mmcblk0: trying to eject using floppy eject command
  eject: floppy eject command failed
  eject: /dev/mmcblk0: trying to eject using tape offline command
  eject: tape offline command failed
  eject: unable to eject

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
  Uname: Linux 5.10.0-1057-oem x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu71.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 28 13:31:39 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-05-08 (2608 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2022-02-21 (126 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1980080/+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 1980080] [NEW] Unable to eject SDcard -getting remounted immediately

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

THe problem is on Dell XPS13 9310 and built-in microSD card reader(without 
adapter). When I plug the card it's visiible in file manager, with little 
'eject' icon. I can read/write to it. After finishing and using eject button. 
THe card it's still present in gnome along with 'eject' button. But when 
clicking eject it says 'No object for D-bus interface' and both the device and 
partition blockdevices are still present. 
I can't also eject from command line:
nusch@xps13:~$ LANG="en" eject -v /dev/mmcblk0
eject: device name is `/dev/mmcblk0'
eject: /dev/mmcblk0: not mounted
eject: /dev/mmcblk0: is whole-disk device
eject: /dev/mmcblk0: trying to eject using CD-ROM eject command
eject: CD-ROM eject command failed
eject: /dev/mmcblk0: trying to eject using SCSI commands
eject: not an sg device, or old sg driver
eject: SCSI eject failed
eject: /dev/mmcblk0: trying to eject using floppy eject command
eject: floppy eject command failed
eject: /dev/mmcblk0: trying to eject using tape offline command
eject: tape offline command failed
eject: unable to eject

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
Uname: Linux 5.10.0-1057-oem x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu71.2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 28 13:31:39 2022
DisplayManager: gdm3
InstallationDate: Installed on 2015-05-08 (2608 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to impish on 2022-02-21 (126 days ago)

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


** Tags: amd64 apport-bug jammy third-party-packages wayland-session
-- 
Unable to eject SDcard -getting remounted immediately
https://bugs.launchpad.net/bugs/1980080
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gvfs 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 1947698] Re: window buttons alignment is wrong in RTL locales

[Brian Murray]

Hello Danial, or anyone else affected,

Accepted gtk4 into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gtk4/4.6.6+ds-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

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

Title:
  window buttons alignment is wrong in RTL locales

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

Bug description:
  Impact
  --
  gtk4 is completely untranslated.

  For RTL locales (such as Farsi, Arabic, and Hebrew), GTK4 apps also
  have the wrong alignment because of this bug.

  Test Case
  -
  https://translations.launchpad.net/ubuntu/jammy/+source/gtk4/+pots/gtk40
  will look similar to
  https://translations.launchpad.net/ubuntu/kinetic/+source/gtk4/+pots/gtk40

  and

  
https://translations.launchpad.net/ubuntu/jammy/+source/gtk4/+pots/gtk40-properties
  will look similar to
  
https://translations.launchpad.net/ubuntu/kinetic/+source/gtk4/+pots/gtk40-properties

  They will show long lists of languages, many partially translated

  Other Info
  --
  This bug won't be fully fixed until a new language pack is built and 
published. That will happen shortly before the Ubuntu 22.04.1 milestone (so 
approximately late July).

  Original Bug Report
  ---
  In RTL locales (e.g. fa_IR.UTF-8), the alignment of window buttons (close, 
min, max) is reverted.

  For example, in the `gnome-chess` or `extensions`, window buttons are
  in the right corner, when all other windows has buttons on the left.

  21.10
  -
  This bug also affects Ubuntu 21.10 but there just isn't time to get this bug 
fixed there before End of Life on July 14.

  If you're affected, please upgrade to Ubuntu 22.04 LTS which will be
  supported for many more years.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libgtk-4-1 4.4.0+ds1-5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 19 12:57:21 2021
  InstallationDate: Installed on 2021-07-13 (98 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fa_IR
   SHELL=/bin/bash
  SourcePackage: gtk4
  UpgradeStatus: Upgraded to impish on 2021-10-16 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1947698/+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 1980742] Re: Update gtk4 to 4.6.6

[Brian Murray]

Hello Jeremy, or anyone else affected,

Accepted gtk4 into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gtk4/4.6.6+ds-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Update gtk4 to 4.6.6

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

Bug description:
  Impact
  --
  There is a new point release in the stable GTK 4.6 series.

  https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.6/NEWS

  Test Case 1
  ---
  Make sure that opening and saving files from the Firefox and Chromium snaps 
still work

  Test Case 2
  ---
  snap install portal-test
  snap run portal-test
  Verify that the app seems to still work ok

  What Could Go Wrong
  ---
  Ubuntu includes xdg-desktop-portal-gnome by default which is used for many 
snap actions like providing a file chooser. This is critical functionality for 
our snaps.

  The Ubuntu flavors use a different portal backend, most commonly xdg-
  desktop-portal-gtk which uses GTK3 so it's not affected by this SRU.

  The other gtk4 apps installed by default in Ubuntu are gnome-chess and
  gnome-shell-extension-prefs.

  gtk4 is part of core GNOME and is in my latest proposed update to the 
microrelease exception
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/42

  gtk4 has extensive build tests and autopkgtests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1980742/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

[li]

I still think the libva source build and install is not use the proper
default path, so the related app is unable to find driver from
/usr/local/,  these apps only use /usr/ lib search path.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the snap with

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if 
possible;
  - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
  - GPU (if in doubt, attach the output of `lscpu`);
  - CPU generation (if in doubt, attach the output of `lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

[li]

Try https://launchpad.net/~nteodosio/+snap/chromium-browser-
hwacc/+build/1819056

The libva seems not working.

run:  LIBVA_MESSAGING_LEVEL=2 snap run chromium 
--enable-features=VaapiVideoDecoder
log:

Gtk-Message: 07:27:15.926: Failed to load module "canberra-gtk-module"
Gtk-Message: 07:27:15.928: Failed to load module "canberra-gtk-module"
WARNING: Kernel has no file descriptor comparison support: Operation not 
permitted
[26304:26523:0713/072719.712410:ERROR:udev_watcher.cc(98)] Failed to begin udev 
enumeration.
Warning: /usr/lib/x86_64-linux-gnu/libvulkan_intel.so: cannot open shared 
object file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON 
/usr/lib/x86_64-linux-gnu/libvulkan_intel.so.Ignoring this JSON
Warning: /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so: cannot open shared object 
file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON 
/usr/lib/x86_64-linux-gnu/libvulkan_lvp.so.Ignoring this JSON
Warning: /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so: cannot open shared 
object file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON 
/usr/lib/x86_64-linux-gnu/libvulkan_radeon.so.Ignoring this JSON
Warning: vkCreateInstance: Found no drivers!
Error: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
at CheckVkSuccessImpl 
(../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
at CreateVkInstance 
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:387)
at Initialize 
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:263)
at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:193)
at operator() 
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:462)


There is no any libva log output

run: snap run --shell chromium
run: LIBVA_DRIVERS_PATH=/snap/chromium/current/usr/lib/x86_64-linux-gnu/dri/ 
vainfo

vainfo: error while loading shared libraries: libva-x11.so.2: cannot
open shared object file: No such file or directory

From the source, it seems libva-dev is removed in default apt install.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the snap with

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if 
possible;
  - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
  - GPU (if in doubt, attach the output of `lscpu`);
  - CPU generation (if in doubt, attach the output of `lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go t

[Desktop-packages] [Bug 1973638] Update Released

[Brian Murray]

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

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

Title:
  gnome-shell 42 leaks tens of megabytes with every screenshot

Status in GNOME Shell:
  Unknown
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gjs source package in Jammy:
  Fix Released
Status in gnome-shell source package in Jammy:
  Triaged

Bug description:
  [Impact]

  gnome-shell's memory usage grows by tens of megabytes with every
  screenshot. A few screenshots make it 100MB larger and a few dozen
  screenshots make it 1GB larger.

  [Test Plan]

  1. Log into gnome-shell.

  2. Measure its real memory usage:

     grep RSS /proc/`pidof gnome-shell`/status

  3. Take 20 full screen screenshots by pressing PrtScn each time. No
  need to save them anywhere.

  4. Measure the memory usage again.

  Expected: Memory usage grows a little but growth does not exceed a few
  hundred megabytes. It should level off after a while and sometimes
  even shrink due to garbage collection.

  Observed: Memory usage grows without bounds, easily exceeding 1GB
  after about 20 screenshots (depending on screen resolution). It never
  shrinks significantly.

  [Where problems could occur]

  Since the fix affects GJS, problems could occur in any part of gnome-
  shell.

  [Other Info]

  This leak requires multiple fixes to minimize the memory usage. For
  the moment we are only aiming to fix the main GJS portion of the bug
  that allows memory usage to exceed 1GB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot

[Launchpad Bug Tracker]

This bug was fixed in the package gjs - 1.72.0-3~ubuntu22.04.2

---
gjs (1.72.0-3~ubuntu22.04.2) jammy; urgency=medium

  * Cherry-pick patch to fix memory leak seen when taking screenshots
(LP: #1973638)

 -- Jeremy Bicha   Wed, 29 Jun 2022 08:44:53 -0400

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

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

Title:
  gnome-shell 42 leaks tens of megabytes with every screenshot

Status in GNOME Shell:
  Unknown
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gjs source package in Jammy:
  Fix Released
Status in gnome-shell source package in Jammy:
  Triaged

Bug description:
  [Impact]

  gnome-shell's memory usage grows by tens of megabytes with every
  screenshot. A few screenshots make it 100MB larger and a few dozen
  screenshots make it 1GB larger.

  [Test Plan]

  1. Log into gnome-shell.

  2. Measure its real memory usage:

     grep RSS /proc/`pidof gnome-shell`/status

  3. Take 20 full screen screenshots by pressing PrtScn each time. No
  need to save them anywhere.

  4. Measure the memory usage again.

  Expected: Memory usage grows a little but growth does not exceed a few
  hundred megabytes. It should level off after a while and sometimes
  even shrink due to garbage collection.

  Observed: Memory usage grows without bounds, easily exceeding 1GB
  after about 20 screenshots (depending on screen resolution). It never
  shrinks significantly.

  [Where problems could occur]

  Since the fix affects GJS, problems could occur in any part of gnome-
  shell.

  [Other Info]

  This leak requires multiple fixes to minimize the memory usage. For
  the moment we are only aiming to fix the main GJS portion of the bug
  that allows memory usage to exceed 1GB.

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

[Brian Murray]

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

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

Title:
  Broken background portal autostart in 1.14.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Jammy:
  Fix Released

Bug description:
  - Impact

  With 1.14.3 the background portal creates a broken autostart file (it
  sends an incorrectly quoted app ID to implementations). This means
  apps like EasyEffects or Pika Backup cannot rely on the background
  portal to create a working autostart file. Please update to xdg-
  desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop-
  portal/releases/tag/1.14.4 which fixes this issue.

  - Test Case

  1. Install ASHPD Demo
  https://flathub.org/apps/details/com.belmoussaoui.ashpd.demo from
  Flathub

  2. Within the app make a background portal request with auto start
  enabled (you must accept the prompt from GNOME Shell)

  3. Note the contents of
  ~/.config/autostart/com.belmoussaoui.ashpd.demo.desktop is a desktop
  file, however the exec key’s value has an app id with quotes, making
  it invalid.

  4. After logging out and in or restarting, the app will not already be
  running, even though it previously asked the portal API for it to be
  auto started.

  The same steps can be repeated with EasyEffects from Flathub instead
  of ASHPD Demo, note the EasyEffects switch is named "Start Service at
  Login" within EasyEffects' preferences menu.

  When the bug is fixed, the created desktop file for auto start is
  valid and the app will start after login.

  - Regression potential

  The update is a new minor version including the fix for that bug and
  translation updates (which are going to be imported by launchpad but
  not part of the deb on Ubuntu)

  The codepath change is specific to flatpak commandline parsing so
  check that flatpaks still start correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1975638/+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 1975638] Re: Broken background portal autostart in 1.14.3

[Launchpad Bug Tracker]

This bug was fixed in the package xdg-desktop-portal -
1.14.4-1ubuntu1~22.04.1

---
xdg-desktop-portal (1.14.4-1ubuntu1~22.04.1) jammy; urgency=medium

  * New stable update
- background: Fix a regression introduced in 1.14.0 which caused invalid
  autostart files to be generated. (lp: #1975638)

 -- Sebastien Bacher   Mon, 13 Jun 2022 16:09:30
+0200

** Changed in: xdg-desktop-portal (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Broken background portal autostart in 1.14.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Jammy:
  Fix Released

Bug description:
  - Impact

  With 1.14.3 the background portal creates a broken autostart file (it
  sends an incorrectly quoted app ID to implementations). This means
  apps like EasyEffects or Pika Backup cannot rely on the background
  portal to create a working autostart file. Please update to xdg-
  desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop-
  portal/releases/tag/1.14.4 which fixes this issue.

  - Test Case

  1. Install ASHPD Demo
  https://flathub.org/apps/details/com.belmoussaoui.ashpd.demo from
  Flathub

  2. Within the app make a background portal request with auto start
  enabled (you must accept the prompt from GNOME Shell)

  3. Note the contents of
  ~/.config/autostart/com.belmoussaoui.ashpd.demo.desktop is a desktop
  file, however the exec key’s value has an app id with quotes, making
  it invalid.

  4. After logging out and in or restarting, the app will not already be
  running, even though it previously asked the portal API for it to be
  auto started.

  The same steps can be repeated with EasyEffects from Flathub instead
  of ASHPD Demo, note the EasyEffects switch is named "Start Service at
  Login" within EasyEffects' preferences menu.

  When the bug is fixed, the created desktop file for auto start is
  valid and the app will start after login.

  - Regression potential

  The update is a new minor version including the fix for that bug and
  translation updates (which are going to be imported by launchpad but
  not part of the deb on Ubuntu)

  The codepath change is specific to flatpak commandline parsing so
  check that flatpaks still start correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1975638/+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 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session

[Jiri Jurica]

Hello,

as I can see you discuss two different issues that I faced as well:

- The first is that setting up alt + shift shortcut using gnome-tweaks does not 
work properly anymore (it was working on Ubuntu 20.4) because it does not 
modify the language indicator. 
- The second is that if you try to set up this shortcut using Ubuntu settings 
(Keyboard -> Shortcuts -> Switch to the next source / Switch to the previous 
source), it will take only specific keys and ignores alt and shift. It seems 
like a bug/useless restriction in the GUI app.

I found the following workaround for the second issue (execute commands as user 
that is logged to graphical environment):
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Alt_L']"
gsettings set org.gnome.desktop.wm.keybindings switch-input-source-backward 
"['Shift_L']"
This breaks the key restrictions in settings and ensures expected behavior 
including changing the language indicator.

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

Title:
  Using certain xkb-options, e.g. Alt+Shift, for switching input sources
  not reflected by the input source indicator in a wayland session

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

Bug description:
  Currently, there is no way to define Left Alt + Left Shift key combination to 
change keyboard layouts in Ubuntu 22.04. In previous versions there was a 
convenient "Keyboard Layout Options" window in which there was able to set 
required key combination. Since 22.04 release I can't find a way to do that 
because useless "Keyboard Shortcuts" window opens instead in which unable to 
set Left Alt + Left Shift as "Switch to the next source" shortcut.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-01-07 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  jammy wayland-session ubiquity-22.04.3
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+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 1958019]

[belozyorcev]

Hi guys!

I also have problem with subwoofers (like in comment #559) on Lenovo
Yoga Slim 7 Carbon 14ACN6.

https://psref.lenovo.com/Detail/Yoga/Yoga_Slim_7_Carbon_14ACN6?M=82L0005PRK

I tried kernels 5.18.10, 5.17.15 (and 5.17.0-1012-oem on Ubuntu).

The sound is bad everywhere :(

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

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1930485] Re: Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.

[Bug Watch Updater]

** Changed in: firefox
   Status: New => Unknown

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

Title:
  Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  New

Bug description:
  I am running Weston/Wayland on Ubuntu 18.0.4.

  I am able to successfully start the display server:
  ```
  export XDG_RUNTIME_DIR=/run/weston
  weston --tty 1 &
  ```

  Next, I try to run firefox on it:

  ```
  export XDG_RUNTIME_DIR=/run/weston
  export GDK_BACKEND=wayland
  export MOZ_ENABLE_WAYLAND=1
  export DISPLAY=wayland-0
  export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/
  export WAYLAND_DEBUG=1
  export WAYLAND_DISPLAY=wayland-0

  firefox \
--g-fatal-warnings \
--kiosk \
--private-window \
https://bing.com
  ```

  This outputs:

  ```
  [1446891.592]  -> wl_display@1.get_registry(new id wl_registry@2)
  [1446891.702]  -> wl_disp...@1.sync(new id wl_callback@3)
  [1446893.656] wl_display@1.delete_id(3)
  [1446893.737] wl_registry@2.global(1, "wl_compositor", 4)
  [1446893.781]  -> wl_regis...@2.bind(1, "wl_compositor", 3, new id 
[unknown]@4)
  [1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1)
  [1446893.889]  -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id 
[unknown]@5)
  [1446893.938] wl_registry@2.global(3, "wp_viewporter", 1)
  [1446893.973] wl_registry@2.global(4, "wp_presentation", 1)
  [1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1)
  [1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1)
  [1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3)
  [1446894.109]  -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id 
[unknown]@6)
  [1446894.156] wl_registry@2.global(8, "wl_shm", 1)
  [1446894.190]  -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7)
  [1446894.429]  -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304)
  [1446894.974]  -> wl_shm_pool@8.resize(5568)
  [1446895.214]  -> wl_shm_pool@8.resize(12096)
  [1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4)
  [1446895.315] wl_registry@2.global(10, "wl_seat", 5)
  [1446895.353]  -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9)
  [1446925.977]  -> wl_compositor@4.create_surface(new id wl_surface@10)
  [1446926.203]  -> wl_data_device_manager@6.get_data_device(new id 
wl_data_device@11, wl_seat@9)
  [1446926.370]  -> wl_compositor@4.create_surface(new id wl_surface@12)
  [1446926.636]  -> wl_disp...@1.sync(new id wl_callback@13)
  [1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3)
  [1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1)
  [1446926.906] wl_registry@2.global(13, "wl_output", 3)
  [1446926.965]  -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14)
  [1446927.172]  -> wl_disp...@1.sync(new id wl_callback@15)
  [1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1)
  [1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1)
  [1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1)
  [1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1)
  [1446927.494] wl_registry@2.global(18, "xdg_shell", 1)
  [1446927.585] wl_registry@2.global(19, "wl_shell", 1)
  [1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1)
  [1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1)
  [1446927.777] wl_callb...@3.done(1)
  [1446929.537] wl_display@1.delete_id(13)
  [1446929.624] wl_display@1.delete_id(15)
  [1446929.656] wl_shm@7.format(0)
  [1446929.684] wl_shm@7.format(1)
  [1446929.709] wl_shm@7.format(909199186)
  [1446929.733] wl_shm@7.format(842093913)
  [1446929.758] wl_shm@7.format(842094158)
  [1446929.783] wl_shm@7.format(1448695129)
  [1446929.807] wl_seat@9.capabilities(2)
  [1446929.834]  -> wl_seat@9.get_keyboard(new id wl_keyboard@3)
  [1446929.903] wl_s...@9.name("default")
  [1446929.931] wl_callb...@13.done(1)
  [1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0)
  [1446930.094] wl_output@14.scale(1)
  [1446930.123] wl_out...@14.mode(3, 1920, 1080, 6)
  [1446930.193] wl_out...@14.done()
  [1446930.245] wl_callb...@15.done(1)
  [1446930.278]  -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id 
[unknown]@15)
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed 
(t=0.548476) [GFX1-]: glxtest: EGL test failed
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed 
(t=0.548476) |[2][GFX1-]: No GPUs detected via PCI (t=0.548504) [GFX1-]: No 
GPUs dete

[Desktop-packages] [Bug 1877038]

[Bugs-c]

I can't give you an estimate but this is my current work item. The
priority of this meta bug wasn't reflecting that, my apologies.

-- 
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 27867]

[Ramstien168]

Thanks for sharing a great article.
You are providing wonderful information, it is very useful to us.
Keep posting like these informative articles.
Thank you. https://bugzilla.mozilla.org/show_bug.cgi?id=306625

pg game
https://pgslot.link/

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

Title:
  Background color is always white, top banner is never displayed in
  Firefox

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Problem shows whatever the version of Epiphany (before and after today's 
upodate
  ie).

  Whatever the website I visit, the background colour is always white, and the
  logo/banner at the top of the page, is not displayed.

  I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and
  no yellow background.

  http://bugzilla.gnome.org/show_bug.cgi?id=121118:
  http://bugzilla.gnome.org/show_bug.cgi?id=121118

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

[Robert Mader]

Closing as unresponsive (and likely fixed).

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

Title:
  Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  New

Bug description:
  I am running Weston/Wayland on Ubuntu 18.0.4.

  I am able to successfully start the display server:
  ```
  export XDG_RUNTIME_DIR=/run/weston
  weston --tty 1 &
  ```

  Next, I try to run firefox on it:

  ```
  export XDG_RUNTIME_DIR=/run/weston
  export GDK_BACKEND=wayland
  export MOZ_ENABLE_WAYLAND=1
  export DISPLAY=wayland-0
  export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/
  export WAYLAND_DEBUG=1
  export WAYLAND_DISPLAY=wayland-0

  firefox \
--g-fatal-warnings \
--kiosk \
--private-window \
https://bing.com
  ```

  This outputs:

  ```
  [1446891.592]  -> wl_display@1.get_registry(new id wl_registry@2)
  [1446891.702]  -> wl_disp...@1.sync(new id wl_callback@3)
  [1446893.656] wl_display@1.delete_id(3)
  [1446893.737] wl_registry@2.global(1, "wl_compositor", 4)
  [1446893.781]  -> wl_regis...@2.bind(1, "wl_compositor", 3, new id 
[unknown]@4)
  [1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1)
  [1446893.889]  -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id 
[unknown]@5)
  [1446893.938] wl_registry@2.global(3, "wp_viewporter", 1)
  [1446893.973] wl_registry@2.global(4, "wp_presentation", 1)
  [1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1)
  [1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1)
  [1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3)
  [1446894.109]  -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id 
[unknown]@6)
  [1446894.156] wl_registry@2.global(8, "wl_shm", 1)
  [1446894.190]  -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7)
  [1446894.429]  -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304)
  [1446894.974]  -> wl_shm_pool@8.resize(5568)
  [1446895.214]  -> wl_shm_pool@8.resize(12096)
  [1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4)
  [1446895.315] wl_registry@2.global(10, "wl_seat", 5)
  [1446895.353]  -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9)
  [1446925.977]  -> wl_compositor@4.create_surface(new id wl_surface@10)
  [1446926.203]  -> wl_data_device_manager@6.get_data_device(new id 
wl_data_device@11, wl_seat@9)
  [1446926.370]  -> wl_compositor@4.create_surface(new id wl_surface@12)
  [1446926.636]  -> wl_disp...@1.sync(new id wl_callback@13)
  [1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3)
  [1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1)
  [1446926.906] wl_registry@2.global(13, "wl_output", 3)
  [1446926.965]  -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14)
  [1446927.172]  -> wl_disp...@1.sync(new id wl_callback@15)
  [1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1)
  [1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1)
  [1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1)
  [1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1)
  [1446927.494] wl_registry@2.global(18, "xdg_shell", 1)
  [1446927.585] wl_registry@2.global(19, "wl_shell", 1)
  [1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1)
  [1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1)
  [1446927.777] wl_callb...@3.done(1)
  [1446929.537] wl_display@1.delete_id(13)
  [1446929.624] wl_display@1.delete_id(15)
  [1446929.656] wl_shm@7.format(0)
  [1446929.684] wl_shm@7.format(1)
  [1446929.709] wl_shm@7.format(909199186)
  [1446929.733] wl_shm@7.format(842093913)
  [1446929.758] wl_shm@7.format(842094158)
  [1446929.783] wl_shm@7.format(1448695129)
  [1446929.807] wl_seat@9.capabilities(2)
  [1446929.834]  -> wl_seat@9.get_keyboard(new id wl_keyboard@3)
  [1446929.903] wl_s...@9.name("default")
  [1446929.931] wl_callb...@13.done(1)
  [1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0)
  [1446930.094] wl_output@14.scale(1)
  [1446930.123] wl_out...@14.mode(3, 1920, 1080, 6)
  [1446930.193] wl_out...@14.done()
  [1446930.245] wl_callb...@15.done(1)
  [1446930.278]  -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id 
[unknown]@15)
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed 
(t=0.548476) [GFX1-]: glxtest: EGL test failed
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed 
(t=0.548476) |[2][GFX1-]: No GPUs detected via PCI (t=0.548504) [GFX1-]: No 
GPUs detected via 

[Desktop-packages] [Bug 1877038]

[Drew-dani]

Thanks for the update and suggestion. Can we prioritize this item? It has a 
large impact on 2 major tech companies.
Also, do you have an estimated completion date when FIDO2 will be available on 
Mac and Linux?

-- 
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 1969315] Re: text in torrent info tabs change after opening it to gibberish

[Nili]

This bug has also been affecting me in Devuan (testing) for several
months, I'm not sure when it started specifically, but I believe the
last 2 months i can say for sure.

Joined here because my searches in my distributor didn't turn up much
data.

I want also to add that Dialog Preferences/Properties tabs have issues
where changes by (confusing the data on this dialog), more or less like
the above posts, clicking repeatedly the tabs brings the application to
crash aswell sometimes.

Changing different GTK3 themes, even default Adwaita does not bring
anything positively or a fix.

I gathered some data on the attach.

** Attachment added: "transmission-gtk, error, crash, tabs+text issue"
   
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+attachment/5602682/+files/transmission-errors

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

Title:
  text in torrent info tabs change after opening it to gibberish

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  on transmission-gtk

  after opening the torrent's properties panel, the text at first it's showing 
ok, buy on mouse hover it changes to random text
  worked fine on 21.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 19:28:03 2022
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+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 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot

[Jeremy Bicha]

Before installing the update:
$ grep RSS /proc/`pidof gnome-shell`/status
VmRSS:323100 kB
after running the 20 screenshots
$ grep RSS /proc/`pidof gnome-shell`/status
VmRSS:605112 kB

and the size didn't really go down.


After installing gjs 1.72.0-3~ubuntu22.04.2,

$ grep RSS /proc/`pidof gnome-shell`/status
VmRSS:325388 kB

After the 20 screenshots
$ grep RSS /proc/`pidof gnome-shell`/status
VmRSS:559232 kB

After waiting a few moments
$ grep RSS /proc/`pidof gnome-shell`/status
VmRSS:340772 kB

That verifies this bug fix.

** Changed in: gnome-shell (Ubuntu)
 Assignee: Jeremy Bicha (jbicha) => (unassigned)

** Changed in: gnome-shell (Ubuntu Jammy)
 Assignee: Jeremy Bicha (jbicha) => (unassigned)

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

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

Title:
  gnome-shell 42 leaks tens of megabytes with every screenshot

Status in GNOME Shell:
  Unknown
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gjs source package in Jammy:
  Fix Committed
Status in gnome-shell source package in Jammy:
  Triaged

Bug description:
  [Impact]

  gnome-shell's memory usage grows by tens of megabytes with every
  screenshot. A few screenshots make it 100MB larger and a few dozen
  screenshots make it 1GB larger.

  [Test Plan]

  1. Log into gnome-shell.

  2. Measure its real memory usage:

     grep RSS /proc/`pidof gnome-shell`/status

  3. Take 20 full screen screenshots by pressing PrtScn each time. No
  need to save them anywhere.

  4. Measure the memory usage again.

  Expected: Memory usage grows a little but growth does not exceed a few
  hundred megabytes. It should level off after a while and sometimes
  even shrink due to garbage collection.

  Observed: Memory usage grows without bounds, easily exceeding 1GB
  after about 20 screenshots (depending on screen resolution). It never
  shrinks significantly.

  [Where problems could occur]

  Since the fix affects GJS, problems could occur in any part of gnome-
  shell.

  [Other Info]

  This leak requires multiple fixes to minimize the memory usage. For
  the moment we are only aiming to fix the main GJS portion of the bug
  that allows memory usage to exceed 1GB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1979347] Re: SRU pygobject 3.42.1, including fix for the append function

[Jeremy Bicha]

I also verified the fix. Before I installed python3-gi 3.42.1-0ubuntu1,
when I ran the script, I only got errors on the command line. After
installing the update, the window showed and there were no errors on the
command line.

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

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

Title:
  SRU pygobject 3.42.1, including fix for the append function

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

Bug description:
  >> Impact <<

  Applications crash when they call the append function to append data
  to stores.

  >> Test plan <<

  When executing the attached bug.py script,

  - With the fix: A dummy window with a text field is mapped.

  - Without the fix: An error message is raised and no window is mapped.

  >> Regression potential <<

  Since this includes a new upstream release, by looking at the NEWS
  file ,
  regressions could show up:

  - On programs which use ListStore and Treeview. Additionally, those
  changes should not affect GTK2 or GTK3.

  - As leaks, given the replace of g_error by g_critical by
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1979347/+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 1969303] Re: "No package to remove" error when attempting to uninstall

[fossfreedom]

ok - I have taken the commit from the snap-store-41 branch and applied
it - it works locally here.

I've pinged on IRC ubuntu-desktop how best to proceed with the SRU for
jammy

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Fix Released
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Jammy:
  Triaged

Bug description:
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+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 1969303] Re: "No package to remove" error when attempting to uninstall

[fossfreedom]

** Changed in: gnome-software (Ubuntu Jammy)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Fix Released
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Jammy:
  Triaged

Bug description:
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

[Łukasz Zemczak]

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.1

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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+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 1981432] [NEW] [SRU] Backport label-ft plugin to 22.04

[Alfonso Sanchez-Beato]

Public bug reported:

[Impact]

 * This is a request to backport changes in kinetic plymouth package
   to 0.9.5+git20211018-1ubuntu4 to jammy. That version contains a new
   plugin named label-ft, which was introduced to replace the label
   plugin in Ubuntu Core systems. The difference with the label plugin
   is that it pulls much less dependencies (LP: #1976352), which allows
   a much smaller initramfs. This change should not affect classic systems.

[Test Plan]

 * The test plan consists on creating a UC image using this package and
make sure that label.so and cairo/pango dependencies are not pulled,
while we still have a splash screen.

 * For classic, the test plan is to refresh plymouth and make sure that
   it still uses label.so and its dependencies, and still the splash
   works.

[Where problems could occur]

 * The change introduces a new package named plymouth-label-ft with the
label-ft.so plugin. This package will not be installed on classic by
default, and it is the main change proposed. The rest of the plymouth
code changes use label-ft.so as a fallback if label.so is not present.
This is just a few lines of code, and still uses label.so by default, so
the potential risk of breaking the splash should be small. If something
goes wrong, we could be without splash and without a user friendly way
of unlocking disks if using FDE.

[Other Info]

 * Change should be relevant for UC only

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

** Description changed:

  [Impact]
  
-  * This is a request to backport changes in kinetic plymouth package
-to 0.9.5+git20211018-1ubuntu4 to jammy. That version contains a new
-plugin named label-ft, which was introduced to replace the label
-plugin in Ubuntu Core systems. The difference with the label plugin
-is that it pulls much less dependencies (LP: #1976352), which allows
-a much smaller initramfs. This change should not affect classic systems.
+  * This is a request to backport changes in kinetic plymouth package
+    to 0.9.5+git20211018-1ubuntu4 to jammy. That version contains a new
+    plugin named label-ft, which was introduced to replace the label
+    plugin in Ubuntu Core systems. The difference with the label plugin
+    is that it pulls much less dependencies (LP: #1976352), which allows
+    a much smaller initramfs. This change should not affect classic systems.
  
  [Test Plan]
  
-  * The test plan consists on creating a UC image using this package and make
-sure that label.so and cairo/pango dependencies are not pulled, while we
-still have a splash screen.
+  * The test plan consists on creating a UC image using this package and
+ make sure that label.so and cairo/pango dependencies are not pulled,
+ while we still have a splash screen.
  
-  * For classic, the test plan is to refresh plymouth and make sure that
-it still uses label.so and its dependencies, and still the splash works.
+  * For classic, the test plan is to refresh plymouth and make sure that
+    it still uses label.so and its dependencies, and still the splash
+works.
  
  [Where problems could occur]
  
-  * The change introduces a new package named plymouth-label-ft with the 
label-ft.so
-plugin. This package will not be installed on classic by default, and it is
-the main change proposed. The rest of the plymouth code changes use 
label-ft.so
-as a fallback if label.so is not present. This is just a few lines of code,
-and still uses label.so by default, so the potential risk of breaking the 
splash
-should be small. If something goes wrong, we could be without splash and 
without
-a user friendly way of unlocking disks if using FDE.
+  * The change introduces a new package named plymouth-label-ft with the
+ label-ft.so plugin. This package will not be installed on classic by
+ default, and it is the main change proposed. The rest of the plymouth
+ code changes use label-ft.so as a fallback if label.so is not present.
+ This is just a few lines of code, and still uses label.so by default, so
+ the potential risk of breaking the splash should be small. If something
+ goes wrong, we could be without splash and without a user friendly way
+ of unlocking disks if using FDE.
  
  [Other Info]
-  
-  * Change should be relevant for UC only
+ 
+  * Change should be relevant for UC only

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

Title:
  [SRU] Backport label-ft plugin to 22.04

Status in plymouth package in Ubuntu:
  New

Bug description:
  [Impact]

   * This is a request to backport changes in kinetic plymouth package
     to 0.9.5+git20211018-1ubuntu4 to jammy. That version contains a new
     plugin named label-ft, which was introduced to replace the label
     plugin in Ubuntu Core systems. The difference with the label plugin
     is that it pulls much less 

[Desktop-packages] [Bug 711305] Re: Thunderbird is already running, but is not responding. To open a new window, you must first close the existing Thunderbird process, or restart your system. Error re

[Claudio Corvino]

Hi, I have the same problem with Thunderbird snap 102.0.2 and Ubuntu
20.04, if I try to "Compose a new message" from Gnome bar with right-
click I receive the "Already running" dialog.

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

Title:
  Thunderbird is already running, but is not responding. To open a new
  window, you must first close the existing Thunderbird process, or
  restart your system. Error received when clicking a mailto link in
  firefox.

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This thunderbird error is given when clicking a mailto link. Instead
  of using the thunderbird that's already open it tries to open a new
  instance. Preferred Applications has Thunderbird select, but I have
  also tried Custom command "thunderbird %s". This has been tested on
  10.04 and 10.10. Both result in this error if thunderbird is already
  running.

  Thunderbird is already running, but is not responding. To open a new
  window, you must first close the existing Thunderbird process, or
  restart your system.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Tue Feb  1 10:19:09 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/711305/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock

[Daniel van Vugt]

Comment #29 is now being tracked in
https://github.com/micheleg/dash-to-dock/issues/1769


** Bug watch added: github.com/micheleg/dash-to-dock/issues #1769
   https://github.com/micheleg/dash-to-dock/issues/1769

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

Title:
  Dock auto-hides when a right click context menu is opened while a
  window is under the dock

Status in Dash to dock:
  Fix Released
Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  If the dock is set to auto-hide and a window is under the dock, then
  the dock hides prematurely when a menu is opened from one of its
  icons. This only seems to happen with GNOME 42.

  [Test Plan]

  1. Set the dock to auto hide.
  2. Move a window under the dock's position so that it wants to auto-hide.
  3. Open the dock and right click on one of the icons to open a menu.

  Expected: Dock stays open while the menu is open.
  Observed: Dock closes while the menu is open.

  [Where problems could occur]

  This fix may affect any scenarios relating to the dock auto-hiding.

  [Other Info]

  Upstream fixes:
  ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739
  dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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 1981349] Re: wslu prevents from opening files and folders on some situations

[José Marinho]

** Description changed:

- With wslu installed, files and locations can't be opened from Gnome 
Activities View either on a Wayland session or a Xorg one. This affects too 
when I try to open from Places Status Indicator.In fact, I filed a bug some 
time ago, but that bug was expired. Now I found the reason and file a bug 
against the proper package.
- The bug is this one: 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181
- And I realized when I saw this thread: 
https://answers.launchpad.net/ubuntu/+question/701579
+ With wslu installed, files and locations can't be opened from Gnome 
Activities View either on a Wayland session or a Xorg one. This affects too 
when I try to open from Places Status Indicator.In fact, I filed a bug some 
time ago against this extension, but that bug was expired. Now I found the 
reason and then I create a bug report against the proper package.
+ The bug report against Places Status Indicator is this one: 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181
+ And I realized the cause of the bug against the extension when I saw this 
thread: https://answers.launchpad.net/ubuntu/+question/701579
+ Once I removed wslu from my system (on two different pc's) the problem with 
the extension has gone and I can open files and folders from Activities view.

** Description changed:

- With wslu installed, files and locations can't be opened from Gnome 
Activities View either on a Wayland session or a Xorg one. This affects too 
when I try to open from Places Status Indicator.In fact, I filed a bug some 
time ago against this extension, but that bug was expired. Now I found the 
reason and then I create a bug report against the proper package.
+ With wslu installed, files and locations can't be opened from Gnome 
Activities View either on a Wayland session or a Xorg one. This affects when I 
try to go to a location on Places Status Indicator too.In fact, I filed a bug 
some time ago against this extension, but that bug was expired. Now I found the 
reason and then I create a bug report against the proper package.
  The bug report against Places Status Indicator is this one: 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181
  And I realized the cause of the bug against the extension when I saw this 
thread: https://answers.launchpad.net/ubuntu/+question/701579
  Once I removed wslu from my system (on two different pc's) the problem with 
the extension has gone and I can open files and folders from Activities view.

** Description changed:

- With wslu installed, files and locations can't be opened from Gnome 
Activities View either on a Wayland session or a Xorg one. This affects when I 
try to go to a location on Places Status Indicator too.In fact, I filed a bug 
some time ago against this extension, but that bug was expired. Now I found the 
reason and then I create a bug report against the proper package.
+ With wslu installed, files and locations can't be opened from Gnome 
Activities View on a Wayland session or on a Xorg one. This affects when I try 
to go to a location on Places Status Indicator too.In fact, I filed a bug some 
time ago against this extension, but that bug was expired. Now I found the 
reason and then I create a bug report against the proper package.
  The bug report against Places Status Indicator is this one: 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181
  And I realized the cause of the bug against the extension when I saw this 
thread: https://answers.launchpad.net/ubuntu/+question/701579
  Once I removed wslu from my system (on two different pc's) the problem with 
the extension has gone and I can open files and folders from Activities view.

** Description changed:

- With wslu installed, files and locations can't be opened from Gnome 
Activities View on a Wayland session or on a Xorg one. This affects when I try 
to go to a location on Places Status Indicator too.In fact, I filed a bug some 
time ago against this extension, but that bug was expired. Now I found the 
reason and then I create a bug report against the proper package.
+ With wslu installed, files and locations can't be opened from Gnome 
Activities View on a Wayland session or on a Xorg one. The same happens when I 
try to go to a location on Places Status Indicator too.In fact, I filed a bug 
some time ago against this extension, but that bug was expired. Now I found the 
reason and then I create a bug report against the proper package.
  The bug report against Places Status Indicator is this one: 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181
  And I realized the cause of the bug against the extension when I saw this 
thread: https://answers.launchpad.net/ubuntu/+question/701579
  Once I removed wslu from my system (on two different pc's) the problem with 
the extension has gone and I can open files and folders from Activities view.

** Descrip

[Desktop-packages] [Bug 1959469] Comment bridged from LTC Bugzilla

[bugproxy]

An updated test package was created for kinetic and build with the help of this 
PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1959469
for the major architectures.

This incl. building and executing the testsuite too, which results in all tests 
passed:
...

All 112 tests passed

...
PASS: rsa-sign
PASS: rsa-verify
PASS: rsa-encrypt
==
All 3 tests passed
==

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions

[Yuan-Chen Cheng]

** Tags added: jellyfish-edge-staging

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

Title:
  Displaylink is extremely slow in Xorg sessions

Status in Nouveau Xorg driver:
  New
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Hirsute:
  Won't Fix
Status in xorg-server source package in Impish:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  New
Status in xserver-xorg-video-nouveau source package in Jammy:
  New

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

[Simon Chopin]

** Tags added: fr-2537

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+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 1972790] Re: Can't connect to hotspot created on ubuntu

[Dustin Utecht]

I tried to connect to the AP on 07:49:xx.

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1969315] Re: text in torrent info tabs change after opening it to gibberish

[Sebastien Bacher]

The bug is weird yes, I've never been able to trigger it on my
installation. It could be that it depends of a library yes, of from the
theme in use perhaps, or other factor...

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

Title:
  text in torrent info tabs change after opening it to gibberish

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  on transmission-gtk

  after opening the torrent's properties panel, the text at first it's showing 
ok, buy on mouse hover it changes to random text
  worked fine on 21.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 19:28:03 2022
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+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 1972790] Re: Can't connect to hotspot created on ubuntu

[Sebastien Bacher]

Thanks, that's the complete log though and not the part from -f when a
client tried to connect right? Did you maybe note down the time when you
tried to connect?

The log has nl80211 warnings similar to bug #1886169 , unsure if that
could be the issue though

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1970473] Re: [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

[Bug Watch Updater]

** Changed in: xserver-xorg-video-ati (Debian)
   Status: Unknown => Fix Released

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

Title:
  [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

Status in xserver-xorg-video-ati package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-ati source package in Jammy:
  Fix Committed
Status in xserver-xorg-video-ati package in Debian:
  Fix Released

Bug description:
  * Impact

  The xserver crash, closing the session, when trying to rotate the
  screen when using the ati driver

  * Test case
  - start an xorg based session
  - try to rotate the screen by 90°

  -> the session shouldn't close

  * Regression potential

  if the fix was incorrect it could lead to screen parameters not being
  set correctly. Try changing the resolution and rotation and ensure the
  changes are what is expected

  

  
  When using Settings/Display/Orientation/Portret right and Apply then X 
crashes and login screen is displayed. Tested with 3 different AMD systems 
(older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro MT PC
  dmi.product.sku: AT493AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/xserver-xorg-video-ati/+bug/1970473/+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 1972790] Re: Can't connect to hotspot created on ubuntu

[Dustin Utecht]

1. yes.
2. currently to busy, sorry!
3. uploaded a log

I tried to connect via MacBook (macOS Monterey 12.4), Iphone (iOS 15.5),
Android (Version unknown).

** Attachment added: "wpa.log"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+attachment/5602531/+files/wpa.log

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1978307] Re: gwenview aborts with a std::out_of_range exception raised in libexiv2

[Arrigo Marchiori]

Here is a more detailed gdb output

terminate called after throwing an instance of 'std::out_of_range'  

 
  what():  basic_string::at: __n (which is 19) >= this->size() (which is 19)

 

Thread 1 "gwenview" received signal SIGABRT, Aborted.   

 
0xf7fd5079 in __kernel_vsyscall ()  

 
(gdb) bt

 
#0  0xf7fd5079 in __kernel_vsyscall ()  

 
#1  0xf5d1ea02 in __libc_signal_restore_set (set=0xc0cc) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
 
#2  __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 

 
#3  0xf5d1fe91 in __GI_abort () at abort.c:79   

 
#4  0xf5f3b97d in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 

 
#5  0xf5f43174 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 

 
#6  0xf5f431dd in std::terminate() () from 
/usr/lib/i386-linux-gnu/libstdc++.so.6  
  
#7  0xf5f434dc in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6

 
#8  0xf5f6defa in std::__throw_out_of_range_fmt(char const*, ...) () from 
/usr/lib/i386-linux-gnu/libstdc++.so.6  
   
#9  0xf5881da3 in std::__cxx11::basic_string, 
std::allocator >::at (__n=19, this=0xc67c)
  
at /usr/include/c++/7/bits/basic_string.h:1098  

 
#10 Exiv2::Internal::printXmpDate (os=..., value=...) at tags.cpp:2774  

 
#11 0xf58c3aff in Exiv2::Xmpdatum::write (this=0xe7016260, os=...) at 
xmp.cpp:281 
   
#12 0xf7d870af in Exiv2::operator<< (md=..., os=...) at 
/usr/include/exiv2/metadatum.hpp:305
 
#13 Gwenview::ImageMetaInfoModelPrivate::fillExivGroup > > > (this=, parent=..., 
group=, container=...) at ./lib/imagemetainfomodel.cpp:284   

#14 0xf7d8212f in Gwenview::ImageMetaInfoModel::setExiv2Image (this=, image=) at ./lib/imagemetainfomodel.cpp:454
  
#15 0xf7d2fa54 in Gwenview::Document::setExiv2Image (this=0x56ad70b0, 
image=...) at ./lib/document/document.cpp:395   
   
#16 0xf7d2e7f0 in Gwenview::AbstractDocumentImpl::setDocumentExiv2Image 
(this=0x56b73570, image=...) at ./lib/document/abstractdocumentimpl.cpp:82  
 
#17 0xf7d434b3 in Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded 
(this=0x56b73570) at ./lib/document/loadingdocumentimpl.cpp:491 
 
#18 0xf7debf44 in Gwenview::LoadingDocumentImpl::qt_static_metacall 
(_o=0x56b73570, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xcb78) 
 
at 
./obj-i686-linux-gnu/lib/gwenviewlib_autogen/DV7UALDUNI/moc_loadingdocumentimpl.cpp:85

#19 0xf6303c6e in QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
[...]

I hope this helps.

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

Title:
  gwenview aborts with a std::out_of_range exception raised in libexiv2

Status in exiv2 package in Ubuntu:
  New
Status in gwenview package in Ubuntu:
  New

Bug description:
  This bug seems to be a regression of KDE bug 441121:
  https://bugs.kde.org/show_bug.cgi?id=441121

  When opening certain JPG files, gwenview aborts with an uncaught C++
  exception std::out_of_range

  System is Ubuntu 18.04.6 LTS x86 with up-to-date packages.

[Desktop-packages] [Bug 1085] Re: selecting text in full header mode fails

[Bug Watch Updater]

** Changed in: thunderbird
   Importance: Medium => Unknown

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

Title:
  selecting text in full header mode fails

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  control+a does not select all the text in the full header window

  
  WORKAROUND:
  use   View|Message Source   instead of  View|Headers|All

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

[9-henry]

There are still plans to update the message header recipient list along
the lines of
https://bugzilla.mozilla.org/attachment.cgi?id=9243994&action=edit I'm
not aware of an open bug for this specifically.

Bug 1752532 is introducing new multi-selection widgets that we plan on
using for the recipients list (specifically, the "grouped list" widget).
I'll block on this for the time being.

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

Title:
  selecting text in full header mode fails

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  control+a does not select all the text in the full header window

  
  WORKAROUND:
  use   View|Message Source   instead of  View|Headers|All

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

[Bugzilla2007]

*** Bug 356745 has been marked as a duplicate of this bug. ***

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

Title:
  selecting text in full header mode fails

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  control+a does not select all the text in the full header window

  
  WORKAROUND:
  use   View|Message Source   instead of  View|Headers|All

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

[Bugzilla2007]

*** Bug 327621 has been marked as a duplicate of this bug. ***

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

Title:
  selecting text in full header mode fails

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  control+a does not select all the text in the full header window

  
  WORKAROUND:
  use   View|Message Source   instead of  View|Headers|All

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

[Bugzilla2007]

For an impression how much users want to select and copy from inbound
message headers, see the ancient parent bug:

Bug 61497 - [SM] Can't select text in message headers / copy subject

**42 duplicates** were filed against that bug, most of them demanding
that *all* of the headers should be selectable for copying, i.e.
including *recipients*. However, bug 61497 only fixed half of the
problem (selecting subject), the other half was moved to this bug 167010
(originally `SeaMonkey`, then `MailNews Core`, now `Thunderbird`).

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

Title:
  selecting text in full header mode fails

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  control+a does not select all the text in the full header window

  
  WORKAROUND:
  use   View|Message Source   instead of  View|Headers|All

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

[Bugzilla2007]

Ryan, Alex, Henry - FYI wrt 114.
10+ duplicates atm, and 42 users CC'ed.

If we could have a similar UX as in composition (easily selectable
recipient pills), that would support this basic workflow for many users
and avoid clumsy workarounds in 2023 (see user story for more).

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

Title:
  selecting text in full header mode fails

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  control+a does not select all the text in the full header window

  
  WORKAROUND:
  use   View|Message Source   instead of  View|Headers|All

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1085/+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 1980718] Re: External monitor not working on Wayland

[Daniel van Vugt]

No action required. Closed.

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

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

Title:
  External monitor not working on Wayland

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  When I connect the external monitor the image is shown on the external
  display but it freezes (on both displays); after I unplug the external
  display the following errors are logged (not sure it is related to the
  freeze):

  Jul  5 09:19:39 xps gnome-shell[10252]: 
meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < 
n_logical_monitors' failed
  Jul  5 09:19:39 xps gnome-shell[10252]: 
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) 
number < g_list_length (manager->logical_monitors)' failed
  Jul  5 09:19:39 xps gnome-shell[10252]: 
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' 
failed

  The external display is connected via a thunderbolt port and an
  adapter to HDMI.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  5 09:21:33 2022
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-08-07 (696 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (68 days ago)

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