[Desktop-packages] [Bug 2056767] Re: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split

[Jeremy Bícha]

** Tags removed: block-proposed

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

Title:
  FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main)
  with gnome-software packaging split

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Impact
  --
  I request permission to sync the gnome-software packaging from Debian. The 
biggest change is splitting gnome-software's .deb support into a separate 
package, gnome-software-plugin-deb, to match the existing -snap and -flatpak 
packages. This will allow users and flavors to specifically opt into the parts 
of the GNOME Software experience they want. For instance, someone may want to 
use only the Flatpak part because they use the Snap Store to manage .debs and 
Snaps. Or maybe they want a different combination.

  This has been requested by multiple users on Ubuntu Discourse and at
  least one Launchpad bug and one Debian bug.

  fwupd plugin
  
  I am dropping the fwupd plugin (now in a separate package too) to Suggests so 
upgrades to Ubuntu 24.04 LTS will likely get it uninstalled and new installs 
won't have it either unless a user explicitly installs it later.

  Ubuntu Desktop includes the firmware-updater snap. Several Ubuntu
  desktop flavors also include it. For people who don't want snaps,
  there is also the gnome-firmware app packaged as a .deb.

  Because Ubuntu already has update-manager to handle apt update
  notifications, I am also dropping the autostart file to reduce
  background RAM use.

  A few Ubuntu desktop flavors do not provide any firmware updater app
  at all. Ubuntu Budgie developers thought a firmware updater app was
  too technical for inclusion in the default Ubuntu 24.04 LTS install.

  autostart
  -
  I have also dropped the autostart file since the fwupd plugin is no longer 
included by default and Ubuntu already has ways to notify users about available 
apt updates (update-manager and unattended upgrades) and snaps already 
automatically update.

  Potential Problems
  ---
  gnome-software has an explicit Recommend: gnome-software-plugin-deb so that 
people upgrading to Ubuntu 24.04 LTS will keep the deb support installed. That 
recommends will be dropped for Ubuntu 26.04 LTS because it won't be needed 
then. (There is a Depends on the virtual packages that enable installing apps.)

  Full Changelog Entries
  --
  gnome-software (46.0-4) unstable; urgency=medium

    * Fix typo in gnome-software-plugin-deb package description
    * Add lintian overrides for desktop-command-not-in-package

   -- Jeremy Bícha  Fri, 29 Mar 2024 16:45:30 -0400

  gnome-software (46.0-3) unstable; urgency=medium

    * Update Homepage
    * Release to Unstable

   -- Jeremy Bícha  Thu, 28 Mar 2024 13:23:28 -0400

  gnome-software (46.0-2) experimental; urgency=medium

    * Split deb support into separate gnome-software-plugin-deb package
  (Closes: #1066030) (LP: #2019137, #2056767)
    * Have each plugin provide a virtual gnome-software-plugin package
    * Suggest all the gnome-software plugins
    * Recommend gnome-software-plugin-deb for upgrades
    * Split firmware update support into separate fwupd plugin & recommend it
  except on Ubuntu which provides a separate firmware-updater app
  Intentionally, do not have this provides the virtual gnome-software-plugin
  since it doesn't allow browsing apps.
    * Drop patch that hides upstreams Software Sources dialog (Closes: #1060803)
    * Drop Depends: software-properties-gtk
    * Stop recommending gnome-software-plugin-snap on Ubuntu

   -- Jeremy Bícha  Wed, 27 Mar 2024 18:33:03 -0400

  Build Logs
  --
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15898505/+listing-archive-extra

  Desktop Flavors Affected
  
  GNOME Software is currently included in the default install for only
  Ubuntu Cinnamon. See Joshua's comment below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2056767/+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 2064569] [NEW] The shortcut for "Increment number at cursor" not works in gnome-text-editor

[Cristiano Fraga G. Nunes]

Public bug reported:

The shortcut for "Increment number at cursor" (Shift+Ctrl+A) not works
in gnome-text-editor on Ubuntu 24.04.

Note: The shortcut for "Decrement number at cursor" (Shift+Ctrl+X) works
well.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-text-editor 46.1-1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.498
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Thu May  2 06:33:33 2024
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-text-editor
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy noble

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

Title:
  The shortcut for "Increment number at cursor" not works in gnome-text-
  editor

Status in gnome-text-editor package in Ubuntu:
  New

Bug description:
  The shortcut for "Increment number at cursor" (Shift+Ctrl+A) not works
  in gnome-text-editor on Ubuntu 24.04.

  Note: The shortcut for "Decrement number at cursor" (Shift+Ctrl+X)
  works well.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-text-editor 46.1-1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.498
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 06:33:33 2024
  LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2064569/+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 2064568] [NEW] can't set picture as desktop wallpaper in nautilus

[Erald Bardhi]

Public bug reported:

When right-clicking a picture in nautilus, and then clicking on the 'Set
as Background...' option from the menu, it doesn't do anything. The
wallpaper can be changed from the image viewer though.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May  2 09:01:15 2024
GsettingsChanges:
 
InstallationDate: Installed on 2024-05-01 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


** Tags: amd64 apport-bug noble

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

Title:
  can't set picture as desktop wallpaper in nautilus

Status in nautilus package in Ubuntu:
  New

Bug description:
  When right-clicking a picture in nautilus, and then clicking on the
  'Set as Background...' option from the menu, it doesn't do anything.
  The wallpaper can be changed from the image viewer though.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 09:01:15 2024
  GsettingsChanges:
   
  InstallationDate: Installed on 2024-05-01 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064568/+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 2064096] Re: Services fail to start in noble deployed with TPM+FDE

[Christian Ehrhardt ]

Thanks for the great debug work so far already, I think it is "apparmor
or kernel" enough that we should add those packages and subscribe a few
folks we know dealing with those details - I'd start with jjohansen as
he'd be the best to map us to either knowledge or a known case.

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

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

Title:
  Services fail to start in noble deployed with TPM+FDE

Status in apparmor package in Ubuntu:
  New
Status in cups package in Ubuntu:
  Confirmed
Status in rsyslog package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  What's known so far:
  - 24.04 desktop deployed with TPM+FDE shows this bug
  - services confined with apparmor that need to access something in 
/run/systemd (like the notify socket) fail to do so, even if the apparmor 
profile is in complain mode. And the apparmor profile does already have rules 
to allow that access
  - only after running aa-disable  can the service start fine
  - paths logged by the apparmor DENIED or ALLOWED messages are missing the 
"/run" prefix from "/run/systemd/..".
  - When we add rules to the profile using "/systemd/" (i.e., also dropping 
the /run prefix), then it works
  - other access in /run/systemd/ are also blocked, but the most noticeable one 
is the notify mechanism
  - comment #2 also states that azure CVM images are also impacted
  - comment #4 has instructions on how to create such a VM locally with LXD vms

  Original description follows:

  This might be related to #2064088

  The rsyslog service is continually timing out and restarting. If I use
  a service drop-in file and change the 'Type' from 'notify' to
  'simple', the service starts and appears to work normally.

  In the journal, I can see the attached apparmor errors. I can't make
  sense of them, but if it's a similar issue to #2064088, then I suspect
  apparmor is preventing the systemd notify function from alerting
  systemd that the service is up and running.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: rsyslog 8.2312.0-3ubuntu9
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 10:37:46 2024
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+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 2064566] [NEW] nautilus opens only in light mode

[Erald Bardhi]

Public bug reported:

The nautilus file manager, as well as some other system apps like the
snap store and settings, only opens in light mode, even when dark mode
is used by user, on Ubuntu 24.04 using X11 and NVIDIA driver 535.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May  2 08:38:44 2024
GsettingsChanges:

InstallationDate: Installed on 2024-05-01 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


** Tags: amd64 apport-bug noble

** Description changed:

- The nautilus file manager only opens in light mode, even when dark mode
- is used by user, on Ubuntu 24.04 using X11 and NVIDIA driver 535
+ The nautilus file manager, as well as some other system apps like the
+ snap store and settings, only opens in light mode, even when dark mode
+ is used by user, on Ubuntu 24.04 using X11 and NVIDIA driver 535.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 08:38:44 2024
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2024-05-01 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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

Title:
  nautilus opens only in light mode

Status in nautilus package in Ubuntu:
  New

Bug description:
  The nautilus file manager, as well as some other system apps like the
  snap store and settings, only opens in light mode, even when dark mode
  is used by user, on Ubuntu 24.04 using X11 and NVIDIA driver 535.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 08:38:44 2024
  GsettingsChanges:

  InstallationDate: Installed on 2024-05-01 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064566/+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 2064553] Re: Update to 125.0.3

[Nishit Majithia]

References:
  https://ubuntu.com/security/notices/USN-6747-2

Package Information:
  https://launchpad.net/ubuntu/+source/firefox/125.0.3+build1-0ubuntu0.20.04.1


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

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

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

Title:
  Update to 125.0.3

Status in firefox package in Ubuntu:
  Fix Released
Status in firefox source package in Focal:
  Fix Released

Bug description:
  https://www.mozilla.org/en-US/firefox/125.0.3/releasenotes/

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

[dreamsyntax]

After continued use of 6.8.7 and later 6.8.8, I can confirm using the
`./tas2781-2dev-on.sh 2` in my case as root regularly whenever audio goes out 
works fine.

What needs to happen at the kernel level / in a patch to resolve this?

-- 
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 2064553] [NEW] Update to 125.0.3

[Nishit Majithia]

Public bug reported:

https://www.mozilla.org/en-US/firefox/125.0.3/releasenotes/

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Assignee: Nishit Majithia (0xnishit)
 Status: New

** Affects: firefox (Ubuntu Focal)
 Importance: Undecided
 Assignee: Nishit Majithia (0xnishit)
 Status: New

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

** Changed in: firefox (Ubuntu Focal)
 Assignee: (unassigned) => Nishit Majithia (0xnishit)

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

Title:
  Update to 125.0.3

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

Bug description:
  https://www.mozilla.org/en-US/firefox/125.0.3/releasenotes/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2064553/+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 2063049] Re: Google Chrome and Chromium 124 have a transparent window on Wayland

[Daniel van Vugt]

Looks like the fix is in Chrome 124.0.6367.118

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

Title:
  Google Chrome and Chromium 124 have a transparent window on Wayland

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  chromium snap only launches with titlebar and transparent window after
  recent snap update on wayland and intel grafics.

  Adding --ozone-platform=wayland fixes the issue for me. (workaround
  from bug #1968610)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: chromium-browser 2:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Sun Apr 21 20:25:30 2024
  DiskUsage:
   FilesystemType   Size  Used Avail Use% Mounted on
   rpool/ROOT/ubuntu_gk6kaa  zfs 50G  7,7G   42G  16% /
   tmpfs tmpfs   16G  128M   16G   1% /dev/shm
   rpool/USERDATA/k1l_0tberh zfs437G  396G   42G  91% /home/k1l
  InstallationDate: Installed on 2022-03-24 (760 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   635  Done2024-04-21T00:51:33+02:00  2024-04-21T00:52:11+02:00  Snap 
"chromium" aktualisieren
  Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60 
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
  Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/2063049/+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 2063892] Re: Missing entry in context menu for « starring » an item in Nautilus 46 / Ubuntu 24.04

[Coeur Noir]

** Summary changed:

- How to « star » an item in Nautilus 46 / Ubuntu 24.04 ?
+ Missing entry in context menu for « starring » an item in Nautilus 46 / 
Ubuntu 24.04

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

Title:
  Missing entry in context menu for « starring » an item in Nautilus 46
  / Ubuntu 24.04

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Hi !

  For few months I'm getting used to « starred » items in Nautilus /
  Ubuntu 22.04.

  To my surprise I can't find how to do the same in 24.04,

  looks like the option for « starring » an element is missing in
  context menu.

  It's a default install of 24.04 hence « minimal » so maybe I'm missing
  a package ?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 27 00:45:55 2024
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1040, 667)'
  InstallationDate: Installed on 2024-04-25 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/2063892/+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 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process

[Robert Fletcher]

Also seeing the same issue on a headless server (Linode) 24.04 Ubuntu server
Installed ubuntu-desktop 

cat /etc/os-release 
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo


journalctl -xeu gnome-remote-desktop.service
Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
░░ Subject: A start job for unit gnome-remote-desktop.service has begun 
execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit gnome-remote-desktop.service has begun execution.
░░ 
░░ The job identifier is 2929.
Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has 
exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 217.

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

Title:
  gnome-remote-desktop.service: Failed to determine user credentials: No
  such process

Status in gnome-remote-desktop package in Ubuntu:
  Confirmed

Bug description:
  On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.

  The desktop does not show up though gdm3 is running.

  I see the following error messages which might indicate a dependency
  issue:

  pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 1.
  Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 2.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 3.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 4.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1756]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36

[Desktop-packages] [Bug 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)

[er453r]

I can confirm that still happens in Ubuntu 24.04 and executing

update-alternatives --set x-cursor-theme
/usr/share/icons/Adwaita/cursor.theme

fixes it,

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

Title:
  GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white
  square (missing adwaita-icon-theme-full)

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Do not think this is hardware dependent, but I'm using an HPE
  MicroServer Gen10 Plus.

  I installed the server edition of 22.04.  Post-Installation, I added
  some desktop environments.  After logging in, these are working fine.

  However on the gdm login entry and password entry screens I had no
  mouse pointer icon.  A semi-opaque white square tracked the mouse
  movements.  My reading suggested that gdm defaults to using the cursor
  icon theme provided by the adwaita-icon-theme package.  I discovered
  this theme comes in two sizes, a basic, smaller package installed
  automatically and a larger "full" package.

  $ apt list 'adwaita-icon-theme*'
  Listing... Done
  adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic]
  adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed]
  $

  The gdm mouse pointer appears and disappears with installation and
  removal of the package "adwaita-icon-theme-full".  Either gdm's
  dependencies should include the "full" package OR the appropriate
  mouse pointer icons should be moved from the full to the basic
  "adwaita-icon-theme" package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1972080/+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 2064545] [NEW] Can't enter form field for secret user key passphrase

[Daniel von Obernitz]

Public bug reported:

When you configure an openvpn network using the gnome GUI for network-
manager-openvpn and select type "Password and certificate TLS" you can't
enter into the form field for the secret key passphrase - you can click
on it, but when typing, the previously selected field is overwritten.
Via tab you also can't navigate to the field. But it is possible to use
context menu and paste something in the field.

On Ubuntu 22.04 I had no issue with that, I ran into it testing 24.04.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager-openvpn-gnome 1.10.2-4build2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May  1 23:27:31 2024
InstallationDate: Installed on 2024-04-25 (6 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/zsh
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: noble

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

Title:
  Can't enter form field for secret user key passphrase

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

Bug description:
  When you configure an openvpn network using the gnome GUI for network-
  manager-openvpn and select type "Password and certificate TLS" you
  can't enter into the form field for the secret key passphrase - you
  can click on it, but when typing, the previously selected field is
  overwritten. Via tab you also can't navigate to the field. But it is
  possible to use context menu and paste something in the field.

  On Ubuntu 22.04 I had no issue with that, I ran into it testing 24.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager-openvpn-gnome 1.10.2-4build2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  1 23:27:31 2024
  InstallationDate: Installed on 2024-04-25 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/2064545/+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 2061914] Re: libjavascriptcoregtk-4.0-18 seems to be missing on the latest build (24.04)

[Gastón Alegre Stotzer]

Ubuntu is transitioning webkit2gtk-4.0 in 24.04 LTS  thus breaking
dependencies for third parties.

For reference:
https://discourse.ubuntu.com/t/desktop-team-integration-squad-updates-monday-26th-february-2024/42754/3
https://ubuntu-archive-team.ubuntu.com/transitions/index.html1
https://ubuntu-archive-team.ubuntu.com/transitions/html/webkit2gtk-4.0.html#!good,bad,partial,unknown,!notintesting

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/webkit2gtk/+question/812403

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

Title:
  libjavascriptcoregtk-4.0-18 seems to be missing on the latest build
  (24.04)

Status in webkit2gtk package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  >lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  as a workaround downloaded from:
  
https://answers.launchpad.net/ubuntu/noble/amd64/libjavascriptcoregtk-4.0-18/2.43.3-1

  libjavascriptcoregtk-4.0-18/now 2.43.3-1 amd64 [instalado, local]
JavaScript engine library from WebKitGTK

  3) What you expected to happen

  sudo apt install libjavascriptcoregtk-4.0-18

  4) What happened instead

  missing package/not available

  EXPECTED:
   gir1.2-javascriptcoregtk-4.0: JavaScript engine library from WebKitGTK - 
GObject introspection data
  gir1.2-javascriptcoregtk-4.1: JavaScript engine library from WebKitGTK - 
GObject introspection data
  gir1.2-javascriptcoregtk-6.0: JavaScript engine library from WebKitGTK - 
GObject introspection data
  gir1.2-webkit-6.0: Web content engine library for GTK - GObject introspection 
data
   gir1.2-webkit2-4.0: Web content engine library for GTK - GObject 
introspection data
  gir1.2-webkit2-4.1: Web content engine library for GTK - GObject 
introspection data
   libjavascriptcoregtk-4.0-18: JavaScript engine library from WebKitGTK
   libjavascriptcoregtk-4.0-18-dbgsym: debug symbols for 
libjavascriptcoregtk-4.0-18
  libjavascriptcoregtk-4.0-bin: WebKitGTK JavaScript command-line interpreter 
(transitional dummy package)
   libjavascriptcoregtk-4.0-bin-dbgsym: No summary available for 
libjavascriptcoregtk-4.0-bin-dbgsym in ubuntu noble.
   libjavascriptcoregtk-4.0-dev: JavaScript engine library from WebKitGTK - 
development files
  libjavascriptcoregtk-4.1-0: JavaScript engine library from WebKitGTK
  libjavascriptcoregtk-4.1-0-dbgsym: debug symbols for 
libjavascriptcoregtk-4.1-0
  libjavascriptcoregtk-4.1-dev: JavaScript engine library from WebKitGTK - 
development files
  libjavascriptcoregtk-6.0-1: JavaScript engine library from WebKitGTK
  libjavascriptcoregtk-6.0-1-dbgsym: debug symbols for 
libjavascriptcoregtk-6.0-1
  libjavascriptcoregtk-6.0-dev: JavaScript engine library from WebKitGTK - 
development files
  libwebkit2gtk-4.0-37: Web content engine library for GTK
  libwebkit2gtk-4.0-37-dbgsym: debug symbols for libwebkit2gtk-4.0-37
  libwebkit2gtk-4.0-dev: Web content engine library for GTK - development files
  libwebkit2gtk-4.0-doc: Web content engine library for GTK - documentation
  libwebkit2gtk-4.1-0: Web content engine library for GTK
  libwebkit2gtk-4.1-0-dbgsym: debug symbols for libwebkit2gtk-4.1-0
  libwebkit2gtk-4.1-dev: Web content engine library for GTK - development files
  libwebkitgtk-6.0-4: Web content engine library for GTK
  libwebkitgtk-6.0-4-dbgsym: debug symbols for libwebkitgtk-6.0-4
  libwebkitgtk-6.0-dev: Web content engine library for GTK - development files
  webkit2gtk-driver: WebKitGTK WebDriver support
  webkit2gtk-driver-dbgsym: debug symbols for webkit2gtk-driver

  AVAILABLE:
  Built packages
   MISSING!!!
  gir1.2-javascriptcoregtk-4.1 JavaScript engine library from WebKitGTK - 
GObject introspection data
  gir1.2-javascriptcoregtk-6.0 JavaScript engine library from WebKitGTK - 
GObject introspection data
  gir1.2-webkit-6.0 Web content engine library for GTK - GObject 
introspection data
   MISSING!!!
  gir1.2-webkit2-4.1 Web content engine library for GTK - GObject 
introspection data
   MISSING!!!
   MISSING!!!
  libjavascriptcoregtk-4.0-bin WebKitGTK JavaScript command-line 
interpreter (transitional dummy package)
   MISSING!!!
  libjavascriptcoregtk-4.1-0 JavaScript engine library from WebKitGTK
  libjavascriptcoregtk-4.1-0-dbgsym debug symbols for 
libjavascriptcoregtk-4.1-0
  libjavascriptcoregtk-4.1-dev JavaScript engine library from WebKitGTK - 
development files
  libjavascriptcoregtk-6.0-1 JavaScript engine library from WebKitGTK
  libjava

[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Gabriel Simões]

OS: Ubuntu 22.04.04 LTS
$XDG_SESSION_TYPE: x11
nVidia: 535.171.04

Yep, the system has improved significantly. I haven't noticed any laggy
behavior.

Thanks, Daniel!

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  In Progress
Status in mutter source package in Mantic:
  In Progress
Status in mutter source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Run: journalctl -b0 | grep MetaSyncRing
  4. Verify the above command does NOT show "MetaSyncRing" messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
  being modified is only used with that driver.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+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 2061995] Re: ULTS 22, 24: FontConfig broken by including ".conf" file

[Peter Grandi]

After several hundred package updates over time this problem is no
longer occurring, I suspect that it was something buggy in the XML
library used by FotnConfig.

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

Title:
  ULTS 22,24: FontConfig broken by including ".conf" file

Status in Ubuntu:
  New
Status in fontconfig package in Ubuntu:
  New

Bug description:
  This happens to me on both ULTS 22 and ULKTS 24 on FotnConfig in
  somewhat different ways:

  * In ULTS 24 if there is a file '/etc/fonts/local.conf' then all fonts
  are rendered as if the font were not hinted or 'hinting' were 'false'.
  This is not noticeable if antialiasing is on, and most users default
  to antialiasing.

  * In ULTS 22 if there is a file
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' then some fonts are no longer
  found, or get rendered with rectangular shapes. I guess not many users
  customize their font settings.

  A telling example from ULTS 22:

  $  cat /etc/fonts/conf.d/10-antialias.conf
  
  
  
  

  false

  
  $  cp -p /etc/fonts/conf.d/10-antialias.conf 
$XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  This happens also with a skeleton
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' (or '/etc/fonts/local.conf')
  too:

  $  cat > $XDG_CONFIG_HOME/fontconfig/fonts.conf
  
  
  
  
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  None of these anomalies happen under ULST 20.

  My impression: symptoms vary and are weird, so probably it is
  something like a buffer overflow when reading the ".conf" files or the
  use of not-initialized memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2061995/+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 2064540] [NEW] Very laggy after latest update/upgrade

[Logan Etherton]

Public bug reported:

Last night, I performed a standard apt update/upgrade, and then
attempted to install Python 3.11 via pyenv.

When I tried to install Python 3.11, my system froze for about 10
seconds and then restarted. I tried again, and got the same result.

Since then, opening a terminal and typing anything is very, very laggy.
Switching tabs takes at least a second, moving to another directory,
typing any commands, etc, is all very slow.

I performed the apt upgrade command first. Here is the output from
/var/log/apt.

---

Start-Date: 2024-04-30  20:59:51
Commandline: apt upgrade
Requested-By: logan (1000)
Upgrade: containerd.io:amd64 (1.6.28-2, 1.6.31-1), docker-compose-plugin:amd64 
(2.25.0-1~ubuntu.22.04~jammy, 2.27.0-1~ubuntu.22.04~jammy), libpulse0:amd64 
(1:15.99.1+dfsg1-1ubuntu2.1, 1:15.99.1+dfsg1-1ubuntu2.2), coreutils:amd64 
(8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), docker-ce-cli:amd64 
(5:25.0.5-1~ubuntu.22.04~jammy, 5:26.1.1-1~ubuntu.22.04~jammy), 
openssh-client:amd64 (1:8.9p1-3ubuntu0.6, 1:8.9p1-3ubuntu0.7), apt:amd64 
(2.4.11, 2.4.12), mongodb-mongosh:amd64 (2.1.5, 2.2.5), 
google-chrome-stable:amd64 (123.0.6312.58-1, 124.0.6367.118-1), 
linux-modules-nvidia-535-6.5.0-27-generic:amd64 (6.5.0-27.28~22.04.1+1, 
6.5.0-27.28~22.04.1+2), libpulsedsp:amd64 (1:15.99.1+dfsg1-1ubuntu2.1, 
1:15.99.1+dfsg1-1ubuntu2.2), pulseaudio:amd64 (1:15.99.1+dfsg1-1ubuntu2.1, 
1:15.99.1+dfsg1-1ubuntu2.2), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), 
pulseaudio-utils:amd64 (1:15.99.1+dfsg1-1ubuntu2.1, 
1:15.99.1+dfsg1-1ubuntu2.2), libmutter-10-0:amd64 (42.9-0ubuntu5, 
42.9-0ubuntu7), linux-objects-nvidia-535-6.5.0-27
 -generic:amd64 (6.5.0-27.28~22.04.1+1, 6.5.0-27.28~22.04.1+2), 
firmware-sof-signed:amd64 (2.0-1ubuntu4.5, 2.0-1ubuntu4.7), 
tracker-miner-fs:amd64 (3.3.3-0ubuntu0.20.04.2, 3.3.3-0ubuntu0.20.04.3), 
libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), 
libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), 
mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), docker-buildx-plugin:amd64 
(0.13.1-1~ubuntu.22.04~jammy, 0.14.0-1~ubuntu.22.04~jammy), libruby3.0:amd64 
(3.0.2-7ubuntu2.4, 3.0.2-7ubuntu2.5), docker-ce:amd64 
(5:25.0.5-1~ubuntu.22.04~jammy, 5:26.1.1-1~ubuntu.22.04~jammy), 
libpulse-mainloop-glib0:amd64 (1:15.99.1+dfsg1-1ubuntu2.1, 
1:15.99.1+dfsg1-1ubuntu2.2), ubuntu-pro-client-l10n:amd64 (31.2~22.04, 
31.2.2~22.04), update-notifier:amd64 (3.192.54.6, 3.192.54.8), 
gir1.2-mutter-10:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
docker-ce-rootless-extras:amd64 (5:25.0.5-1~ubuntu.22.04~jammy, 
5:26.1.1-1~ubuntu.22.04~jammy), snapd:amd64 (2.58+22.04.1, 2.61.3
 +22.04), linux-signatures-nvidia-6.5.0-27-generic:amd64 
(6.5.0-27.28~22.04.1+1, 6.5.0-27.28~22.04.1+2), tracker-extract:amd64 
(3.3.3-0ubuntu0.20.04.2, 3.3.3-0ubuntu0.20.04.3), 
pulseaudio-module-bluetooth:amd64 (1:15.99.1+dfsg1-1ubuntu2.1, 
1:15.99.1+dfsg1-1ubuntu2.2), ruby3.0:amd64 (3.0.2-7ubuntu2.4, 
3.0.2-7ubuntu2.5), openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.6, 
1:8.9p1-3ubuntu0.7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
ubuntu-advantage-tools:amd64 (31.2~22.04, 31.2.2~22.04), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8), ubuntu-pro-client:amd64 
(31.2~22.04, 31.2.2~22.04)
End-Date: 2024-04-30  21:00:22

--

I think realized I was missing some pyenv dependencies, so I installed
them before trying to install Python 3.11 again, although I experienced
the same issue (froze, hard reset). Here are the details of that:

Start-Date: 2024-04-30  21:17:58
Commandline: apt install build-essential libssl-dev zlib1g-dev libbz2-dev 
libreadline-dev libsqlite3-dev curl libncursesw5-dev xz-utils tk-dev 
libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev
Requested-By: logan (1000)
Install: libidn2-dev:amd64 (2.3.2-2build1, automatic), 
libalgorithm-merge-perl:amd64 (0.08-3, automatic), g++-11:amd64 
(11.4.0-1ubuntu1~22.04, automatic), build-essential:amd64 (12.9ubuntu3), 
libfreetype6-dev:amd64 (2.11.1+dfsg-1ubuntu0.2, automatic), xtrans-dev:amd64 
(1.4.0-1, automatic), g++:amd64 (4:11.2.0-1ubuntu1, automatic), 
libxrender-dev:amd64 (1:0.9.10-1build4, automatic), libxml2-dev:amd64 
(2.9.13+dfsg-1ubuntu0.4), libfontconfig1-dev:amd64 (2.13.1-4.2ubuntu5, 
automatic), libbz2-dev:amd64 (1.0.8-5build1), libxcb1-dev:amd64 (1.14-3ubuntu3, 
automatic), libxss-dev:amd64 (1:1.2.3-1build2, automatic), 
libgnutls28-dev:amd64 (3.7.3-4ubuntu1.5, automatic), 
libalgorithm-diff-perl:amd64 (1.201-1, automatic), libncursesw5-dev:amd64 
(6.3-2ubuntu0.1), libfakeroot:amd64 (1.28-1ubuntu1, automatic), 
libgmpxx4ldbl:amd64 (2:6.2.1+dfsg-3ubuntu1, automatic), libreadline-dev:amd64 
(8.1.2-1), libpng-dev:amd64 (1.6.37-3build5, automatic), 
libxmlsec1-gnutls:amd64 (1.2.33-1build2, automatic), libnsp
 r4-dev:amd64 (2:4.35-0ubuntu0.22.04.1, automatic), libxau-dev:amd64 
(1:1.0.9-1build5, automatic), libfontconfig-dev:amd64 (2.13.1-4.2ubuntu5, 
automatic), libxmlsec

[Desktop-packages] [Bug 2038761] Re: gnome-disk-utility does not give size of nvme disk

[corrado venturini]

On Ubuntu 24.04 problem seems solved

** Attachment added: "Screenshot from 2024-05-01 21-01-41.png"
   
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2038761/+attachment/5773753/+files/Screenshot%20from%202024-05-01%2021-01-41.png

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

Title:
  gnome-disk-utility does not give size of nvme disk

Status in udisks:
  New
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  Mantic gnome-disk-utility: 45.0-1ubuntu1 Size of nvme disk is blank while in 
Jammy 42.0-1ubuntu1 gives correct size.
  see attached image

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-disk-utility 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 17:16:12 2023
  InstallationDate: Installed on 2023-10-07 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231005)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/2038761/+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 2063476] Re: Xilinx: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2

[Niran]

Hi,
Is there any temporary fix for utilizing gnome-control-center?
This bug has been preventing my from accessing my settings for the last week.
Any suggestions/workaround until the bug gets fixed is appreciated

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

Title:
  Xilinx: libwebkit2gtk-4.0.so.37: undefined symbol:
  gbm_bo_create_with_modifiers2

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

Bug description:
  Cannot run gnome-control-center due to missing symbol lookup.

  Please see the output of the console:
  ```
  ubuntu@kria:~$ gnome-control-center -h
  gnome-control-center: symbol lookup error: 
/lib/aarch64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: 
gbm_bo_create_with_modifiers2
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8
  ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136
  Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: config-disk (/dev/mmcblk1p1)
  Date: Thu Apr 25 16:57:26 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Gerhard Radatz]

OS: Ubuntu 22.04.04 LTS
$XDG_SESSION_TYPE: x11
nVidia: 535.171.04


This fix also solves an annoying flickering issue with IntelliJ Idea

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  In Progress
Status in mutter source package in Mantic:
  In Progress
Status in mutter source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Run: journalctl -b0 | grep MetaSyncRing
  4. Verify the above command does NOT show "MetaSyncRing" messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
  being modified is only used with that driver.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+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 2064535] [NEW] jammy update from 23.0.4 to 23.2.1 dropped transitional packages

[dann frazier]

Public bug reported:

I happened to notice that the bump from 23.0.4 to 23.2.1 in jammy
included a change that dropped a number of transitional packages:

mesa (23.1.4-1) unstable; urgency=medium

  [ Diederik de Haas ]
  * Drop transitional libegl1-mesa package (Closes: #1032712)
  * Drop transitional libgles2-mesa package (Closes: #1032718)
  * Drop transitional libwayland-egl1-mesa package (Closes: #1032737)
  * Drop transitional libgl1-mesa-glx package (Closes: #1032738)
  * d/README.source: Update git repo location to Salsa


Since I did not see that discussed in the SRU bug 2037604, I thought I'd call 
attention to it. No objection to this being closed as Won't Fix.

I don't think this impacts any supported upgrade paths - focal GA'd w/
20.0.4-2ubuntu1 which seems to have already had these transitional
packages in place. This is presumably a practical regression for someone
upgrading an old bionic install straight to jammy but that, of course,
is not supported.

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

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

Title:
  jammy update from 23.0.4 to 23.2.1 dropped transitional packages

Status in mesa package in Ubuntu:
  New

Bug description:
  I happened to notice that the bump from 23.0.4 to 23.2.1 in jammy
  included a change that dropped a number of transitional packages:

  mesa (23.1.4-1) unstable; urgency=medium

[ Diederik de Haas ]
* Drop transitional libegl1-mesa package (Closes: #1032712)
* Drop transitional libgles2-mesa package (Closes: #1032718)
* Drop transitional libwayland-egl1-mesa package (Closes: #1032737)
* Drop transitional libgl1-mesa-glx package (Closes: #1032738)
* d/README.source: Update git repo location to Salsa

  
  Since I did not see that discussed in the SRU bug 2037604, I thought I'd call 
attention to it. No objection to this being closed as Won't Fix.

  I don't think this impacts any supported upgrade paths - focal GA'd w/
  20.0.4-2ubuntu1 which seems to have already had these transitional
  packages in place. This is presumably a practical regression for
  someone upgrading an old bionic install straight to jammy but that, of
  course, is not supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2064535/+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 2061739] Re: crash in meta_wayland_transaction_commit

[Patrice DUROUX]

Oh, great, thanks!
So I was not alone in this wrong multiverse :-)

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

Title:
  crash in meta_wayland_transaction_commit

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  The system is Ubuntu Noble with a regular daily updates.
  This happens many times since few days ago but not clear
  at all how to reproduce it.

  Regards,
  Patrice

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Apr 16 09:26:16 2024
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-05-24 (1789 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu6
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to noble on 2019-05-28 (1785 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2061739/+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 2059756] Re: [SRU] adsys 0.14.1

[Robie Basak]

Currently the version of adsys in Mantic is 0.13.1ubuntu0.1, which is
lower than the version in Jammy Unapproved. What's your plan for Mantic
and/or users upgrading to Mantic please?

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

Title:
  [SRU] adsys 0.14.1

Status in adsys package in Ubuntu:
  Fix Released
Status in golang-1.22 package in Ubuntu:
  Fix Released
Status in adsys source package in Jammy:
  Confirmed
Status in golang-1.22 source package in Jammy:
  Confirmed
Status in adsys source package in Mantic:
  Confirmed
Status in golang-1.22 source package in Mantic:
  Confirmed

Bug description:
  [context]
  ADSys is a tool designed for administering and implementing Group Policy 
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of 
services and commands that empower administrators to efficiently manage policy 
updates and maintain compliance with organizational business rules.

  Given that ADSys directly interfaces with Active Directory and needs
  to align with new business requirements in LTS releases, it has been
  essential to keep the package consistently updated with the latest
  changes of ADSys upstream source. As ADSys is a key component of our
  commercial offerings, our customers anticipate the availability of
  recently implemented features in the 22.04 release.

  Now that ADSys has a complete set of features, the request is to
  proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note
  that any new features introduced in subsequent versions will be
  exclusively available in 24.04 and later releases.

  This version includes a comprehensive end to end automated test suite
  that runs ADSys against a real Active directory environment.

  Version 0.14.1 is available for 22.04 in a PPA
  (https://launchpad.net/~ubuntu-enterprise-
  desktop/+archive/ubuntu/adsys) and already used in production by
  customers.

  At this time of writing the number of open issues is 1 in Launchpad
  and 16 in GitHub including 6 enhancements. None of them have a high or
  critical importance.

  [references]
  LP: https://launchpad.net/ubuntu/+source/adsys
  LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
  GitHub: https://github.com/ubuntu/adsys/
  GH Bugs: https://github.com/ubuntu/adsys/issues
  Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/
  Initial SRU discussion: 
https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html

  [changes]
  Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog
   * New features
     * New policies:
   - Add mount / network shares policy manager
   - Add AppArmor policy manager
   - Support multiple AD backends and implement Winbind support
   - Add system proxy policy manager
   - Add certificate policy manager for machines
   - Add adsysctl policy purge command to purge applied policies
   - Full documentation
   - Full end to end automated test suite.

   * Enhancements
    * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
    * Expose Ubuntu Pro status in the "status" command
    * Update scripts manager creation
    * List Pro policy types in service status output
    * Warn when Pro-only rules are configured
    * Use systemd via D-Bus instead of systemctl commands
    * Add placeholder notes for entry types
    * Rework Kerberos ticket handling logic to satisfy the Heimdal 
implementation of Kerberos
    * Rework policy application sync strategy
    * Print logs when policies are up to date
    * Update policy definitions to include dconf key for dark mode background
    * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
    * Allow sssd backend to work without ad_domain being set (LP: #2054445)
    * Update apport hook to include journal errors and package logs

   * Bug fixes
    * Fix policy update failing when GPT.INI contains no version key
    * Fix object lookup for users having a FQDN as their hostname
    * Support special characters in domains when parsing sssd configuration
    * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
    * Ensure empty state for dconf policy
    * Handle case mismatches in GPT.INI file name
    * Ensure GPO URLs contain the FQDN of the domain controller
    * Add runtime dependency on nfs-common

   * Other
    * Updates to latest versions of Go (fixing known Go vulnerabilities)
    * Updates to latest versions of the Go dependencies
    * Updates and improvements to CI and QoL
    * Migrate translation support to native approach using go-i18n + gotext and 
switch to upstream gotext version

  Dependencies:
  * Build-dep: golang-go (>= 2:1.22~)

  * Dependencies to backport to 22.04:
    * golang-go >= 2:1.22
    * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will 

[Desktop-packages] [Bug 2064370] Re: Blank screen after boot in raspberry pi 4

[Andreas Hasenack]

** Package changed: software-properties (Ubuntu) => linux-raspi (Ubuntu)

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

Title:
  Blank screen after boot in raspberry pi 4

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  
  I just flashed noble arm64+raspi image and booted it in my raspberry pi 4, 
and after initial rainbow screen kernel boots with 4 raspberries on the top and 
boot text appears as normal. But then, before it finishes booting, the screen 
goes blank.

  Image is ubuntu-24.04-preinstalled-server-arm64+raspi.img.xz
  downloaded at Apr/30.

  ubuntu@ubuntu:~$ uname -a
  Linux ubuntu 6.8.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 
02:29:55 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  I know the system booted because I can access it over the network and
  I even plugged a usb-serial adapter in the uart GPIOs and from there I
  can see the boot does progress to completion and offers me a prompt
  where I can use the system normally. But the HDMI screen stays blank.

  The funny thing is that I have been trying daily builds for quite some
  time now and they used to work well, this is the first one that does
  this (the official release).

  After testing some config options I found that if I change
  "dtoverlay=vc4-kms-v3d" for "dtoverlay=vc4-fkms-v3d" in config.txt
  then it boots ok and the screen stays on (note the change from kms to
  fkms).

  I also tried appending ",cma-128" to that line (it is present on other
  lines -- like for pi3 and pi0 -- but not on this one), it does not
  help.

  I don't think the issue is with my monitor since it works well for a
  long time. Also I checked EDIDs, they are detected when using fkms but
  they are blank when using kms:

  With KMS:
  ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid 
  EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty.

  With fKMS:
  ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid 
  edid-decode (hex):

  00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00
  01 1a 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24
  ..
  (supressed)

  I do not use a graphical environment on this unit so I don't know the
  consequences of this change (to me it just fixes the issue, but I
  guess it was there for a reason).

  Let me know if you need any other information from the environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+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 2056758] Re: ubuntu-bug doesn't let me file bugs for Snap thunderbird

[Helga]

Filing a bug with `ubuntu-bug thunderbird` now works for me on apport
(2.28.1-0ubuntu3).

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

Title:
  ubuntu-bug doesn't let me file bugs for Snap thunderbird

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid
Status in apport source package in Noble:
  Fix Committed

Bug description:
  I'm trying to report a bug in the new Snap for Thunderbird.

  When I run "ubuntu-bug thunderbird", it:
  * Collects information correctly after I input the sudo password
  * Opens a page like 
https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?,
 which does not seem to be valid.

  This is not the case for Firefox, which works fine with ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 
14:47:27.874792575 
+0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash
   640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 
17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash
  CurrentDesktop: KDE
  Date: Mon Mar 11 16:54:18 2024
  InstallationDate: Installed on 2022-08-29 (560 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2056758/+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 2064354] Re: File manager crashes on run

[Elijah Reed]

I couldn't upload the file either so here is the gdb log:
GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from nautilus...

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Downloading separate debug info for /usr/bin/nautilus...
Reading symbols from 
/home/techlover112/.cache/debuginfod_client/b8e657e15ab34018861f9fe42870ca0bf01d9449/debuginfo...
(gdb) handle SIG33 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/nautilus 
Downloading separate debug info for system-supplied DSO at 0x7ffd675ea000...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libnautilus-extension.so.4...
Downloading separate debug info for /lib/x86_64-linux-gnu/libglib-2.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libglib-2.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgtk-4.so.1...
Downloading separate debug info for /lib/x86_64-linux-gnu/libpango-1.0.so.0...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libcairo.so.2...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libgraphene-1.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgio-2.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgobject-2.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libadwaita-1.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgmodule-2.0.so.0...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libgnome-autoar-0.so.0...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libgnome-desktop-4.so.2...
Downloading separate debug info for /lib/x86_64-linux-gnu/libportal.so.1...
Downloading separate debug info for /lib/x86_64-linux-gnu/libportal-gtk4.so.1...
Downloading separate debug info for /lib/x86_64-linux-gnu/libselinux.so.1...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libtracker-sparql-3.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libunity.so.9...
Downloading separate debug info for /lib/x86_64-linux-gnu/libunity.so.9...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Downloading separate debug info for /lib/x86_64-linux-gnu/libpcre2-8.so.0...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libharfbuzz.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libfribidi.so.0...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libcairo-gobject.so.2...
Downloading separate debug info for /lib/x86_64-linux-gnu/libfontconfig.so.1...
Downloading separate debug info for /lib/x86_64-linux-gnu/libepoxy.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libXi.so.6...
Downloading separate debug info for /lib/x86_64-linux-gnu/libX11.so.6...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libvulkan.so.1...
Downloading separate debug info for /lib/x86_64-linux-gnu/libpng16.so.16...
Downloading separate debug info for /lib/x86_64-linux-gnu/libtiff.so.6...
Downloading separate debug info for /lib/x86_64-linux-gnu/libjpeg.so.8...
Downloading separate debug info for /lib/x86_64-linux-gnu/libxkbcommon.so.0...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libwayland-client.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libwayland-egl.so.1...
Downloading separate debug info for /lib/x86_64-linux-gnu/libXext.so.6...
Downloading separate debug info for /lib/x86_64-linux-gnu/libXcursor.so.1...
Downloading separate debu

[Desktop-packages] [Bug 2064364] Re: gnome-control-center: WireGuard peer info closes on focus loss.

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => New

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

Title:
  gnome-control-center: WireGuard peer info closes on focus loss.

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

Bug description:
  Just installed a fresh Ubuntu 24.04 LTS

  In Settings (gnome-control-center) -> Network -> VPN '+'-> WireGuard
  -> WireGuard -> Peers '+'.

  When adding a peer for the Wireguard connection, if the popout or
  window loses focus (for example because we need do copy-paste from
  another window), the entire "peer" dialog closes and we lose the
  previous info.

  It's not reasonable to setup a WireGuard connection manually because
  typing several long keys by hand is too error prone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/2064364/+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 2064099] Re: Quickly switching right and left clicks freezes Nautilus

[Khalid Abu Shawarib]

upstream: https://gitlab.gnome.org/GNOME/gtk/-/issues/6465

(It's not yet clear if it's a GTK or a compositor issue)

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

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

Title:
  Quickly switching right and left clicks freezes Nautilus

Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  1. Open Nautilus.
  2. Try to right click and left click randomly and quickly.

  This behavior will freeze Nautilus until you must kill it and it
  happens every time you do this, and you cannot even move it's window.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 12:42:46 2024
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
  InstallationDate: Installed on 2024-03-22 (38 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago)
  usr_lib_nautilus:
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064099/+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 2064364] Re: gnome-control-center: WireGuard peer info closes on focus loss.

[Sebastien Bacher]

Thanks for the upstream reference!

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

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

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2437
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-control-center: WireGuard peer info closes on focus loss.

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

Bug description:
  Just installed a fresh Ubuntu 24.04 LTS

  In Settings (gnome-control-center) -> Network -> VPN '+'-> WireGuard
  -> WireGuard -> Peers '+'.

  When adding a peer for the Wireguard connection, if the popout or
  window loses focus (for example because we need do copy-paste from
  another window), the entire "peer" dialog closes and we lose the
  previous info.

  It's not reasonable to setup a WireGuard connection manually because
  typing several long keys by hand is too error prone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/2064364/+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 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected

[Chris Chiu]

@trurl42, seems you have different machine which I will need alsa-info
and dmesg for your config. Could you file another bug and attached the
detail information as comment #1.

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

Title:
  [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all
  despite the sound bars moving fine and device detected

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  The volume bars in sound settings react to what sound is played
  correctly but I can't hear any sounds

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paramvir   1924 F pulseaudio
   /dev/snd/pcmC0D0p:   paramvir   1924 F...m pulseaudio
   /dev/snd/pcmC0D6c:   paramvir   1924 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  5 02:22:25 2020
  InstallationDate: Installed on 2020-04-26 (161 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paramvir   1924 F pulseaudio
   /dev/snd/pcmC0D0p:   paramvir   1924 F...m pulseaudio
   /dev/snd/pcmC0D6c:   paramvir   1924 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0K1VDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7591
  dmi.product.sku: 0923
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+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 2064354] Re: File manager crashes on run

[Dominik]

> nautilus is the filemanager, it's not used to select files in other
applications (that's the fileselector widget from GTK)

Thanks, this confirms other applications are affected as well. Following
the other bug you linked, I can confirm that (at least) GNOME settings
and the system monitor are affected as well.

I wonder why 535 was the most recent driver offered by "Software &
Updates -> Additional Drivers". Anyway, switching to the nvidia 550
driver seems to resolve this issue for me fully.

Thank you!

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

Title:
  File manager crashes on run

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I 
obtained the following from the command prompt: 
  $ nautilus
  ** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files
  libEGL warning: egl: failed to create dri2 screen
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 16:15:29 2024
  GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
  InstallationDate: Installed on 2024-04-24 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064354/+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 2064364] Re: gnome-control-center: WireGuard peer info closes on focus loss.

[wontfix]

Bug is upstream here https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues/2437

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2437
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2437

** Tags added: noble vpn wireguard

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

Title:
  gnome-control-center: WireGuard peer info closes on focus loss.

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

Bug description:
  Just installed a fresh Ubuntu 24.04 LTS

  In Settings (gnome-control-center) -> Network -> VPN '+'-> WireGuard
  -> WireGuard -> Peers '+'.

  When adding a peer for the Wireguard connection, if the popout or
  window loses focus (for example because we need do copy-paste from
  another window), the entire "peer" dialog closes and we lose the
  previous info.

  It's not reasonable to setup a WireGuard connection manually because
  typing several long keys by hand is too error prone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064364/+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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Gabriel Simões]

Hey guys... hey Daniel,

Do you guys know when the fix will officially be available for 22.4.04
LTS? Is it expected in the next few days or weeks, or will it take a
long time to happen?

Thanks a lot!

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  In Progress
Status in mutter source package in Mantic:
  In Progress
Status in mutter source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Run: journalctl -b0 | grep MetaSyncRing
  4. Verify the above command does NOT show "MetaSyncRing" messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
  being modified is only used with that driver.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+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 2064364] Re: gnome-control-center: WireGuard peer info closes on focus loss.

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-control-center: WireGuard peer info closes on focus loss.

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

Bug description:
  Just installed a fresh Ubuntu 24.04 LTS

  In Settings (gnome-control-center) -> Network -> VPN '+'-> WireGuard
  -> WireGuard -> Peers '+'.

  When adding a peer for the Wireguard connection, if the popout or
  window loses focus (for example because we need do copy-paste from
  another window), the entire "peer" dialog closes and we lose the
  previous info.

  It's not reasonable to setup a WireGuard connection manually because
  typing several long keys by hand is too error prone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064364/+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 2064364] Re: gnome-control-center: wireguard pair closes when loosing focus

[wontfix]

** Description changed:

  Just installed a fresh Ubuntu 24.04 LTS
  
- In gnome-control-center -> Network -> VPN -> + -> Wireguard -> Pairs
- -> +
+ In Settings (gnome-control-center) -> Network -> VPN '+'-> WireGuard ->
+ WireGuard -> Peers '+'.
  
- When adding a pair for the Wireguard connection, if the window looses
- focus (for example because we need do copy-paste from another window),
- the entire "pair" dialog closes and we loose as the info previously
- entered.
+ When adding a peer for the Wireguard connection, if the popout or window
+ loses focus (for example because we need do copy-paste from another
+ window), the entire "peer" dialog closes and we lose the previous info.
  
- As it is, it's almost not humanly possible to setup a wireguard
- connection manually because typing several long keys by hand is too
- error prone.
+ It's not reasonable to setup a WireGuard connection manually because
+ typing several long keys by hand is too error prone.

** Summary changed:

- gnome-control-center: wireguard pair closes when loosing focus
+ gnome-control-center: WireGuard peer info closes on focus loss.

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

Title:
  gnome-control-center: WireGuard peer info closes on focus loss.

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

Bug description:
  Just installed a fresh Ubuntu 24.04 LTS

  In Settings (gnome-control-center) -> Network -> VPN '+'-> WireGuard
  -> WireGuard -> Peers '+'.

  When adding a peer for the Wireguard connection, if the popout or
  window loses focus (for example because we need do copy-paste from
  another window), the entire "peer" dialog closes and we lose the
  previous info.

  It's not reasonable to setup a WireGuard connection manually because
  typing several long keys by hand is too error prone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064364/+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 2064354] Re: File manager crashes on run

[Sebastien Bacher]

@Dominik

> nautilus cannot be started to pick a file in Firefox

nautilus is the filemanager, it's not used to select files in other
applications (that's the fileselector widget from GTK)

also you manage to get a backtrace from nautilus it seems?

>From what you copied the crash is in

 #5 0x7ba570201e0d in ProducerCleanup () from /lib/x86_64-linux-
gnu/libnvidia-vulkan-producer.so

which means the nvidia 535 driver, which sounds similar to bug #2063827.
Could you try if switching to 550 driver fixes the issue for you?

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

Title:
  File manager crashes on run

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I 
obtained the following from the command prompt: 
  $ nautilus
  ** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files
  libEGL warning: egl: failed to create dri2 screen
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 16:15:29 2024
  GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
  InstallationDate: Installed on 2024-04-24 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064354/+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 2064096] Re: Services fail to start in noble deployed with TPM+FDE

[Andreas Hasenack]

** Description changed:

+ What's known so far:
+ - 24.04 desktop deployed with TPM+FDE shows this bug
+ - services confined with apparmor that need to access something in 
/run/systemd (like the notify socket) fail to do so, even if the apparmor 
profile is in complain mode
+ - only after running aa-disable  can the service start fine
+ - paths logged by the apparmor DENIED or ALLOWED messages are missing the 
"/run" prefix from "/run/systemd/.."
+ - other access in /run/systemd/ are also blocked, but the most noticeable one 
is the notify mechanism
+ - comment #2 also states that azure CVM images are also impacted
+ 
+ 
+ Original description follows:
+ 
  This might be related to #2064088
  
  The rsyslog service is continually timing out and restarting. If I use a
  service drop-in file and change the 'Type' from 'notify' to 'simple',
  the service starts and appears to work normally.
  
  In the journal, I can see the attached apparmor errors. I can't make
  sense of them, but if it's a similar issue to #2064088, then I suspect
  apparmor is preventing the systemd notify function from alerting systemd
  that the service is up and running.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: rsyslog 8.2312.0-3ubuntu9
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 10:37:46 2024
  ProcEnviron:
-  LANG=en_GB.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  What's known so far:
  - 24.04 desktop deployed with TPM+FDE shows this bug
  - services confined with apparmor that need to access something in 
/run/systemd (like the notify socket) fail to do so, even if the apparmor 
profile is in complain mode
  - only after running aa-disable  can the service start fine
  - paths logged by the apparmor DENIED or ALLOWED messages are missing the 
"/run" prefix from "/run/systemd/.."
  - other access in /run/systemd/ are also blocked, but the most noticeable one 
is the notify mechanism
  - comment #2 also states that azure CVM images are also impacted
- 
+ - comment #4 has instructions on how to create such a VM locally with LXD vms
  
  Original description follows:
  
  This might be related to #2064088
  
  The rsyslog service is continually timing out and restarting. If I use a
  service drop-in file and change the 'Type' from 'notify' to 'simple',
  the service starts and appears to work normally.
  
  In the journal, I can see the attached apparmor errors. I can't make
  sense of them, but if it's a similar issue to #2064088, then I suspect
  apparmor is preventing the systemd notify function from alerting systemd
  that the service is up and running.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: rsyslog 8.2312.0-3ubuntu9
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 10:37:46 2024
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  What's known so far:
  - 24.04 desktop deployed with TPM+FDE shows this bug
- - services confined with apparmor that need to access something in 
/run/systemd (like the notify socket) fail to do so, even if the apparmor 
profile is in complain mode
+ - services confined with apparmor that need to access something in 
/run/systemd (like the notify socket) fail to do so, even if the apparmor 
profile is in complain mode. And the apparmor profile does already have rules 
to allow that access
  - only after running aa-disable  can the service start fine
- - paths logged by the apparmor DENIED or ALLOWED messages are missing the 
"/run" prefix from "/run/systemd/.."
+ - paths logged by the apparmor DENIED or ALLOWED messages are missing the 
"/run" prefix from "/run/systemd/..". When we add rules to the profile 
using "/systemd/" (i.e., also dropping the /run prefix), then it works
  - other access in /run/systemd/ are also blocked, but the most noticeable one 
is the notify mechanism
  - comment #2 also states that azure CVM images are also impacted
  - comment #4 has instructions on how to create such a VM locally with LXD vms
  
  Original description follows:
  
  This might be related to #2064088
  
  The rsyslog service is cont

[Desktop-packages] [Bug 2064096] Re: rsyslog service timeout on noble numbat

[Andreas Hasenack]

I think neither rsyslog, nor cups, or sssd, are the correct packages for
this bug, but I agree that spreading out the investigation over two
different bugs is not good.

I'll mark https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088 as
a duplicate, and add cups and sssd tasks to this one for tracking
purposes, but I suspect the fix will be elsewhere in the end.

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

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

** Summary changed:

- rsyslog service timeout on noble numbat
+ Services fail to start in noble deployed with TPM+FDE

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

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

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

Title:
  Services fail to start in noble deployed with TPM+FDE

Status in cups package in Ubuntu:
  Confirmed
Status in rsyslog package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  What's known so far:
  - 24.04 desktop deployed with TPM+FDE shows this bug
  - services confined with apparmor that need to access something in 
/run/systemd (like the notify socket) fail to do so, even if the apparmor 
profile is in complain mode. And the apparmor profile does already have rules 
to allow that access
  - only after running aa-disable  can the service start fine
  - paths logged by the apparmor DENIED or ALLOWED messages are missing the 
"/run" prefix from "/run/systemd/..".
  - When we add rules to the profile using "/systemd/" (i.e., also dropping 
the /run prefix), then it works
  - other access in /run/systemd/ are also blocked, but the most noticeable one 
is the notify mechanism
  - comment #2 also states that azure CVM images are also impacted
  - comment #4 has instructions on how to create such a VM locally with LXD vms

  Original description follows:

  This might be related to #2064088

  The rsyslog service is continually timing out and restarting. If I use
  a service drop-in file and change the 'Type' from 'notify' to
  'simple', the service starts and appears to work normally.

  In the journal, I can see the attached apparmor errors. I can't make
  sense of them, but if it's a similar issue to #2064088, then I suspect
  apparmor is preventing the systemd notify function from alerting
  systemd that the service is up and running.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: rsyslog 8.2312.0-3ubuntu9
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 10:37:46 2024
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2064096/+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 2064354] Re: File manager crashes on run

[Dominik]

It affects me as well, attaching a backtrace does not work as nautilus
cannot be started to pick a file in Firefox so I have to insert it here
in full length:

Starting program: /usr/bin/nautilus 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ba5a9e006c0 (LWP 18782)]
[New Thread 0x7ba5a94006c0 (LWP 18783)]
[New Thread 0x7ba5a8a006c0 (LWP 18784)]
[New Thread 0x7ba5a3e006c0 (LWP 18786)]
[New Thread 0x7ba5a34006c0 (LWP 18787)]
[New Thread 0x7ba5a2a006c0 (LWP 18788)]
[New Thread 0x7ba5a20006c0 (LWP 18789)]
[New Thread 0x7ba5a16006c0 (LWP 18790)]
** Message: 13:46:13.407: Connecting to org.freedesktop.Tracker3.Miner.Files
[New Thread 0x7ba5a0c006c0 (LWP 18791)]
[New Thread 0x7ba597a006c0 (LWP 18792)]
[New Thread 0x7ba5964006c0 (LWP 18806)]
[New Thread 0x7ba595a006c0 (LWP 18807)]
[New Thread 0x7ba5950006c0 (LWP 18808)]
[New Thread 0x7ba58be006c0 (LWP 18809)]
[New Thread 0x7ba58b4006c0 (LWP 18810)]
[New Thread 0x7ba58aa006c0 (LWP 18811)]
[Thread 0x7ba58aa006c0 (LWP 18811) exited]
[Thread 0x7ba58b4006c0 (LWP 18810) exited]
[Thread 0x7ba58be006c0 (LWP 18809) exited]
[Thread 0x7ba5950006c0 (LWP 18808) exited]
[Thread 0x7ba595a006c0 (LWP 18807) exited]
[Thread 0x7ba5964006c0 (LWP 18806) exited]
[Thread 0x7ba5a16006c0 (LWP 18790) exited]
[Thread 0x7ba5a20006c0 (LWP 18789) exited]
[Thread 0x7ba5a34006c0 (LWP 18787) exited]
libEGL warning: egl: failed to create dri2 screen
[New Thread 0x7ba58aa006c0 (LWP 18825)]
[New Thread 0x7ba5964006c0 (LWP 18826)]
[New Thread 0x7ba5950006c0 (LWP 18827)]
[New Thread 0x7ba58b4006c0 (LWP 18828)]
[New Thread 0x7ba595a006c0 (LWP 18829)]
[New Thread 0x7ba58be006c0 (LWP 18830)]
[New Thread 0x7ba565c006c0 (LWP 18831)]
[New Thread 0x7ba5652006c0 (LWP 18832)]
[New Thread 0x7ba5590006c0 (LWP 18833)]
[New Thread 0x7ba54fe006c0 (LWP 18834)]
[New Thread 0x7ba54f4006c0 (LWP 18835)]
[New Thread 0x7ba54ea006c0 (LWP 18836)]
[New Thread 0x7ba54e0006c0 (LWP 18837)]
[New Thread 0x7ba54d6006c0 (LWP 18839)]
[New Thread 0x7ba54cc006c0 (LWP 18841)]
[New Thread 0x7ba53be006c0 (LWP 18842)]
[New Thread 0x7ba53b4006c0 (LWP 18843)]

Thread 1 "nautilus" received signal SIGSEGV, Segmentation fault.
Download failed: Invalid argument.  Continuing without source file 
./elf/./elf/dl-close.c.
_dl_close (_map=0x0) at ./elf/dl-close.c:770
warning: 770./elf/dl-close.c: No such file or directory
(gdb) where
#0  _dl_close (_map=0x0) at ./elf/dl-close.c:770
#1  0x7ba5b0a8e51c in __GI__dl_catch_exception 
(exception=exception@entry=0x7ffea44f2e80, operate=0x7ba5b0a8f750 <_dl_close>, 
args=0x0)
at ./elf/dl-catch.c:237
#2  0x7ba5b0a8e669 in _dl_catch_error (objname=0x7ffea44f2ee8, 
errstring=0x7ffea44f2ef0, mallocedp=0x7ffea44f2ee7, 
operate=, args=) at ./elf/dl-catch.c:256
#3  0x7ba5af297c73 in _dlerror_run (operate=, 
args=) at ./dlfcn/dlerror.c:138
#4  0x7ba5af2979a6 in __dlclose (handle=) at 
./dlfcn/dlclose.c:31
#5  0x7ba570201e0d in ProducerCleanup () from 
/lib/x86_64-linux-gnu/libnvidia-vulkan-producer.so
#6  0x7ba5702020db in ProducerInit () from 
/lib/x86_64-linux-gnu/libnvidia-vulkan-producer.so
#7  0x7ba55aa1a0e2 in ?? () from 
/lib/x86_64-linux-gnu/libnvidia-glcore.so.535.171.04
#8  0x7ba55aa4442f in ?? () from 
/lib/x86_64-linux-gnu/libnvidia-glcore.so.535.171.04
#9  0x7ba55aa6844d in ?? () from 
/lib/x86_64-linux-gnu/libnvidia-glcore.so.535.171.04
#10 0x7ba5a31b1b50 in ?? () from /lib/x86_64-linux-gnu/libGLX_nvidia.so.0
#11 0x7ba5aed2a0da in terminator_CreateSwapchainKHR (device=0x64be52a66a50, 
pCreateInfo=0x64be53358d58, pAllocator=0x0, 
pSwapchain=0x64be53358d38) at 
/usr/src/vulkan-loader-1.3.275.0-1build1/loader/wsi.c:499
#12 0x7ba5668f93ac in kopper_CreateSwapchain (result=, 
h=, w=, cdt=0x64be53358710, 
screen=0x64be5282b8c0) at ../src/gallium/drivers/zink/zink_kopper.c:316
#13 update_swapchain (screen=0x64be5282b8c0, cdt=0x64be53358710, w=, h=)
at ../src/gallium/drivers/zink/zink_kopper.c:379
#14 0x7ba5668fa66a in zink_kopper_displaytarget_create 
(screen=screen@entry=0x64be5282b8c0, tex_usage=, 
format=, width=, height=, 
alignment=alignment@entry=64, loader_private=, 
stride=) at ../src/gallium/drivers/zink/zink_kopper.c:460
#15 0x7ba5668fff96 in resource_create (pscreen=0x64be5282b8c0, 
templ=0x7ffea44f3770, whandle=whandle@entry=0x0, 
modifiers=modifiers@entry=0x0, modifiers_count=modifiers_count@entry=0, 
loader_private=0x64be53351630, user_mem=, 
external_usage=0) at ../src/gallium/drivers/zink/zink_resource.c:1498
#16 0x7ba5669001bd in zink_resource_create_drawable (pscreen=, templ=, loader_private=)
at ../src/gallium/drivers/zink/zink_resource.c:1578
#17 0x7ba565eb9328 in kopper_allocate_textures (ctx=0x64be531146f0, 
drawable=, statts=, 
statts_count=) at ../src/gallium/frontends/dri/kopper.c:608
#18 0x7ba565eba876 in dri_st_framebuffer_validate (st=, 
pdrawable=, statts=0x64be533580b0, count=

[Desktop-packages] [Bug 2064485] Re: Discover crasFrequent crashes in plasma-discover with libglib-2.0 errorshes after click on apps or extension for apps or plasma extensions

[Sebastien Bacher]

Thanks but I'm deleting that file since it might include
private/sensitive information and shouldn't be attached to a public
report, please follow the instruction from the previous post to submit
it properly to the error tracker instead

** Attachment removed: "_usr_bin_plasma-discover.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2064485/+attachment/5773561/+files/_usr_bin_plasma-discover.1000.crash

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

Title:
  Discover crasFrequent crashes in plasma-discover with libglib-2.0
  errorshes after click on apps or extension for apps or plasma
  extensions

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  Description:
  I am experiencing frequent crashes with the application plasma-discover on 
Ubuntu 22.04.4 LTS. These crashes occur when I attempt to access the update 
functions within the Discover UI. Terminal outputs and system logs indicate 
issues with libglib-2.0, showing repeated trap int3 errors, which are typically 
used for debug breakpoints in development builds.

  Expected Behavior:
  Plasma Discover should run smoothly, allowing the management of software 
updates and installations without crashing.

  Actual Behavior:
  Discover crashes frequently, especially when trying to access the updates 
section or other specific parts of the application.

  Steps Attempted:

  Resetting configuration files for Discover.
  Running Discover from the terminal to capture any error outputs.
  System update and reinstallation of plasma-discover and its dependencies.
  Analyzing system logs with journalctl, which showed repeated issues with 
libglib-2.0.

  System and Package Information:

  Ubuntu Version: 22.04.4 LTS
  Package Versions:
  libglib2.0-0: Installed: 2.72.4-0ubuntu2.2
  plasma-discover: Installed: 5.24.7-0ubuntu0.1

  This issue significantly impacts the functionality of the Discover
  application, hindering routine software management and updates. Any
  assistance or resolution would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglib2.0-0 2.72.4-0ubuntu2.2
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May  1 09:58:53 2024
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2064485/+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 2058687] Re: [SRU] libreoffice 7.6.6 for mantic

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 4:7.6.6-0ubuntu0.23.10.1

---
libreoffice (4:7.6.6-0ubuntu0.23.10.1) mantic; urgency=medium

  * New upstream release (LP: #2058687)
  * debian/rules:
- also suggest libreoffice-{hyphenation,spellcheck}-tr in -l10n-tr
  and libreoffice-{hyphenation,spellcheck}-fr in -l10n-fr (as for fi)

 -- Rico Tzschichholz   Thu, 21 Mar 2024 20:20:29
+0100

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

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

Title:
  [SRU] libreoffice 7.6.6 for mantic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Mantic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release

   * Version 7.6.5 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 
(that's a total of 39 bugs):
   https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs

   7.6.6 RC3 is identical to the 7.6.6 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_76/1898/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 39 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687/+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 2058687] Update Released

[Robie Basak]

The verification of the Stable Release Update for libreoffice 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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2058687

Title:
  [SRU] libreoffice 7.6.6 for mantic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Mantic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release

   * Version 7.6.5 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 
(that's a total of 39 bugs):
   https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs

   7.6.6 RC3 is identical to the 7.6.6 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_76/1898/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 39 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687/+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 2064495] [NEW] .bash_history not working with gnome-terminal

[Major András]

Public bug reported:

I opened a gnome-terminal, I issue a command, and exit. The
"~/.bash_history"file does not contain the command issued.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-terminal 3.52.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May  1 11:50:58 2024
InstallationDate: Installed on 2024-04-28 (3 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=hu_HU.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

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

Title:
  .bash_history not working with gnome-terminal

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I opened a gnome-terminal, I issue a command, and exit. The
  "~/.bash_history"file does not contain the command issued.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-terminal 3.52.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  1 11:50:58 2024
  InstallationDate: Installed on 2024-04-28 (3 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064495/+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 1993054] Re: USB key eject does not eject

[Victor]

"I changed "this.cancellable" in lines 632 and 635 to "null" in the
locations.js file and now everything works as it should" - still works
for 24.04 (lines is 636 and 639)

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

Title:
  USB key eject does not eject

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  New
Status in gnome-shell-extension-ubuntu-dock source package in Noble:
  In Progress

Bug description:
  I insert an USB key: 
icon appear in the dock and in the nautilus sidebar with title and a small 
arrow
  right click on icon in the dock and select 'Eject':
the icon disappear in the dock but does NOT disappear from the nautilus 
sidebar  
  click on the arrow near the icon in nautilus sidebar: 
the icon disappear and I see a message in notification area with: '... USB 
flash memory ... can be removed'

  problem happens when org.gnome.shell.extensions.dash-to-dock 
show-mounts-only-mounted is set to TRUE
  the problem does not occur if show-mounts-only-mounted is set to FALSE

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell-extension-ubuntu-dock 74ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 16 09:48:16 2022
  InstallationDate: Installed on 2022-09-30 (15 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 2061739] Re: crash in meta_wayland_transaction_commit

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  crash in meta_wayland_transaction_commit

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  The system is Ubuntu Noble with a regular daily updates.
  This happens many times since few days ago but not clear
  at all how to reproduce it.

  Regards,
  Patrice

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Apr 16 09:26:16 2024
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-05-24 (1789 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu6
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to noble on 2019-05-28 (1785 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2061739/+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 2064485] Re: Discover crasFrequent crashes in plasma-discover with libglib-2.0 errorshes after click on apps or extension for apps or plasma extensions

[Paul Schumacher]

I have attached the crash file to this bug report to provide additional
information that may assist in diagnosing.


** Attachment added: "_usr_bin_plasma-discover.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2064485/+attachment/5773561/+files/_usr_bin_plasma-discover.1000.crash

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

Title:
  Discover crasFrequent crashes in plasma-discover with libglib-2.0
  errorshes after click on apps or extension for apps or plasma
  extensions

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  Description:
  I am experiencing frequent crashes with the application plasma-discover on 
Ubuntu 22.04.4 LTS. These crashes occur when I attempt to access the update 
functions within the Discover UI. Terminal outputs and system logs indicate 
issues with libglib-2.0, showing repeated trap int3 errors, which are typically 
used for debug breakpoints in development builds.

  Expected Behavior:
  Plasma Discover should run smoothly, allowing the management of software 
updates and installations without crashing.

  Actual Behavior:
  Discover crashes frequently, especially when trying to access the updates 
section or other specific parts of the application.

  Steps Attempted:

  Resetting configuration files for Discover.
  Running Discover from the terminal to capture any error outputs.
  System update and reinstallation of plasma-discover and its dependencies.
  Analyzing system logs with journalctl, which showed repeated issues with 
libglib-2.0.

  System and Package Information:

  Ubuntu Version: 22.04.4 LTS
  Package Versions:
  libglib2.0-0: Installed: 2.72.4-0ubuntu2.2
  plasma-discover: Installed: 5.24.7-0ubuntu0.1

  This issue significantly impacts the functionality of the Discover
  application, hindering routine software management and updates. Any
  assistance or resolution would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglib2.0-0 2.72.4-0ubuntu2.2
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May  1 09:58:53 2024
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2064485/+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 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]

[Daniel van Vugt]

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

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4
  [drmModeAtomicCommit: Invalid argument]

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble wayland-session
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064275/+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 2064485] Re: Discover crasFrequent crashes in plasma-discover with libglib-2.0 errorshes after click on apps or extension for apps or plasma extensions

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. However, your crash report is either missing or challenging to deal 
with as a '.crash' file. Please follow these instructions to have apport report 
a new bug about your crash that can be dealt with by the automatic retracer. 
 
 If you are running the Ubuntu Stable Release you might need to enable apport 
in /etc/default/apport and restart. 
 
 If you are using Ubuntu with the Gnome desktop environment - launch nautilus 
and navigate to your /var/crash directory and double click on the crash report 
you wish to submit. 
 
 If you are using Kubuntu or Xubuntu you can file the crash using 
/usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a 
terminal - where _my_crash_report.crash is the crash you would like to report. 
 I'm closing this bug report since the process outlined above will 
automatically open a new bug report which can then dealt with more efficiently. 
Thanks in advance for your cooperation and understanding.

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

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

Title:
  Discover crasFrequent crashes in plasma-discover with libglib-2.0
  errorshes after click on apps or extension for apps or plasma
  extensions

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  Description:
  I am experiencing frequent crashes with the application plasma-discover on 
Ubuntu 22.04.4 LTS. These crashes occur when I attempt to access the update 
functions within the Discover UI. Terminal outputs and system logs indicate 
issues with libglib-2.0, showing repeated trap int3 errors, which are typically 
used for debug breakpoints in development builds.

  Expected Behavior:
  Plasma Discover should run smoothly, allowing the management of software 
updates and installations without crashing.

  Actual Behavior:
  Discover crashes frequently, especially when trying to access the updates 
section or other specific parts of the application.

  Steps Attempted:

  Resetting configuration files for Discover.
  Running Discover from the terminal to capture any error outputs.
  System update and reinstallation of plasma-discover and its dependencies.
  Analyzing system logs with journalctl, which showed repeated issues with 
libglib-2.0.

  System and Package Information:

  Ubuntu Version: 22.04.4 LTS
  Package Versions:
  libglib2.0-0: Installed: 2.72.4-0ubuntu2.2
  plasma-discover: Installed: 5.24.7-0ubuntu0.1

  This issue significantly impacts the functionality of the Discover
  application, hindering routine software management and updates. Any
  assistance or resolution would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglib2.0-0 2.72.4-0ubuntu2.2
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May  1 09:58:53 2024
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2064485/+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 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]

[Daniel van Vugt]

If you are interested in debugging then please use:

  MUTTER_DEBUG_FORCE_KMS_MODE=atomic
  MUTTER_DEBUG=kms

Then wait until the problem happens again and run:

  journalctl -b0 /usr/bin/gnome-shell > gslog.txt

and attach the resulting text file here.

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4
  [drmModeAtomicCommit: Invalid argument]

Status in mutter package in Ubuntu:
  New

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble wayland-session
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064275/+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 2064485] [NEW] Discover crasFrequent crashes in plasma-discover with libglib-2.0 errorshes after click on apps or extension for apps or plasma extensions

[Paul Schumacher]

Public bug reported:

Description:
I am experiencing frequent crashes with the application plasma-discover on 
Ubuntu 22.04.4 LTS. These crashes occur when I attempt to access the update 
functions within the Discover UI. Terminal outputs and system logs indicate 
issues with libglib-2.0, showing repeated trap int3 errors, which are typically 
used for debug breakpoints in development builds.

Expected Behavior:
Plasma Discover should run smoothly, allowing the management of software 
updates and installations without crashing.

Actual Behavior:
Discover crashes frequently, especially when trying to access the updates 
section or other specific parts of the application.

Steps Attempted:

Resetting configuration files for Discover.
Running Discover from the terminal to capture any error outputs.
System update and reinstallation of plasma-discover and its dependencies.
Analyzing system logs with journalctl, which showed repeated issues with 
libglib-2.0.

System and Package Information:

Ubuntu Version: 22.04.4 LTS
Package Versions:
libglib2.0-0: Installed: 2.72.4-0ubuntu2.2
plasma-discover: Installed: 5.24.7-0ubuntu0.1

This issue significantly impacts the functionality of the Discover
application, hindering routine software management and updates. Any
assistance or resolution would be greatly appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libglib2.0-0 2.72.4-0ubuntu2.2
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed May  1 09:58:53 2024
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  Discover crasFrequent crashes in plasma-discover with libglib-2.0
  errorshes after click on apps or extension for apps or plasma
  extensions

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Description:
  I am experiencing frequent crashes with the application plasma-discover on 
Ubuntu 22.04.4 LTS. These crashes occur when I attempt to access the update 
functions within the Discover UI. Terminal outputs and system logs indicate 
issues with libglib-2.0, showing repeated trap int3 errors, which are typically 
used for debug breakpoints in development builds.

  Expected Behavior:
  Plasma Discover should run smoothly, allowing the management of software 
updates and installations without crashing.

  Actual Behavior:
  Discover crashes frequently, especially when trying to access the updates 
section or other specific parts of the application.

  Steps Attempted:

  Resetting configuration files for Discover.
  Running Discover from the terminal to capture any error outputs.
  System update and reinstallation of plasma-discover and its dependencies.
  Analyzing system logs with journalctl, which showed repeated issues with 
libglib-2.0.

  System and Package Information:

  Ubuntu Version: 22.04.4 LTS
  Package Versions:
  libglib2.0-0: Installed: 2.72.4-0ubuntu2.2
  plasma-discover: Installed: 5.24.7-0ubuntu0.1

  This issue significantly impacts the functionality of the Discover
  application, hindering routine software management and updates. Any
  assistance or resolution would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglib2.0-0 2.72.4-0ubuntu2.2
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May  1 09:58:53 2024
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2064485/+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 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]

[Ge-org Brohammer]

Thank you.  I have added the option and it seems to be working. If there
is anything else I can check or test to solve the bug, let me know.

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4
  [drmModeAtomicCommit: Invalid argument]

Status in mutter package in Ubuntu:
  New

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble wayland-session
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064275/+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 2051574] Re: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()

[Lucas]

Issue present on installed today 24.04, during initial boot

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

Title:
  gnome-shell-portal-helper crashed with SIGTRAP in
  waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Same as Summary

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 08:56:29 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-portal-helper
  InstallationDate: Installed on 2024-01-25 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116)
  ProcCmdline: /usr/libexec/gnome-shell-portal-helper
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
  Title: gnome-shell-portal-helper crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051574/+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 2061584] Re: Rendering issues in VirtualBox with 3d on (GTK ngl backend)

[Daniel van Vugt]

Are we sure this can't just be grouped in with bug 2061118?

Bug 2063923 for example is not VMware but shows a video with the same
looking artifacts as bug 2061118.

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

Title:
  Rendering issues in VirtualBox with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in gtk4 source package in Noble:
  Triaged
Status in mesa source package in Noble:
  Triaged

Bug description:
  GTK4 apps are rendering very badly with Ubuntu 24.04 LTS Beta when ran
  in VirtualBox.

  This includes the Welcome to Ubuntu app (gnome-initial-setup), gnome-
  text-editor, and drawing the background (which uses gnome-shell-
  extension-desktop-icons-ng on Ubuntu).

  This issue was triggered by GTK4's switch to ngl as the default
  renderer instead of gl.

  However, some other similar issues (LP: #2061118, LP: #2060679) are
  being fixed in mesa instead of in gtk4 itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2061584/+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 2064354] Re: File manager crashes on run

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

Title:
  File manager crashes on run

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I 
obtained the following from the command prompt: 
  $ nautilus
  ** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files
  libEGL warning: egl: failed to create dri2 screen
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 16:15:29 2024
  GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
  InstallationDate: Installed on 2024-04-24 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064354/+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 2064354] Re: File manager crashes on run

[Sebastien Bacher]

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

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

Title:
  File manager crashes on run

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I 
obtained the following from the command prompt: 
  $ nautilus
  ** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files
  libEGL warning: egl: failed to create dri2 screen
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 16:15:29 2024
  GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
  InstallationDate: Installed on 2024-04-24 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064354/+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 2064364] Re: gnome-control-center: wireguard pair closes when loosing focus

[Sebastien Bacher]

Thank you for your bug report, could you perhaps report it upstream also
on https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues ?

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

Title:
  gnome-control-center: wireguard pair closes when loosing focus

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

Bug description:
  Just installed a fresh Ubuntu 24.04 LTS

  In gnome-control-center -> Network -> VPN -> + -> Wireguard -> Pairs
  -> +

  When adding a pair for the Wireguard connection, if the window looses
  focus (for example because we need do copy-paste from another window),
  the entire "pair" dialog closes and we loose as the info previously
  entered.

  As it is, it's almost not humanly possible to setup a wireguard
  connection manually because typing several long keys by hand is too
  error prone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064364/+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 2063923] Re: Graphic shows strange

[Daniel van Vugt]

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

Maybe that should be bug 2061584?

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

Title:
  Graphic shows strange

Status in gtk4 package in Ubuntu:
  New

Bug description:
  In Ubuntu 24.04 LTS, GNOME Applications are written in Flutter, but it
  doesn't look proper.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 27 16:32:00 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. Virtio 1.0 GPU [1af4:1050] (rev 01) (prog-if 00 [VGA 
controller])
 Subsystem: Red Hat, Inc. Virtio 1.0 GPU [1af4:1100]
  InstallationDate: Installed on 2024-04-27 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 001: Dev 002, If 0, Class=Human Interface Device, 
Driver=usbhid, 480M
   /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e54ffc83-f536-4520-a7c1-9f8dc8cca485 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.2
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/gtk4/+bug/2063923/+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 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'

[Daniel van Vugt]

Bumping importance since this is officially a blocker:
https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043

** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => High

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

** Changed in: mutter (Ubuntu)
Milestone: None => noble-updates

** Changed in: gnome-shell (Ubuntu)
Milestone: None => noble-updates

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

Title:
  gnome-shell crashed with signal 5:  Settings schema
  'org.gnome.mutter.wayland' does not contain a key named 'xwayland-
  allow-byte-swapped-clients'

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

Bug description:
  Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 
'org.gnome.mutter.wayland' does not contain a key named 
'xwayland-allow-byte-swapped-clients'
  Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 5
  Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 
'org.gnome.mutter.wayland' does not contain a key named 
'xwayland-allow-byte-swapped-clients'
  Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 5

  https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f
  https://errors.ubuntu.com/problem/db8f7e3dfc79e658b9b2aa8c596b014ce4b9f217
  https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c

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