[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Treviño]

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

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

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Opinion
Status in gnome-keyring package in Ubuntu:
  Won't Fix
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

[Zalán Hári]

** Description changed:

  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message after
  a red FAILED in the terminal. The system administrator is myself,
  because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the
  update with dpkg. While dpkg was upgrading, it printed an error message
  for every WiFi connection:
  
  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”
  
- It took at least one and a half our to find the solution on Ask Ubuntu.
+ It took at least one and a half hour to find the solution on Ask Ubuntu.
  The problem was: /etc/resolv.conf became a broken link, along with
  systemd-resolve.service. I needed to remove both of them and write a new
  resolv.conf to fix the error.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half hour to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:

[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Jurgen Schellaert]

I believe that the evolution mail program and google accounts are to
blame.

The problem went away for me after I deleted my keyring and switched
from evolution to thunderbird.

Trying to (re-)add a mail account to evolution immediately brings the
problem is back.

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Won't Fix

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-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

[Daniel van Vugt]

Please try using apport-cli if ubuntu-bug fails, but I guess both might
fail if any packages are out of date.

I'm guessing this crash is due to some extension because nobody else is
reporting it, and because you seem to have so many extensions installed.
And because the crashing code seems to be called directly from some
Javascript. So please try removing gnome-shell extensions from the
system.

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

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

Title:
  crash in meta_wayland_transaction_commit

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/gnome-shell/+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 1998344] Re: Night Light doesn't alter screen display colour temperature

[ubuntuuser]

This problem is still going on the new 24.04 when running on a very old
mac.

OS: Ubuntu Noble Numbat (development 
Host: MacBookPro8,2 1.0 
Kernel: 6.8.0-22-generic 
DE: GNOME 46.0 
CPU: Intel i7-2675QM (8) @ 3.100GHz 
GPU: Intel 2nd Generation Core Proce 
GPU: AMD ATI Radeon HD 6630M/6650M/6

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

Title:
  Night Light doesn't alter screen display colour temperature

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

Bug description:
  Night light turns on and off correctly (manually and automatically at 
sunset/sunrise), but it has no effect on screen colour temperature. Altering 
the colour temperature slider makes no difference. Changing display temperature 
in dconf-editor didn't have any effect either.
  Behaviour is the same in Wayland and Xorg sessions.

  (Note that 22.10 is the first ubuntu release where graphics have worked at 
all with this machine
  (Intel® Core™ i3-10100 CPU Intel CometLake-S GT2 [UHD Graphics 630]) 
  With kernels before 5.19 the i915 driver module wouldn't load.)

  I have raised the issue on ubuntu forums,
  https://ubuntuforums.org/showthread.php?t=2481261 with no indication
  of it being a problem also reported by other 22.10 users, so it may be
  specific to this CPU.

  It also appears to be specific to gnome desktop. I have tried a
  Kubuntu liveUSB and night light worked correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 30 14:47:25 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/1998344/+subscriptions


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

[Desktop-packages] [Bug 2061886] Re: Under VMWare resolution does not change automaticaly

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xserver-xorg-video-vmware (Ubuntu)

** Tags added: vmwgfx

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

Title:
  Under VMWare resolution does not change automaticaly

Status in xserver-xorg-video-vmware package in Ubuntu:
  New

Bug description:
  When resizing a VMWare Workstation, under Ubuntu20 the resolution
  would change automaticaly.  It does not in the Ubuntu 24 Beta. During
  installation I have enabled download of third party driver.

  I can see vmtoold running.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  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: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Apr 16 14:03:39 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2024-04-16 (0 days ago)
  InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware7,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=93447c69-bef1-4d4b-917b-41be1fbda0ea ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2023
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.21100432.B64.2301110304
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.21100432.B64.2301110304:bd01/11/2023:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware7,1
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  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.11-2ubuntu1
  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/xserver-xorg-video-vmware/+bug/2061886/+subscriptions


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

[Desktop-packages] [Bug 2061927] Re: Gnome Online Accounts setup removed from gnome-initial-setup

[Jeremy Bícha]

** Bug watch added: gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues #215
   https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/215

** Also affects: gnome-initial-setup via
   https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/215
   Importance: Unknown
   Status: Unknown

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

Title:
  Gnome Online Accounts setup removed from gnome-initial-setup

Status in GNOME Initial Setup:
  Unknown
Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  Per LP: #2049513, Online Accounts integration was removed as opposed
  to finding a downstream solution, which would have been as easy as
  using the default web browser instead of a webkitgtk-powered popup.
  Unfortunately, even though potential ideas were tossed around during
  the Ubuntu Flavor Sync at Ubuntu Summit 2023 in Riga and the following
  flavor sync online, obviously nothing ever came to fruition.

  This issue is especially important to Edubuntu as one of its target
  audiences (teachers) want to be able to set-up their systems for email
  right away. gnome-initial-setup would give them that email setup out-
  of-the-box.

  This is a User Experience regression and a solution needs to be found
  even if we need to implement one downstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-initial-setup/+bug/2061927/+subscriptions


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

[Desktop-packages] [Bug 2061936] Re: Chrome starts, but runs wild in the bg (never gets to the screen). chromium works fine.

[Cesar A. Quiroz]

Running ubuntu-bug managed to open a Chrome window!  (The one I am
typing from.)  I will keep it alive as long as possible.

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

Title:
  Chrome starts, but runs wild in the bg (never gets to the screen).
  chromium works fine.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This started today. The chrome snap was automatically updated (updates
  to chrome have been arriving fast).  After the update, chrome started
  failing:

  * Clocking on the launcher succeeds, but nothing pops up to the
  screen. The UI freezes (can't even updated htop on a term).

  * Right clicking on the launcher icon, followed by choosing Quit
  restores responsiveness, but there is no chrome.

  * chromium launches fine.

  Both images come from the same snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:48:10 2024
  ProcEnviron:
   LANG=en_US.UTF-8
   LC_TIME=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  Snap: chromium 123.0.6312.122 (latest/stable)
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   612  Done2024-04-16T18:04:21-07:00  2024-04-16T18:04:40-07:00  Revert 
"chromium" snap
   613  Done2024-04-16T18:11:03-07:00  2024-04-16T18:11:16-07:00  Refresh 
"chromium" snap
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061936/+subscriptions


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

[Desktop-packages] [Bug 2061827] Re: Resizing app window can trigger tilling highlighter

[Daniel van Vugt]

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  Resizing app window can trigger tilling highlighter

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when resizing apps windows, it show the tilling highlighter
  as shown in the screenshot and it stays like that until you try to
  tile a window manually.

  It's only a view but you can still click what's behind it.

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 13:28:07 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-03-22 (25 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.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 2024-04-11 (5 days ago)

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


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

[Desktop-packages] [Bug 2061936] [NEW] Chrome starts, but runs wild in the bg (never gets to the screen). chromium works fine.

[Cesar A. Quiroz]

Public bug reported:

This started today. The chrome snap was automatically updated (updates
to chrome have been arriving fast).  After the update, chrome started
failing:

* Clocking on the launcher succeeds, but nothing pops up to the screen.
The UI freezes (can't even updated htop on a term).

* Right clicking on the launcher icon, followed by choosing Quit
restores responsiveness, but there is no chrome.

* chromium launches fine.

Both images come from the same snap.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 18:48:10 2024
ProcEnviron:
 LANG=en_US.UTF-8
 LC_TIME=en_GB.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
Snap: chromium 123.0.6312.122 (latest/stable)
SnapChanges:
 ID   Status  Spawn  Ready  Summary
 612  Done2024-04-16T18:04:21-07:00  2024-04-16T18:04:40-07:00  Revert 
"chromium" snap
 613  Done2024-04-16T18:11:03-07:00  2024-04-16T18:11:16-07:00  Refresh 
"chromium" snap
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug mantic snap

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

Title:
  Chrome starts, but runs wild in the bg (never gets to the screen).
  chromium works fine.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This started today. The chrome snap was automatically updated (updates
  to chrome have been arriving fast).  After the update, chrome started
  failing:

  * Clocking on the launcher succeeds, but nothing pops up to the
  screen. The UI freezes (can't even updated htop on a term).

  * Right clicking on the launcher icon, followed by choosing Quit
  restores responsiveness, but there is no chrome.

  * chromium launches fine.

  Both images come from the same snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:48:10 2024
  ProcEnviron:
   LANG=en_US.UTF-8
   LC_TIME=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  Snap: chromium 123.0.6312.122 (latest/stable)
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   612  Done2024-04-16T18:04:21-07:00  2024-04-16T18:04:40-07:00  Revert 
"chromium" snap
   613  Done2024-04-16T18:11:03-07:00  2024-04-16T18:11:16-07:00  Refresh 
"chromium" snap
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061936/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-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

[Daniel van Vugt]

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

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

Title:
  crash in meta_wayland_transaction_commit

Status in gnome-shell package in Ubuntu:
  New

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/ubuntu/+source/gnome-shell/+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 2061731] Re: Long delay on right click on nautilus window

[Daniel van Vugt]

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

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

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

Title:
  Long delay on right click on nautilus window

Status in Ubuntu:
  Fix Released

Bug description:
  Right click on nautilus window the dropdown menu appears with a delay. NO 
delay clicking on desktop or on firefox window.
  Journalctl shows:

  Apr 16 08:15:07 corrado-n5-nn-0414 gnome-shell[2240]: Failed to read extents 
of focused component: Failed to validate parent window: GLib.Error atspi_error: 
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  Apr 16 08:15:07 corrado-n5-nn-0414 gnome-shell[2240]: Failed to read extents 
of focused component: Failed to validate parent window: GLib.Error atspi_error: 
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  Apr 16 08:15:08 corrado-n5-nn-0414 gnome-shell[2240]: Failed to read extents 
of focused component: Did not receive a reply. Possible causes include: the 
remote application did not send a reply, the message bus security policy 
blocked the reply, the reply timeout expired, or the network connection was 
broken.

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 08:40:36 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-04-14 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240414)
  ProcEnviron:
   LANG=en_US.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: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2038801] Re: Secondary GPU frame rates are held back by dynamic-max-render-time

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: mutter (Ubuntu)
   Status: Triaged => Fix Committed

** Tags added: fixed-in-mutter-46.1 fixed-upstream

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

Title:
  Secondary GPU frame rates are held back by dynamic-max-render-time

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

Bug description:
  Secondary GPU frame rates are held back by dynamic-max-render-time as
  shown on this amdgpu setup connected to a 60 Hz monitor:

  main: 30 FPS
  main + CLUTTER_PAINT=disable-dynamic-max-render-time: 60 FPS

  https://gitlab.gnome.org/GNOME/mutter/-/issues/3070

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


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

[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions

[Daniel van Vugt]

** Tags added: fixed-in-mutter-46.1 fixed-upstream

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

Title:
  [nvidia] Secondary monitor performance is slow on an Nvidia hybrid
  system in Wayland sessions

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

Bug description:
  In session with Wayland the Nvidia driver settings do not load. And
  there is a sluggishness when opening apps, show applications menu,
  maximize, changing workspace, resize, changing monitor windows etc.
  When in an Xorg session the Nvidia settings load correctly and the
  performance is satisfactory.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 21:18:08 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 
[8086:2086]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] 
[8086:2086]
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Avell High Performance A60 MUV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QCCFL357.0122.2020.0911.1520
  dmi.board.name: Avell High Performance
  dmi.board.vendor: Avell High Performance
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV:
  dmi.product.family: A60 MUV
  dmi.product.name: A60 MUV
  dmi.product.sku: A60 MUV
  dmi.sys.vendor: Avell High Performance
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.

[Ken Sharp]

This seems to be specific to Lubuntu. Has anyone tried a recent Lubuntu
release?

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

Title:
  LibreOffice crashes under load.

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:7.0.3-0ubuntu1
Version table:
   1:7.0.3-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages

  I expect to be able to open all of LibreOffice's apps at once and use
  them.

  If you open all the LibreOffice applications and then select a
  template for LibreOffice Writer, they all close immediately, reopen,
  and offer to recover any lost data.

  Error reports may have been sent. I am not sure as this is Hirsute and
  I'm testing it.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: LXQt
  Date: Mon Nov 23 20:06:19 2020
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2061927] [NEW] Gnome Online Accounts setup removed from gnome-initial-setup

[Erich Eickmeyer]

Public bug reported:

Per LP: #2049513, Online Accounts integration was removed as opposed to
finding a downstream solution, which would have been as easy as using
the default web browser instead of a webkitgtk-powered popup.
Unfortunately, even though potential ideas were tossed around during the
Ubuntu Flavor Sync at Ubuntu Summit 2023 in Riga and the following
flavor sync online, obviously nothing ever came to fruition.

This issue is especially important to Edubuntu as one of its target
audiences (teachers) want to be able to set-up their systems for email
right away. gnome-initial-setup would give them that email setup out-of-
the-box.

This is a User Experience regression and a solution needs to be found
even if we need to implement one downstream.

** Affects: gnome-initial-setup (Ubuntu)
 Importance: High
 Status: New

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

Title:
  Gnome Online Accounts setup removed from gnome-initial-setup

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  Per LP: #2049513, Online Accounts integration was removed as opposed
  to finding a downstream solution, which would have been as easy as
  using the default web browser instead of a webkitgtk-powered popup.
  Unfortunately, even though potential ideas were tossed around during
  the Ubuntu Flavor Sync at Ubuntu Summit 2023 in Riga and the following
  flavor sync online, obviously nothing ever came to fruition.

  This issue is especially important to Edubuntu as one of its target
  audiences (teachers) want to be able to set-up their systems for email
  right away. gnome-initial-setup would give them that email setup out-
  of-the-box.

  This is a User Experience regression and a solution needs to be found
  even if we need to implement one downstream.

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


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

[Desktop-packages] [Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1

[Brian Murray]

This ended up causing my release upgrade to go burst into flames. That's
documented in https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/2061923 .

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

Title:
  package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new
  thunderbird package pre-installation script subprocess returned error
  exit status 1

Status in thunderbird package in Ubuntu:
  New

Bug description:
  This happened during an upgrade from Mantic to Noble.

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: thunderbird 2:1snap1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset wl nvidia zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Apr 16 13:15:42 2024
  ErrorMessage: new thunderbird package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-08-10 (2076 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.6ubuntu6
   apt  2.7.14build2
  SnapChanges:
   IDStatus  Spawn  Ready  Summary
   3563  Error   2024-04-16T13:15:26-07:00  2024-04-16T13:15:42-07:00  Install 
"thunderbird" snap
   3564  Done2024-04-16T13:22:00-07:00  2024-04-16T13:22:09-07:00  Install 
"thunderbird" snap
  SourcePackage: thunderbird
  Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new 
thunderbird package pre-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago)

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


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

[Desktop-packages] [Bug 2061918] [NEW] package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1

[Brian Murray]

Public bug reported:

This happened during an upgrade from Mantic to Noble.

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: thunderbird 2:1snap1-0ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset wl nvidia zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Apr 16 13:15:42 2024
ErrorMessage: new thunderbird package pre-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-08-10 (2076 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.6ubuntu6
 apt  2.7.14build2
SnapChanges:
 IDStatus  Spawn  Ready  Summary
 3563  Error   2024-04-16T13:15:26-07:00  2024-04-16T13:15:42-07:00  Install 
"thunderbird" snap
 3564  Done2024-04-16T13:22:00-07:00  2024-04-16T13:22:09-07:00  Install 
"thunderbird" snap
SourcePackage: thunderbird
Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new 
thunderbird package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago)

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


** Tags: amd64 apport-package cuqa-manual-testing need-duplicate-check noble

** Tags added: cuqa-manual-testing

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

Title:
  package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new
  thunderbird package pre-installation script subprocess returned error
  exit status 1

Status in thunderbird package in Ubuntu:
  New

Bug description:
  This happened during an upgrade from Mantic to Noble.

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: thunderbird 2:1snap1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset wl nvidia zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Apr 16 13:15:42 2024
  ErrorMessage: new thunderbird package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-08-10 (2076 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.6ubuntu6
   apt  2.7.14build2
  SnapChanges:
   IDStatus  Spawn  Ready  Summary
   3563  Error   2024-04-16T13:15:26-07:00  2024-04-16T13:15:42-07:00  Install 
"thunderbird" snap
   3564  Done2024-04-16T13:22:00-07:00  2024-04-16T13:22:09-07:00  Install 
"thunderbird" snap
  SourcePackage: thunderbird
  Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new 
thunderbird package pre-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago)

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


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

[Desktop-packages] [Bug 2061915] [NEW] While upgrading python3 package gives error

[Islam]

Public bug reported:

While upgrading the python3 package, it gave these errors:

Setting up python3 (3.12.3-0ubuntu1) ...
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence 
'\#'
  re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence 
'\/'
  re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence 
'\*'
  re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d'
  http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I)
/usr/lib/kitty/kitty/options/definition.py:4116: SyntaxWarning: invalid escape 
sequence '\e'
  long_text='''
/usr/lib/rhythmbox/plugins/alternative-toolbar/alttoolbar_plugins.py:171: 
SyntaxWarning: invalid escape sequence '\('
  translation = re.sub('\(..\)', '', translation, flags=re.DOTALL)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:64: 
SyntaxWarning: invalid escape sequence '\/'
  url = re.split('(\/display[^"]*)', entry)[1]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:66: 
SyntaxWarning: invalid escape sequence '\/'
  title = re.split('(\/display[^>]*)([^<]*)', entry)[2][1:].strip()
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:97: 
SyntaxWarning: invalid escape sequence '\/'
  lyrics = re.split('()(.*)(<\/font>http://jetlyrics\.com/viewlyrics\.php\?id=[0-9]*)\'>', result)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/JlyricParser.py:49: 
SyntaxWarning: invalid escape sequence '\.'
  m = re.search('', 
result)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/TerraParser.py:39: 
SyntaxWarning: invalid escape sequence '\w'
  pattern = re.compile("&(#?\w+?);")
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/WinampcnParser.py:87: 
SyntaxWarning: invalid escape sequence '\['
  lrcplaintext = re.sub('\[.*?\]', '', lrcplaintext)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning: 
invalid escape sequence '\('
  LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)", 
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning: 
invalid escape sequence '\('
  LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)", 
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning: 
invalid escape sequence '\('
  LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)", 
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning: 
invalid escape sequence '\('
  LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)", 
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning: 
invalid escape sequence '\('
  LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)", 
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning: 
invalid escape sequence '\('
  LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)", 
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
running python post-rtupdate hooks for python3.12...

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: python3 3.12.3-0ubuntu1
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: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 00:38:58 2024
InstallationDate: Installed on 2024-03-22 (25 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: python3-defaults
UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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


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

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

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

Title:
  While upgrading python3 package gives error

Status in python3-defaults package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  While upgrading the python3 package, it gave these errors:

  

[Desktop-packages] [Bug 2061916] [NEW] Seahorse asks to unlock the keyring every time after login

[Islam]

Public bug reported:

After upgrading from 23.10 to 24.10 beta, every time I login it ask me to 
unlock the default keyring.
I set the keyring password same as my user's password but still.

Please check the attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: seahorse 43.0-3build2
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: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 00:40:48 2024
InstallationDate: Installed on 2024-03-22 (25 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: seahorse
UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago)

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


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

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

Title:
  Seahorse asks to unlock the keyring every time after login

Status in seahorse package in Ubuntu:
  New

Bug description:
  After upgrading from 23.10 to 24.10 beta, every time I login it ask me to 
unlock the default keyring.
  I set the keyring password same as my user's password but still.

  Please check the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: seahorse 43.0-3build2
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 00:40:48 2024
  InstallationDate: Installed on 2024-03-22 (25 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: seahorse
  UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] libjavascriptcoregtk-4.0-18 seems to be missing on the latest build (24.04)

[Gastón Alegre Stotzer]

Public bug reported:

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
libjavascriptcoregtk-6.0-1-dbgsym debug symbols for 
libjavascriptcoregtk-6.0-1
libjavascriptcoregtk-6.0-dev JavaScript engine library from WebKitGTK - 
development files
libjavascriptcoregtk-bin JavaScript engine library from WebKitGTK - 
command-line interpreter
libjavascriptcoregtk-bin-dbgsym debug symbols for libjavascriptcoregtk-bin
libwebkit2gtk-4.0-doc WebKitGTK documentation (transitional dummy package)
 MISSING!!!
 MISSING!!!
 MISSING!!!
 MISSING!!!
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
libwebkitgtk-doc Web content engine library for GTK - 

[Desktop-packages] [Bug 2061686] Re: After updating to ubuntu 24.04, WiFi doesn't connect to secured networks at login or resume from sleep

[Nicolás Abel Carbone]

Forgetting and reconnecting to the WiFi networks solves the issue. 
Fell free to mark this bug as solved if you consider that this workaround 
invalidates the bug.

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

Title:
  After updating to ubuntu 24.04, WiFi doesn't connect to secured
  networks at login or resume from sleep

Status in network-manager package in Ubuntu:
  New

Bug description:
  I updated a Thinkpad T14 AMD Gen 2 from 23.10 to 24.04. Since the
  update, WiFi doesn't automatically connect at login or when resuming
  from sleep if the network is secured with a password.

  It does connect automatically if it finds a remembered open network.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  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
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 17:50:40 2024
  InstallationDate: Installed on 2022-02-02 (803 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (4 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

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


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

[Desktop-packages] [Bug 2061912] Re: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04

[Nicolás Abel Carbone]

** Package changed: network-manager (Ubuntu) => linux-lowlatency
(Ubuntu)

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

Title:
  After a very recent update most browsers are not able to load webpages
  in Ubuntu 24.04

Status in linux-lowlatency package in Ubuntu:
  New

Bug description:
  After a recent update of packages (in the last couple of hours or so)
  neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap)
  are able to load pages. Gnome Web is the only one that seems to work.
  Also, apt loads fine.

  Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
  Uname: Linux 6.8.0-25-lowlatency x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:55:41 2024
  InstallationDate: Installed on 2022-02-02 (804 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2061912/+subscriptions


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

[Desktop-packages] [Bug 1693999] Re: package libjavascriptcoregtk-4.0-18:amd64 2.16.1-0ubuntu0.16.04.1 failed to install/upgrade: package libjavascriptcoregtk-4.0-18:amd64 is not ready for configurati

[Gastón Alegre Stotzer]

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

Title:
  package libjavascriptcoregtk-4.0-18:amd64 2.16.1-0ubuntu0.16.04.1
  failed to install/upgrade: package libjavascriptcoregtk-4.0-18:amd64
  is not ready for configuration  cannot configure (current status
  'half-installed')

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  pops up during booting

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjavascriptcoregtk-4.0-18:amd64 2.16.1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri May 26 19:24:10 2017
  DuplicateSignature:
   package:libjavascriptcoregtk-4.0-18:amd64:2.16.1-0ubuntu0.16.04.1
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libjavascriptcoregtk-4.0-18:amd64 
(--configure):
package libjavascriptcoregtk-4.0-18:amd64 is not ready for configuration
  ErrorMessage: package libjavascriptcoregtk-4.0-18:amd64 is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-10 (17 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: webkit2gtk
  Title: package libjavascriptcoregtk-4.0-18:amd64 2.16.1-0ubuntu0.16.04.1 
failed to install/upgrade: package libjavascriptcoregtk-4.0-18:amd64 is not 
ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Re: [Desktop-packages] [Bug 2061912] [NEW] After a very recent update most browsers are not able to load webpages in Ubuntu 24.04

[Nicolás Abel Carbone]

I could narrow down the problem to linux-lowlatency 6.8.0-25.25.3.
Before updating to Ubuntu 24.04 I had the lowlatency kernel installed. When
updating it reverted back to generic and the last update installed
linux-lowlatency 6.8.0-25.25.3, which seems to have generated the bug.

Uninstalling the lowlatency kernel and running on the generic solves the
issue.

On Tue, Apr 16, 2024 at 7:05 PM Nicolás Abel Carbone <
2061...@bugs.launchpad.net> wrote:

> Public bug reported:
>
> After a recent update of packages (in the last couple of hours or so)
> neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are
> able to load pages. Gnome Web is the only one that seems to work. Also,
> apt loads fine.
>
> Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 24.04
> Package: network-manager 1.46.0-1ubuntu2
> ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
> Uname: Linux 6.8.0-25-lowlatency x86_64
> ApportVersion: 2.28.0-0ubuntu1
> Architecture: amd64
> CRDA: N/A
> CasperMD5CheckResult: pass
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Apr 16 18:55:41 2024
> InstallationDate: Installed on 2022-02-02 (804 days ago)
> InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
> IpRoute:
>  default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600
>  172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
> linkdown
>  192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128
> metric 600
>  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
> linkdown
> SourcePackage: network-manager
> UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
> nmcli-nm:
>  RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING
> WIFI-HW   WIFI  WWAN-HW  WWAN
>  ejecutando  1.46.0   conectado  Iniciado  total activado
> activado  activado  missing  activado
>
> ** Affects: network-manager (Ubuntu)
>  Importance: Undecided
>  Status: New
>
>
> ** Tags: amd64 apport-bug noble wayland-session
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2061912
>
> Title:
>   After a very recent update most browsers are not able to load webpages
>   in Ubuntu 24.04
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2061912/+subscriptions
>
>

-- 
Nicolás Abel Carbone

Doctor en Física
Investigador Asistente CONICET
JTP en Facultad de Ciencias Exactas UNCPBA
Grupo de Óptica Biomédica - CIFICEN-CONICET-UNCPBA

Research Gate  - epsilon.h
 - Bionirs  - Github


*Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo
indique el mail, por favor no se sienta obligado a responder este mensaje
fuera de su horario de trabajo habitual.*

*My working hours may not be your working hours. Unless otherwise specified
in the mail, please do not feel obligated to reply outside of your normal
work schedule.*

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

Title:
  After a very recent update most browsers are not able to load webpages
  in Ubuntu 24.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  After a recent update of packages (in the last couple of hours or so)
  neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap)
  are able to load pages. Gnome Web is the only one that seems to work.
  Also, apt loads fine.

  Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
  Uname: Linux 6.8.0-25-lowlatency x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:55:41 2024
  InstallationDate: Installed on 2022-02-02 (804 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

To manage notifications about this bug go to:

[Desktop-packages] [Bug 2061912] [NEW] After a very recent update most browsers are not able to load webpages in Ubuntu 24.04

[Nicolás Abel Carbone]

Public bug reported:

After a recent update of packages (in the last couple of hours or so)
neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are
able to load pages. Gnome Web is the only one that seems to work. Also,
apt loads fine.

Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager 1.46.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
Uname: Linux 6.8.0-25-lowlatency x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 18:55:41 2024
InstallationDate: Installed on 2022-02-02 (804 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
IpRoute:
 default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
SourcePackage: network-manager
UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
nmcli-nm:
 RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN 
 ejecutando  1.46.0   conectado  Iniciado  total activadoactivado  
activado  missing  activado

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


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

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

Title:
  After a very recent update most browsers are not able to load webpages
  in Ubuntu 24.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  After a recent update of packages (in the last couple of hours or so)
  neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap)
  are able to load pages. Gnome Web is the only one that seems to work.
  Also, apt loads fine.

  Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
  Uname: Linux 6.8.0-25-lowlatency x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:55:41 2024
  InstallationDate: Installed on 2022-02-02 (804 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

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


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

[Desktop-packages] [Bug 2061907] [NEW] Update freerdp3 to 3.5.0

[Jeremy Bícha]

*** This bug is a security vulnerability ***

Public security bug reported:

freerdp 3.5.0 was released as a security update.

https://github.com/FreeRDP/FreeRDP/releases/tag/3.5.0

https://github.com/FreeRDP/FreeRDP/compare/3.4.0...3.5.0

There are a very large number of coverity fixes and bound check fixes
and resource leak updates in the new release. It does not look very
practical to cherry-pick only some of those fixes. And the git commits
aren't directly associated with which CVE they are supposed to fix.

** Affects: freerdp3 (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: noble upgrade-software-version

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

Title:
  Update freerdp3 to 3.5.0

Status in freerdp3 package in Ubuntu:
  Triaged

Bug description:
  freerdp 3.5.0 was released as a security update.

  https://github.com/FreeRDP/FreeRDP/releases/tag/3.5.0

  https://github.com/FreeRDP/FreeRDP/compare/3.4.0...3.5.0

  There are a very large number of coverity fixes and bound check fixes
  and resource leak updates in the new release. It does not look very
  practical to cherry-pick only some of those fixes. And the git commits
  aren't directly associated with which CVE they are supposed to fix.

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


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

[Desktop-packages] [Bug 1938605] Re: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements

[wontfix]

** No longer affects: gnome-terminal (Debian)

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

Title:
  Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

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

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

  

  should be replaced by

  ,

  and

  

  should be replaced by

  

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

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

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

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


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

[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Allen]

Got it, thanks!

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Won't Fix

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2061731] Re: Long delay on right click on nautilus window

[corrado venturini]

Does not occur in the new installation from Ubuntu 24.04 LTS "Noble
Numbat" - Beta amd64 (20240416)

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

Title:
  Long delay on right click on nautilus window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Right click on nautilus window the dropdown menu appears with a delay. NO 
delay clicking on desktop or on firefox window.
  Journalctl shows:

  Apr 16 08:15:07 corrado-n5-nn-0414 gnome-shell[2240]: Failed to read extents 
of focused component: Failed to validate parent window: GLib.Error atspi_error: 
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  Apr 16 08:15:07 corrado-n5-nn-0414 gnome-shell[2240]: Failed to read extents 
of focused component: Failed to validate parent window: GLib.Error atspi_error: 
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  Apr 16 08:15:08 corrado-n5-nn-0414 gnome-shell[2240]: Failed to read extents 
of focused component: Did not receive a reply. Possible causes include: the 
remote application did not send a reply, the message bus security policy 
blocked the reply, the reply timeout expired, or the network connection was 
broken.

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 08:40:36 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-04-14 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240414)
  ProcEnviron:
   LANG=en_US.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: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Jeremy Bícha]

Allen, gnome-keyring is not the package that needs to be updated for
this issue. It's gdm3.

https://launchpad.net/bugs/2060575

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Won't Fix

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Allen]

Same issue here. I don't understand the status, "Won't fix"?

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Won't Fix

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2061886] [NEW] Under VMWare resolution does not change automaticaly

[Mario Charest]

Public bug reported:

When resizing a VMWare Workstation, under Ubuntu20 the resolution would
change automaticaly.  It does not in the Ubuntu 24 Beta. During
installation I have enabled download of third party driver.

I can see vmtoold running.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
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: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Apr 16 14:03:39 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2024-04-16 (0 days ago)
InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware7,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=93447c69-bef1-4d4b-917b-41be1fbda0ea ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW71.00V.21100432.B64.2301110304
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.21100432.B64.2301110304:bd01/11/2023:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware7,1
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
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.11-2ubuntu1
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

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


** Tags: amd64 apport-bug noble resolution ubuntu

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

Title:
  Under VMWare resolution does not change automaticaly

Status in xorg package in Ubuntu:
  New

Bug description:
  When resizing a VMWare Workstation, under Ubuntu20 the resolution
  would change automaticaly.  It does not in the Ubuntu 24 Beta. During
  installation I have enabled download of third party driver.

  I can see vmtoold running.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  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: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Apr 16 14:03:39 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2024-04-16 (0 days ago)
  InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware7,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=93447c69-bef1-4d4b-917b-41be1fbda0ea ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2023
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.21100432.B64.2301110304
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.21100432.B64.2301110304:bd01/11/2023:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware7,1
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: 

[Desktop-packages] [Bug 2061882] Re: Thunderbird snap loses local folder settings in 24.04

[wil]

** Description changed:

  After Thunderbird snap installs the local folders do not import from the
  deb Thunderbird. There also seems to be no way to get back to the deb
  version. I needed to manually move the local directory back to the
  original.
+ 
+ I can no longer see my inbox and it keeps telling me that the
+ /home/me/snap/thunderbird/hdd/home/me/.thunderbird/24a1u6qp.default/ImapMail/
+ is invalid

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

Title:
  Thunderbird snap loses local folder settings  in 24.04

Status in thunderbird package in Ubuntu:
  New

Bug description:
  After Thunderbird snap installs the local folders do not import from
  the deb Thunderbird. There also seems to be no way to get back to the
  deb version. I needed to manually move the local directory back to the
  original.

  I can no longer see my inbox and it keeps telling me that the
  /home/me/snap/thunderbird/hdd/home/me/.thunderbird/24a1u6qp.default/ImapMail/
  is invalid

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


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

[Desktop-packages] [Bug 2061882] [NEW] Thunderbird snap loses local folder settings in 24.04

[wil]

Public bug reported:

After Thunderbird snap installs the local folders do not import from the
deb Thunderbird. There also seems to be no way to get back to the deb
version. I needed to manually move the local directory back to the
original.

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

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

Title:
  Thunderbird snap loses local folder settings  in 24.04

Status in thunderbird package in Ubuntu:
  New

Bug description:
  After Thunderbird snap installs the local folders do not import from
  the deb Thunderbird. There also seems to be no way to get back to the
  deb version. I needed to manually move the local directory back to the
  original.

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


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

[Desktop-packages] [Bug 2061880] [NEW] Crash on Xubuntu 24.04 Beta when trying to RDP

[wil]

Public bug reported:

This could be related to
https://gitlab.com/Remmina/Remmina/-/issues/3090

remmina-Message: 19:16:12.858: Remmina does not log all output statements. Turn 
on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment 
variable.
More info available on the Remmina wiki at:
https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging

(org.remmina.Remmina:15044): Gtk-WARNING **: 19:16:12.981: 
gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem
[19:16:16:108] [15044:3b0f] [ERROR][com.freerdp.common.settings] - 
[freerdp_settings_get_bool]: Invalid key index 0 
[FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_int_assert]: FALSE 
[obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:634]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 
[0x72d1f542b000], dli_sname=winpr_backtrace [0x72d1f5497540]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 
[0x72d1f542b000], dli_sname=winpr_log_backtrace_ex [0x72d1f549efe0]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 
[0x72d1efc0], dli_sname=(null) [(nil)]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 
[0x72d1efc0], dli_sname=freerdp_settings_get_bool [0x72d1efc648a0]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 4: 
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so 
[0x72d1f5efa000], dli_sname=(null) [(nil)]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 5: 
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so 
[0x72d1f5efa000], dli_sname=(null) [(nil)]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 6: 
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x72d1f9a0], 
dli_sname=(null) [(nil)]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 7: 
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x72d1f9a0], 
dli_sname=(null) [(nil)]
[19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 8: unresolvable, address=(nil)
Aborted (core dumped)
wil@williambell:/var/crash$

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

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

Title:
  Crash on Xubuntu 24.04 Beta when trying to RDP

Status in remmina package in Ubuntu:
  New

Bug description:
  This could be related to
  https://gitlab.com/Remmina/Remmina/-/issues/3090

  remmina-Message: 19:16:12.858: Remmina does not log all output statements. 
Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an 
environment variable.
  More info available on the Remmina wiki at:
  https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging

  (org.remmina.Remmina:15044): Gtk-WARNING **: 19:16:12.981: 
gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem
  [19:16:16:108] [15044:3b0f] [ERROR][com.freerdp.common.settings] - 
[freerdp_settings_get_bool]: Invalid key index 0 
[FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER]
  [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_int_assert]: FALSE 
[obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:634]
  [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 
[0x72d1f542b000], dli_sname=winpr_backtrace [0x72d1f5497540]
  [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 
[0x72d1f542b000], dli_sname=winpr_log_backtrace_ex [0x72d1f549efe0]
  [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 
[0x72d1efc0], dli_sname=(null) [(nil)]
  [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 
[0x72d1efc0], dli_sname=freerdp_settings_get_bool [0x72d1efc648a0]
  [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - 
[winpr_log_backtrace_ex]: 4: 
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so 
[0x72d1f5efa000], dli_sname=(null) 

[Desktop-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-mate-meta - 1.296

---
ubuntu-mate-meta (1.296) noble; urgency=medium

  * Refreshed dependencies
  * Added caja-seahorse to desktop-recommends [armhf]
  * Added firefox to core-recommends [amd64 arm64 armhf], desktop-
recommends [amd64 arm64 armhf] (LP: #2060898)

 -- Martin Wimpress   Tue, 16 Apr 2024 14:47:27 +

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Fix Released
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-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]

Applying:
$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1001.crash
is failing due to the availability of certain package 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/2061739

Title:
  crash in meta_wayland_transaction_commit

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/gnome-shell/+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 2061739] Re: crash in meta_wayland_transaction_commit

[Patrice DUROUX]

** Attachment added: "prevjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061739/+attachment/5766295/+files/prevjournal.txt

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

Title:
  crash in meta_wayland_transaction_commit

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/gnome-shell/+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 2061739] Re: crash in meta_wayland_transaction_commit

[Patrice DUROUX]

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061739/+attachment/5766296/+files/journal.txt

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

Title:
  crash in meta_wayland_transaction_commit

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/gnome-shell/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Treviño]

** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-keyring (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Won't Fix

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Won't Fix

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2061860] [NEW] Update mozjs115 to 115.10.0

[Jeremy Bícha]

Public bug reported:

Includes some security fixes

The build is fairly quick and the autopkgtest burden should be minimal,
probably just gjs.

** Affects: mozjs115 (Ubuntu)
 Importance: High
 Status: In Progress


** Tags: noble upgrade-software-version

** Tags added: upgrade-software-version

** Description changed:

  Includes some security fixes
+ 
+ The build is fairly quick and the autopkgtest burden should be minimal,
+ probably just gjs.

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

Title:
  Update mozjs115 to 115.10.0

Status in mozjs115 package in Ubuntu:
  In Progress

Bug description:
  Includes some security fixes

  The build is fairly quick and the autopkgtest burden should be
  minimal, probably just gjs.

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


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

[Desktop-packages] [Bug 2052963] Re: Upgrade from jammy to mantic failed install for gnome-control-center

[Antonio Chay Hidalgo]

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

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

Title:
  Upgrade from jammy to mantic failed install for gnome-control-center

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

Bug description:
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  apt-cache policy  gnome-control-center
  gnome-control-center:
Installed: (none)
Candidate: 1:45.0-1ubuntu3.1
Version table:
   1:45.0-1ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu mantic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
   1:45.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu mantic/main amd64 Packages

  Expected:
  A correct installation, with proper suggestions if a package is missing.

  What happened:
  I did an upgrade from jammy to mantic, gnome-control-center was missing. When 
tried to install manually, I got this error:

  The following packages have unmet dependencies:
   gnome-control-center : Depends: libsnapd-glib-2-1 (>= 1.63) but it is not 
installable

  Couldn't find any way to satisfy the dependency.

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


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

[Desktop-packages] [Bug 2061857] [NEW] [FFe] enable the new GNOME OneDrive backend

[Sebastien Bacher]

Public bug reported:

One of the new features of the new GNOME 46 is the support of Microsoft
OneDrive accounts. The code relies on a new library 'msgraph'. The MIR
bug #2060035 just got approved and such we would like to turn on the
option now in Noble.

The changes are in

- gnome-online-accounts, adding a new provider for OneDrive

The package with the change has been built in the desktop ppa
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15971851/+listing-archive-extra

The change is basically adding the libmsgraph-dev Build-Depends in
debian/control and changing the option to true in debian/rules

- gvfs, adding a new backend to be able to browse those locations from
nautilus

The package is similar built in our ppa
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15972025/+listing-archive-extra

And the change are similar Build-Depends/rules option


The regression potential is low since those are new backends and not changing 
existing features.

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

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

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

** Summary changed:

- [FFe] enable the new OneDrive backend
+ [FFe] enable the new GNOME OneDrive backend

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

Title:
  [FFe] enable the new GNOME OneDrive backend

Status in gnome-online-accounts package in Ubuntu:
  New
Status in gvfs package in Ubuntu:
  New

Bug description:
  One of the new features of the new GNOME 46 is the support of
  Microsoft OneDrive accounts. The code relies on a new library
  'msgraph'. The MIR bug #2060035 just got approved and such we would
  like to turn on the option now in Noble.

  The changes are in

  - gnome-online-accounts, adding a new provider for OneDrive

  The package with the change has been built in the desktop ppa
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15971851/+listing-archive-extra

  The change is basically adding the libmsgraph-dev Build-Depends in
  debian/control and changing the option to true in debian/rules

  - gvfs, adding a new backend to be able to browse those locations from
  nautilus

  The package is similar built in our ppa
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15972025/+listing-archive-extra

  And the change are similar Build-Depends/rules option

  
  The regression potential is low since those are new backends and not changing 
existing features.

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


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

[Desktop-packages] [Bug 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()

[Laurent Bonnaud]

This bug seems to be fixed in Ubuntu noble.
Thanks!

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

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

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

Title:
  recentmanager crashed with signal 5 in _g_log_abort()

Status in Ubuntu:
  Fix Released

Bug description:
  recentmanager crashed while I was running gnome-desktop-testing-runner

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gtk-3-examples 3.24.12-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct  9 11:44:28 2019
  ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager
  ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap
  Signal: 5
  SourcePackage: gtk+3.0
  StacktraceTop:
   _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
   g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, 
fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, 
user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694
   g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, 
log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925
   g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, 
fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898
   g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 
"../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982
  Title: recentmanager crashed with signal 5 in _g_log_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

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


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

[Desktop-packages] [Bug 2061850] [NEW] Can't authenticate in TTY after installing authd, but sudo works

[Nathan Teodosio]

Public bug reported:

In Ubuntu Noble, I install authd 0.2.1, switch to a different TTY and
try to log in.

I enter my user name and I am asked

> Select your provider
>
> 1: local

I click  and am asked for the password. After entering it I
expect to eventually get a shell, but after installing Authd I can wait
minutes and end up with nothing (as if it were validating the password).

If I enter wrong credentials I get "login incorrect" and a new user name
prompt, which is the correct behavior.

I get the same question asked when using 'sudo' but there it works.

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

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

Title:
  Can't authenticate in TTY after installing authd, but sudo works

Status in authd package in Ubuntu:
  New

Bug description:
  In Ubuntu Noble, I install authd 0.2.1, switch to a different TTY and
  try to log in.

  I enter my user name and I am asked

  > Select your provider
  >
  > 1: local

  I click  and am asked for the password. After entering it I
  expect to eventually get a shell, but after installing Authd I can
  wait minutes and end up with nothing (as if it were validating the
  password).

  If I enter wrong credentials I get "login incorrect" and a new user
  name prompt, which is the correct behavior.

  I get the same question asked when using 'sudo' but there it works.

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


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

[Desktop-packages] [Bug 2060806] Re: Update gstreamer to 1.24.2

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-bad1.0 - 1.24.2-1ubuntu4

---
gst-plugins-bad1.0 (1.24.2-1ubuntu4) noble; urgency=medium

  * Don't try to build zxing on i386

 -- Jeremy Bícha   Mon, 15 Apr 2024 09:00:06 -0400

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Update gstreamer to 1.24.2

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released

Bug description:
  Yesterday, there was a new bugfix release in the stable 1.24.2 series.
  This bug is to track updates for Ubuntu 24.04 LTS.

  https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2060806/+subscriptions


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

[Desktop-packages] [Bug 2061605] Re: Please remove libwpe & wpebackend-fdo from Ubuntu

[Sebastien Bacher]

Removing packages from noble:
libwpe 1.14.2-1 in noble
libwpe-1.0-1 1.14.2-1 in noble amd64
libwpe-1.0-1 1.14.2-1 in noble arm64
libwpe-1.0-1 1.14.2-1 in noble armhf
libwpe-1.0-1 1.14.2-1 in noble ppc64el
libwpe-1.0-1 1.14.2-1 in noble riscv64
libwpe-1.0-1 1.14.2-1 in noble s390x
libwpe-1.0-dev 1.14.2-1 in noble amd64
libwpe-1.0-dev 1.14.2-1 in noble arm64
libwpe-1.0-dev 1.14.2-1 in noble armhf
libwpe-1.0-dev 1.14.2-1 in noble ppc64el
libwpe-1.0-dev 1.14.2-1 in noble riscv64
libwpe-1.0-dev 1.14.2-1 in noble s390x
Comment: webkitgtk isn't using it anymore, no other rdepends, lp: #2061605
Remove [y|N]? y
1 package successfully removed.


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

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

Title:
  Please remove libwpe & wpebackend-fdo from Ubuntu

Status in libwpe package in Ubuntu:
  Fix Released
Status in wpebackend-fdo package in Ubuntu:
  Fix Released

Bug description:
  libwpe and wpebackend-fdo have no remaining reverse dependencies in
  Ubuntu. They are libraries related to wpewebkit (and once used by
  webkit2gtk) but I believe we would rather not be responsible for
  Security support for libraries that we are not even using.

  It looks like they are still used in Debian by cog.

  Please remove these packages from Ubuntu and add to the sync blocklist
  like was done with cog and wpewebkit.

  $ reverse-depends src:libwpe
  Reverse-Depends
  ===
  * libwpebackend-fdo-1.0-1   (for libwpe-1.0-1)
  * libwpebackend-fdo-1.0-dev (for libwpe-1.0-dev)

  $ reverse-depends -b src:libwpe
  Reverse-Build-Depends
  =
  * wpebackend-fdo(for libwpe-1.0-dev)

  $ reverse-depends src:wpebackend-fdo
  No reverse dependencies found

  $ reverse-depends -b src:wpebackend-fdo
  No reverse dependencies found

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


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

[Desktop-packages] [Bug 2061605] Re: Please remove libwpe & wpebackend-fdo from Ubuntu

[Sebastien Bacher]

Removing packages from noble:
wpebackend-fdo 1.14.2-1build3 in noble
libwpebackend-fdo-1.0-1 1.14.2-1build3 in noble amd64
libwpebackend-fdo-1.0-1 1.14.2-1build3 in noble arm64
libwpebackend-fdo-1.0-1 1.14.2-1build3 in noble armhf
libwpebackend-fdo-1.0-1 1.14.2-1build3 in noble ppc64el
libwpebackend-fdo-1.0-1 1.14.2-1build3 in noble riscv64
libwpebackend-fdo-1.0-1 1.14.2-1build3 in noble s390x
libwpebackend-fdo-1.0-dev 1.14.2-1build3 in noble amd64
libwpebackend-fdo-1.0-dev 1.14.2-1build3 in noble arm64
libwpebackend-fdo-1.0-dev 1.14.2-1build3 in noble armhf
libwpebackend-fdo-1.0-dev 1.14.2-1build3 in noble ppc64el
libwpebackend-fdo-1.0-dev 1.14.2-1build3 in noble riscv64
libwpebackend-fdo-1.0-dev 1.14.2-1build3 in noble s390x
Comment: webkitgtk isn't using it anymore, no other rdepends, lp: #2061605
Remove [y|N]? y
1 package successfully removed.


** Changed in: wpebackend-fdo (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove libwpe & wpebackend-fdo from Ubuntu

Status in libwpe package in Ubuntu:
  Fix Released
Status in wpebackend-fdo package in Ubuntu:
  Fix Released

Bug description:
  libwpe and wpebackend-fdo have no remaining reverse dependencies in
  Ubuntu. They are libraries related to wpewebkit (and once used by
  webkit2gtk) but I believe we would rather not be responsible for
  Security support for libraries that we are not even using.

  It looks like they are still used in Debian by cog.

  Please remove these packages from Ubuntu and add to the sync blocklist
  like was done with cog and wpewebkit.

  $ reverse-depends src:libwpe
  Reverse-Depends
  ===
  * libwpebackend-fdo-1.0-1   (for libwpe-1.0-1)
  * libwpebackend-fdo-1.0-dev (for libwpe-1.0-dev)

  $ reverse-depends -b src:libwpe
  Reverse-Build-Depends
  =
  * wpebackend-fdo(for libwpe-1.0-dev)

  $ reverse-depends src:wpebackend-fdo
  No reverse dependencies found

  $ reverse-depends -b src:wpebackend-fdo
  No reverse dependencies found

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


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

[Desktop-packages] [Bug 2061696] Re: Trying to setup a google account in settings

[Nick Rosbrook]

** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-control-
center (Ubuntu)

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

Title:
  Trying to setup a google account in settings

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

Bug description:
  In settings. When I select Online accounts and then google the system
  logs me right out to the login screen.

  What should happen after clicking Google it should allow me to login
  to my Google account or gdrive.

  This is running in a VM.

  Operating System: Kubuntu 24.04
  KDE Plasma Version: 5.27.11
  KDE Frameworks Version: 5.115.0
  Qt Version: 5.15.13
  Kernel Version: 6.8.0-22-generic (64-bit)
  Graphics Platform: X11
  Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
  Memory: 3.8 GiB of RAM
  Graphics Processor: llvmpipe
  Manufacturer: QEMU
  Product Name: Standard PC (Q35 + ICH9, 2009)
  System Version: pc-q35-7.2

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-release-upgrader-core 1:24.04.12
  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
  CrashDB: ubuntu
  CrashReports:
   640:1000:110:680234:2024-04-13 18:07:51.785760566 -0700:2024-04-13 
18:07:50.693760566 -0700:/var/crash/_usr_bin_kglobalaccel5.1000.crash
   640:1000:110:67420:2024-04-14 16:48:23.876370506 -0700:2024-04-14 
16:48:15.949370506 
-0700:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_kf5_kscreen_backend_launcher.1000.crash
   640:0:110:3008619:2024-04-13 18:07:49.462760566 -0700:2024-04-13 
18:07:48.476760566 -0700:/var/crash/_usr_lib_xorg_Xorg.0.crash
   640:1000:110:804462:2024-04-15 16:12:24.216622864 -0700:2024-04-15 
16:12:22.556154331 
-0700:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_kf5_kioslave5.1000.crash
   640:1000:110:899579:2024-04-13 18:07:48.448760566 -0700:2024-04-13 
18:07:47.003760566 
-0700:/var/crash/_usr_lib_x86_64-linux-gnu_kconf_update_bin_konsole_show_menubar.1000.crash
  CurrentDesktop: KDE
  Date: Mon Apr 15 16:15:04 2024
  InstallationDate: Installed on 2024-04-14 (2 days ago)
  InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240411.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  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/2061696/+subscriptions


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

[Desktop-packages] [Bug 2061696] [NEW] Trying to setup a google account in settings

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In settings. When I select Online accounts and then google the system
logs me right out to the login screen.

What should happen after clicking Google it should allow me to login to
my Google account or gdrive.

This is running in a VM.

Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-22-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 3.8 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-7.2

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.12
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
CrashDB: ubuntu
CrashReports:
 640:1000:110:680234:2024-04-13 18:07:51.785760566 -0700:2024-04-13 
18:07:50.693760566 -0700:/var/crash/_usr_bin_kglobalaccel5.1000.crash
 640:1000:110:67420:2024-04-14 16:48:23.876370506 -0700:2024-04-14 
16:48:15.949370506 
-0700:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_kf5_kscreen_backend_launcher.1000.crash
 640:0:110:3008619:2024-04-13 18:07:49.462760566 -0700:2024-04-13 
18:07:48.476760566 -0700:/var/crash/_usr_lib_xorg_Xorg.0.crash
 640:1000:110:804462:2024-04-15 16:12:24.216622864 -0700:2024-04-15 
16:12:22.556154331 
-0700:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_kf5_kioslave5.1000.crash
 640:1000:110:899579:2024-04-13 18:07:48.448760566 -0700:2024-04-13 
18:07:47.003760566 
-0700:/var/crash/_usr_lib_x86_64-linux-gnu_kconf_update_bin_konsole_show_menubar.1000.crash
CurrentDesktop: KDE
Date: Mon Apr 15 16:15:04 2024
InstallationDate: Installed on 2024-04-14 (2 days ago)
InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240411.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade noble
-- 
Trying to setup a google account in settings
https://bugs.launchpad.net/bugs/2061696
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-control-center in Ubuntu.

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

[Desktop-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

[Martin Wimpress ]

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: Triaged => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: In Progress => Fix Committed

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Fix Committed
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+subscriptions


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

[Desktop-packages] [Bug 2061847] [NEW] Thunderbird: incomplete migration to snap

[Romwriter]

Public bug reported:

Thunderbird has migrated to snap, but the thunderbird package does not
depend on the snap package.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: thunderbird 2:1snap1-0ubuntu1
Uname: Linux 6.8.6-060806-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Tue Apr 16 16:35:36 2024
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

** Affects: thunderbird (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 thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2061847

Title:
  Thunderbird: incomplete migration to snap

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Thunderbird has migrated to snap, but the thunderbird package does not
  depend on the snap package.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: thunderbird 2:1snap1-0ubuntu1
  Uname: Linux 6.8.6-060806-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Apr 16 16:35:36 2024
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

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


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

[Desktop-packages] [Bug 2061381] Re: Update pipewire to 1.0.5

[Bug Watch Updater]

** Changed in: pipewire (Debian)
   Status: New => Fix Released

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

Title:
  Update pipewire to 1.0.5

Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire package in Debian:
  Fix Released

Bug description:
  pipewire 1.0.5 is a bugfix release in the stable 1.0 series.

  It allows me to use the Snapshot webcam app with my external USB
  camera if I plug it in after logging in. (I have other issues with
  Snapshot, but this is still an improvement.) Snapshot is included by
  default in the Ubuntu 24.04 LTS Desktop "expanded" installation.

  https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/1.0.5

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


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

[Desktop-packages] [Bug 2059796] Re: Other Software > Remove button doesn't work

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.99.47

---
software-properties (0.99.47) noble; urgency=medium

  * Fix failed removal of Deb822 formated source in "Other Software" tab
(LP: #2059796).

 -- Nathan Pratta Teodosio   Tue, 09 Apr
2024 09:02:50 +0200

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Other Software > Remove button doesn't work

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Test Case
  -
  - Add a PPA with apt-add-repository, not with software-properties (we want a 
deb822 format for the test).
  - Open the Software & Updates tab
  - Switch to the Other Software tab
  - Select the PPA line and click Remove
  - After Authentication, nothing happens.

  No error is emitted to the command line. The repo line still shows.
  The repo is still in /etc/apt/sources.list.d/

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.44
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Uname: Linux 6.8.0-20-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 12:06:07 2024
  InstallationDate: Installed on 2022-04-06 (723 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago)

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


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

[Desktop-packages] [Bug 2061381] Re: Update pipewire to 1.0.5

[Launchpad Bug Tracker]

This bug was fixed in the package pipewire - 1.0.5-1

---
pipewire (1.0.5-1) unstable; urgency=medium

  [ Dylan Aïssi ]
  * New upstream release (Closes: #1069033, LP: #2061381)
  * Refresh patches
  * Drop patch included in upstream release:
  - 64-bit-time-t-compat.patch

  [ Jeremy Bícha ]
  * Revert "Temporarily disable Snap integration on 32-bit non-x86"
  * Revert "Temporarily disable libffado integration on 32-bit non-x86"

pipewire (1.0.4-3) unstable; urgency=medium

  * Team upload

  [ Michael Hudson-Doyle ]
  * s/libpipewire-0.3-0/libpipewire-0.3-0t64/ in the shlibs.local files

  [ Simon McVittie ]
  * Only build Snap integration on supported architectures.
According to Snap documentation, only these architectures are
supported, so enabling the others is unlikely to be particularly
useful. Reducing the architecture list reduces the impact of any
non-portability in snapd-glib.
  * Temporarily disable Snap integration on 32-bit non-x86.
snapd-glib has not yet been rebuilt for the 64-bit time_t transition.
This change should be reverted after snapd-glib is rebuilt.
  * Temporarily disable libffado integration on 32-bit non-x86.
Same reasoning as for snapd-glib, above.
(Closes: #1067558)

 -- Jeremy Bícha   Mon, 15 Apr 2024 21:08:58 +0200

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

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

Title:
  Update pipewire to 1.0.5

Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire package in Debian:
  New

Bug description:
  pipewire 1.0.5 is a bugfix release in the stable 1.0 series.

  It allows me to use the Snapshot webcam app with my external USB
  camera if I plug it in after logging in. (I have other issues with
  Snapshot, but this is still an improvement.) Snapshot is included by
  default in the Ubuntu 24.04 LTS Desktop "expanded" installation.

  https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/1.0.5

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


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

[Desktop-packages] [Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed

[Olivier Gayot]

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on
  target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme-
  stas,shim-signed

Status in subiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  verison：ubuntu 24.04 subiquity version
  OS:noble-live-server-amd64-0222.iso
  CPU:AMD EPYC 9634 84-Core Processor*1
  MEMORY: M321R2GA3BB6-CQKVG*2
  ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
  UEFI MODE

  lsb_release -rd: Description:Untun Noble Numbat(development branch)
  Release: 24.04

  What you expected to happen:
  Install os on nvme,expected to install succefully.

  What happened instead:
  Install os on nvme, install always failed.
  Before installation, we cleaned up all our nvme disk by dd if=/dev/zero 
of=/dev/sda bs=1M count=5

  The error log:
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on 
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed', 
'nvme-cli', 'nvme-stas', 'shim-signed']
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages: 
FAIL: installing missing packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: 
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command 
curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback 
(most recent call last):
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py", 
line 202, in main
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret = 
args.func(args)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1998, in curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
builtin_curthooks(cfg, target, state)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1803, in builtin_curthooks
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
install_missing_packages(cfg, target, osfamily=osfamily)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
 line 1362, in install_missing_packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
distro.install_packages(to_add, target=target, osfamily=osfamily)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472, 
in install_packages
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
install_cmd('install', args=pkglist, opts=opts, target=target,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254, 
in run_apt_command
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv = 
apt_install(mode, args, opts=opts, env=env, target=target,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302, 
in apt_install
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv = 
inchroot.subp(cmd + dl_opts + packages, env=env,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791, 
in subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
subp(*args, **kwargs)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283, 
in subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return 
_subp(*args, **kwargs)
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:   File 
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147, 
in _subp
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise 
ProcessExecutionError(stdout=out, stderr=err,
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: 
curtin.util.ProcessExecutionError: Unexpected error while running command.
  Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:  

[Desktop-packages] [Bug 2060296] Re: Cursor missing in aera screeshot - 22.04 wayland

[Paul White]

** Package changed: gnome (Ubuntu) => gnome-screenshot (Ubuntu)

** Tags added: jammy

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

Title:
  Cursor missing in aera screeshot - 22.04 wayland

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Whether I use gnome-screeshot 4.1-2 or embedded Ubuntu capture tool in
  Jammy 22.04 to capture only a part of a window, then I can't get the
  capture to show the cursor.

  Embedded Ubuntu tool always shows a "cross cursor" to move the
  selected aera, which prevents to capture the particular shape of the
  cursor within the aera, and has not the timer option that would allow
  to hoover over the very zone I wan't to show the cursor when on it
  (Although I can hit the Enter or Space key to start the capture - not
  documented)).

  gnome-screenshot has the time option but fails to capture the cursor.
  Cursor capture only works in fullscreen or window modes.

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


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

[Desktop-packages] [Bug 2060296] [NEW] Cursor missing in aera screeshot - 22.04 wayland

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Whether I use gnome-screeshot 4.1-2 or embedded Ubuntu capture tool in
Jammy 22.04 to capture only a part of a window, then I can't get the
capture to show the cursor.

Embedded Ubuntu tool always shows a "cross cursor" to move the selected
aera, which prevents to capture the particular shape of the cursor
within the aera, and has not the timer option that would allow to hoover
over the very zone I wan't to show the cursor when on it (Although I can
hit the Enter or Space key to start the capture - not documented)).

gnome-screenshot has the time option but fails to capture the cursor.
Cursor capture only works in fullscreen or window modes.

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

-- 
Cursor missing in aera screeshot - 22.04 wayland
https://bugs.launchpad.net/bugs/2060296
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-screenshot in Ubuntu.

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

[Desktop-packages] [Bug 2061819] Re: gnome-shell is very slow

[Jeremy Bícha]

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

** This bug has been marked a duplicate of bug 2059847
   Input lag or freezes on Nvidia desktops with X11 after logging 
"MetaSyncRing: Sync object is not ready -- were events handled properly?"

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

Title:
  gnome-shell is very slow

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  the computer is running normally but the gnome-center and the gnome-
  shell are very slow, the ls command now time to run

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 12:56:15 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-01-17 (89 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2061827] Re: Resizing app window can trigger tilling highlighter

[Launchpad Bug Tracker]

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

** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu)
   Status: New => Confirmed

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

Title:
  Resizing app window can trigger tilling highlighter

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when resizing apps windows, it show the tilling highlighter
  as shown in the screenshot and it stays like that until you try to
  tile a window manually.

  It's only a view but you can still click what's behind it.

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 13:28:07 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-03-22 (25 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.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 2024-04-11 (5 days ago)

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


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

[Desktop-packages] [Bug 2061827] Re: Resizing app window can trigger tilling highlighter

[Launchpad Bug Tracker]

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

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

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

Title:
  Resizing app window can trigger tilling highlighter

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when resizing apps windows, it show the tilling highlighter
  as shown in the screenshot and it stays like that until you try to
  tile a window manually.

  It's only a view but you can still click what's behind it.

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 13:28:07 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-03-22 (25 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.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 2024-04-11 (5 days ago)

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


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

[Desktop-packages] [Bug 2061827] Re: Resizing app window can trigger tilling highlighter

[Jeremy Bícha]

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

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

Title:
  Resizing app window can trigger tilling highlighter

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when resizing apps windows, it show the tilling highlighter
  as shown in the screenshot and it stays like that until you try to
  tile a window manually.

  It's only a view but you can still click what's behind it.

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 13:28:07 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-03-22 (25 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.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 2024-04-11 (5 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-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]

[cam]

I can try 6.7.9 and 6.7.12.

What you described vaguely sounds like the stuff I'm doing when it 
breaks on me so I'll try that too!

I might have some time to do this tomorrow night.

I've wondered if this is a firmware issue as well. Here are my md5sums 
for my files:
af5adf85ef96839ae1aa79bc916f1b91  TAS2XXX387D.bin
951a483a58b1b41e5114f0c0746f583a  TAS2XXX387E.bin
f7f319ba68ab37e093381360e2bdefff  TAS2XXX3881.bin
dfb907ce0135030182704cabb1223465  TAS2XXX3884.bin
a7ebbd19c73cd6fea005bcab025f4921  TAS2XXX3886.bin
f1f0486569020316a7b3253db17c6b94  TAS2XXX38A7.bin
b796beae38a02fa27426560742a829b6  TAS2XXX38A8.bin
830cf65b0d6e2355b70b9ed364b4819d  TAS2XXX38B8.bin
2a4d57199bc04ebc2dd9880f7afee4a7  TAS2XXX38B9.bin
fcaa167bb712cbe7829ae41f9ea7bfa0  TAS2XXX38BA.bin
9a6089a79ef6038691733a18c94c1005  TAS2XXX38BB.bin
0ace13d455c64d5043ac2ee066555f20  TAS2XXX38BE.bin
a90c1c801076cf6f2acfd6edf83e7575  TAS2XXX38BF.bin
3723cbf4848c3df69cd870314817aada  TAS2XXX38C3.bin
dfb907ce0135030182704cabb1223465  TAS2XXX38CB.bin
a7ebbd19c73cd6fea005bcab025f4921  TAS2XXX38CD.bin
33c27f3eec9e46e1e487b0fc4b781725  TIAS2781RCA2.bin
4824e06b5919b577d4671a3dd40fbda4  TIAS2781RCA2.json
61dcfeb8c3dd4c5b922dbbe8d826d2ef  TIAS2781RCA4.bin
38f473162f7dd3546db9ee561fb560bf  TIAS2781RCA4.json

I've considered and looking at the latest files in the linux-firmware 
git repo, but haven't had time yet.


On 4/15/2024 10:19 PM, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #855 from dreamsyn...@gmail.com ---
>> ...it makes me think maybe our problems are symptoms of the same issue
> I agree. I am using endeavour os, but I've also verified my scenario on
> nobara (fedora based).
>
> I found I can somewhat reliably get the audio to fail on 6.8.5 by leaving
> the system muted for a few minutes. Additionally something I noticed on
> 6.8.0 is running a video in a Firefox based browser (I used Librewolf),
> pausing and unpausing could lead to the sound being permanently disabled
> for the whole system until reboot.
>
> I am not self compiling, just using the arch linux and linux-headers
> packages. If this bug tracker is for debian/ubu based distros only, my bad.
> The issue is reproducible regardless.
> I can only confirm that I experience no issue on 6.7.9 on fedora based
> distros and arch. I think I had no luck using 6.7.9 on linux mint (using
> mainline kernel), but I assume it is because of an outdated linux-firmware
> package.
>
> If it isn't a pain for you to test, could you try 6.7.9 and see if you
> experience no issues as well?
>

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

[Desktop-packages] [Bug 1958019]

[soyer]

The firmware files have not changed.

I think it's possible that this commit is the culprit:
https://github.com/torvalds/linux/commit/bec7760a6c5fa59593dac264fa0c628e46815986

Sorry about that, it works fine with tas2563, but I couldn't test it with 
tas2781.
Something related to power management can cause this also.

Please try the following and report if it fixes the issue:

amixer -c 1 cset numid=3,name='Speaker Force Firmware Load' 1

It is possible that the -c 1 and the numid parameters are not exactly
these, they can be obtained from `amixer -c 1 contents` or `amixer -c 0
contents`.

Thanks,
Gergo

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

[cam]

(In reply to dreamsyntax from comment #853)
> Hi, just confirming that on:
> Lenovo Legion Pro 7i (Gen 8 / 2023) the no sound issue has regressed again
> on 6.8.5.
> 
> Last working version without any issues is 6.7.9 - which is odd considering
> the original post lists this as not a regression?
> 
> alsamixer shows ALC287 under system info.
> 
> 
> 6.8.2-6.8.4 have no audio for me.
> 6.8.5 has audio on reboot, but after a seemingly random amount of time the
> audio will no longer function until next reboot.
> 
> 6.7.9 works at all times for me.

I also have the Legion Pro 7i Gen 8 16IRX8H, sound worked through all
those kernel versions for me... But I do have another problem I wonder
if it's related... Occasionally, my sound will just stop working. I
can't get it working until I reboot... This tends to happen at a rate of
less than once per day.

Last time it happened was yesterday. This time I decided to enable
hibernate to see if resume from that would restore my sound (resuming
from sleep doesn't work).

Anyway, the issue didn't happen to me for about a month... and then
happened to me twice recently. Maybe it started around 6.8.4 or 6.8.5?
When it happened yesterday, I was on 6.8.6.

The problem is so intermittent it's hard to pin it down to it starting
with a specific kernel version...

But it makes me think maybe our problems are symptoms of the same issue.

How are you getting recent kernels? Are you self compiling? Are you
using the Ubuntu mainline repo? Something else and/or some other distro
entirely?

I'm compiling my own.

When this happens, audacious gives me some ALSA input/output error. I
suspect some hook to tell the amps to wake up and play audio through the
speakers hangs, but that's all I've got so far.

But sound issues related to TI's smart amps are definitely unrelated to
this bug we're posting in. Someone should start a new bug for these
issues if we hope to get more support.

-- 
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: 

[Desktop-packages] [Bug 1958019]

[dreamsyntax]

Created attachment 306161
attachment-31010-0.html

> ...it makes me think maybe our problems are symptoms of the same issue

I agree. I am using endeavour os, but I've also verified my scenario on
nobara (fedora based).

I found I can somewhat reliably get the audio to fail on 6.8.5 by leaving
the system muted for a few minutes. Additionally something I noticed on
6.8.0 is running a video in a Firefox based browser (I used Librewolf),
pausing and unpausing could lead to the sound being permanently disabled
for the whole system until reboot.

I am not self compiling, just using the arch linux and linux-headers
packages. If this bug tracker is for debian/ubu based distros only, my bad.
The issue is reproducible regardless.
I can only confirm that I experience no issue on 6.7.9 on fedora based
distros and arch. I think I had no luck using 6.7.9 on linux mint (using
mainline kernel), but I assume it is because of an outdated linux-firmware
package.

If it isn't a pain for you to test, could you try 6.7.9 and see if you
experience no issues as well?

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

[dreamsyntax]

Hi, just confirming that on:
Lenovo Legion Pro 7i (Gen 8 / 2023) the no sound issue has regressed again on 
6.8.5.

Last working version without any issues is 6.7.9 - which is odd
considering the original post lists this as not a regression?

alsamixer shows ALC287 under system info.


6.8.2-6.8.4 have no audio for me.
6.8.5 has audio on reboot, but after a seemingly random amount of time the 
audio will no longer function until next reboot.

6.7.9 works at all times for me.

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

[tuupic]

(In reply to admin from comment #851)
> Can confirm on Endeavour 6.8.5 that my Legion Slim 7 16arha7 has working
> speakers now! yay! Lets hope they don't break again...

Does internal microphone work in your OS ?

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

[admin]

Can confirm on Endeavour 6.8.5 that my Legion Slim 7 16arha7 has working
speakers now! yay! Lets hope they don't break again...

-- 
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 2061827] [NEW] Resizing app window can trigger tilling highlighter

[Islam]

Public bug reported:

Sometimes when resizing apps windows, it show the tilling highlighter as
shown in the screenshot and it stays like that until you try to tile a
window manually.

It's only a view but you can still click what's behind it.

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: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 13:28:07 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-03-22 (25 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
 LANG=en_US.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 2024-04-11 (5 days ago)

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


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

** Attachment added: "Screenshot from 2024-04-16 13-27-10.png"
   
https://bugs.launchpad.net/bugs/2061827/+attachment/5766118/+files/Screenshot%20from%202024-04-16%2013-27-10.png

** Description changed:

- Sometimes when resizing apps windows, it show the tilling highlighter as 
shown in the screenshot.
- It only a view but you can still click what's behind it.
+ Sometimes when resizing apps windows, it show the tilling highlighter as
+ shown in the screenshot and it stays like that until you try to tile a
+ window manually.
+ 
+ It's only a view but you can still click what's behind it.
  
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 13:28:07 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-03-22 (25 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.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 2024-04-11 (5 days ago)

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

Title:
  Resizing app window can trigger tilling highlighter

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sometimes when resizing apps windows, it show the tilling highlighter
  as shown in the screenshot and it stays like that until you try to
  tile a window manually.

  It's only a view but you can still click what's behind it.

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 13:28:07 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-03-22 (25 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.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 2024-04-11 (5 days ago)

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


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

[Desktop-packages] [Bug 544639] Re: evince doesn't remember the window size

[betteropensource]

The problem is still present, almost 5 years have already passed, will
it be solved?

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

Title:
  evince doesn't remember the window size

Status in Evince:
  Expired
Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Lucid:
  Fix Released

Bug description:
  Currently uploaded in -proposed:

  evince (2.30.1-0ubuntu1) lucid-proposed; urgency=low

    * New upstream release:
  Bug fixes:
  - Make inverted colors mode work in presentation mode too
    (#614693, Carlos Garcia Campos)
  - Respect GNOME22_USER_DIR env variable (#613637, Ray Strode)
  - Fix loading of local documents when uri contains a page
    destination (#616515, Carlos Garcia Campos)
  - Take default settings from last document opened. Fixes
    regression caused by migration to gio metadata (#606090, Carlos
    Garcia Campos) (LP: #544639, #503372)
  - Update icons to match gnome-icon-theme appearance (#614747,
    Hylke Bons, Carlos Garcia Campos)
  - Make sure there's a new valid page range before updating caches
    (fdo#27599, Carlos Garcia Campos)
  - Update FSF address everywhere (#514607, Arun Persaud)
  - Fix loading of compressed password-protected documents (#613959,
    Carlos Garcia Campos)
  - Close previewer window with control + w (#612972, Carlos Garcia
    Campos)
  - Fix keybindings in previewer window (#612972, Carlos Garcia
    Campos)
  Translation updates

  Test Case:
  install the new version of evince, try to open a pdf and go in preview mode.

  ---
  Binary package hint: evince

  evince starts with a small size and it doesn't remember the new size when
  resized, it only happens when opening it without a document, it does remember
  the size per document

  DistroRelease: Ubuntu 10.04

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


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

[Desktop-packages] [Bug 544639] Re: evince doesn't remember the window size

[betteropensource]

Evince 42.3 is still affected. (in Ubuntu 22.04 fresh install some weeks
ago...)

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

Title:
  evince doesn't remember the window size

Status in Evince:
  Expired
Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Lucid:
  Fix Released

Bug description:
  Currently uploaded in -proposed:

  evince (2.30.1-0ubuntu1) lucid-proposed; urgency=low

    * New upstream release:
  Bug fixes:
  - Make inverted colors mode work in presentation mode too
    (#614693, Carlos Garcia Campos)
  - Respect GNOME22_USER_DIR env variable (#613637, Ray Strode)
  - Fix loading of local documents when uri contains a page
    destination (#616515, Carlos Garcia Campos)
  - Take default settings from last document opened. Fixes
    regression caused by migration to gio metadata (#606090, Carlos
    Garcia Campos) (LP: #544639, #503372)
  - Update icons to match gnome-icon-theme appearance (#614747,
    Hylke Bons, Carlos Garcia Campos)
  - Make sure there's a new valid page range before updating caches
    (fdo#27599, Carlos Garcia Campos)
  - Update FSF address everywhere (#514607, Arun Persaud)
  - Fix loading of compressed password-protected documents (#613959,
    Carlos Garcia Campos)
  - Close previewer window with control + w (#612972, Carlos Garcia
    Campos)
  - Fix keybindings in previewer window (#612972, Carlos Garcia
    Campos)
  Translation updates

  Test Case:
  install the new version of evince, try to open a pdf and go in preview mode.

  ---
  Binary package hint: evince

  evince starts with a small size and it doesn't remember the new size when
  resized, it only happens when opening it without a document, it does remember
  the size per document

  DistroRelease: Ubuntu 10.04

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


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

[Desktop-packages] [Bug 2061299] Re: Thinkpad T510 24.04 beta hangs on live CD

[Rob Peters]

Yes, safe boot boots correctly and that is where I did the dmesg.
Is there anything I can try to help eliminate possibilities?

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

Title:
  Thinkpad T510 24.04 beta hangs on live CD

Status in mesa package in Ubuntu:
  New

Bug description:
  Booting with UB 24.04 CD on Thinkpad T510.  Budgie graphics are missing on 
boot, just test "Ubuntu Budgie 24.04".
  Once desktop is loaded a hard freeze.  If one selects the boot option "Safe 
graphics" then the boot completes and liveCD is functional without lockup

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: mesa-vulkan-drivers 24.0.3-1ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr 14 15:21:51 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
  MachineType: LENOVO 4384AJ9
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset --- quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.release: 1.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET92WW (1.52 )
  dmi.board.name: 4384AJ9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4384AJ9:pvrThinkPadT510:rvnLENOVO:rn4384AJ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4384AJ9
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2061819] [NEW] gnome-shell is very slow

[Bruno]

Public bug reported:

the computer is running normally but the gnome-center and the gnome-
shell are very slow, the ls command now time to run

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 12:56:15 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-01-17 (89 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
RelatedPackageVersions: mutter-common 42.9-0ubuntu7
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  gnome-shell is very slow

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  the computer is running normally but the gnome-center and the gnome-
  shell are very slow, the ls command now time to run

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 12:56:15 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-01-17 (89 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2061618] Re: MIPI camera does not work

[Sebastien Bacher]

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report. We understand the difficulties you are
facing, but it is better to raise problems you are having in the support
tracker at https://answers.launchpad.net/ubuntu if you are uncertain if
they are bugs. If you would prefer live chat support, you can find an
IRC support channel for your flavor of Ubuntu here:
https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with
your problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs.

** Changed in: software-properties (Ubuntu)
   Status: New => Invalid

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

Title:
  MIPI camera does not work

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  zoom app used - no working camera

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


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

[Desktop-packages] [Bug 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver

[Daniel van Vugt]

** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: Invalid => Fix Released

** Changed in: nvidia-graphics-drivers-545 (Ubuntu)
   Status: Invalid => Fix Released

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  GTK-ngl (new default backend) rendering issues with the nvidia 470
  driver

Status in GTK+:
  New
Status in gtk4 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Fix Released

Bug description:
  With nvidia driver, all GTK4 applications have label rendering issues.

  They are not refresh until passing the cursor over them, giving blank
  windows. The corner are white and not themed. Passing from one app
  scren to another one reproduces the issue.

  gnome-control-center or files, for instance, are blank by default.

  As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue.

  Related upstream bugs and discussions are:
  - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542

  
  --

  
  $ glxinfo
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  server glx vendor string: NVIDIA Corporation
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, 
  GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  client glx vendor string: NVIDIA Corporation
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, 
  GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, 
  GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_multisample_coverage, 
  GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, 
  GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  Memory info (GL_NVX_gpu_memory_info):
  Dedicated video memory: 4096 MB
  Total available memory: 4096 MB
  Currently available dedicated video memory: 3041 MB
  OpenGL vendor string: NVIDIA Corporation
  OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2
  OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06
  OpenGL core profile shading language 

[Desktop-packages] [Bug 2052913] Re: [Xorg] Large performance regression in fullscreen windows

[Daniel van Vugt]

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

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

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

Title:
  [Xorg] Large performance regression in fullscreen windows

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble 
(gnome-shell 45.3-1ubuntu1)
  Default Ubuntu GNOME desktop environment used with no user added extensions.

  GPU driverstack identical between the two distros (eliminated as a variable).
  Linux kernel identical between distros (eliminated as a variable)
  CPU, GPU, and RAM clocks pinned to max.

  Test case: Minecraft Java Edition (shared drive with identical setup
  between Ubuntu versions). Fullscreen 1080p. Xorg display server.

  FPS (uncapped):
  Ubuntu Jammy: 177fps
  Ubuntu Noble: 140fps

  Observations:
  Ubuntu Jammy:
  gnome-shell process cpu% when camera is still: 0-1%
  gnome-shell process cpu% when camera is moving: 10-20%
  Memory Bandwidth (CPU and GPU shared): 40%

  Ubuntu Noble:
  gnome-shell process cpu% when camera is still: 20-55%
  gnome-shell process cpu% when camera is moving: 30-55%
  Memory Bandwidth (CPU and GPU shared): 50%

  In both cases GPU utilization is observed to be near 100%.

  So in summary, large performance regression regression which appears
  to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on
  ubuntu jammy when there the camera is still (even with a fps graph
  drawn onscreen) in stark contrast to ubuntu noble.

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


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

[Desktop-packages] [Bug 2061153] Re: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined]

[Daniel van Vugt]

It's not just Hyper-V. For some reason I get the same bug whenever I
install the Nvidia 470 driver. And there's also bug 2061364.

** Summary changed:

- No login prompt after installing in HyperV
+ No login prompt or user list on login screen [JS ERROR: TypeError: 
this._button is undefined]

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

** Changed in: gnome-shell (Ubuntu)
Milestone: None => ubuntu-24.04

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

Title:
  No login prompt or user list on login screen [JS ERROR: TypeError:
  this._button is undefined]

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I installed the 24.04 beta ISO (the version from 2024-04-12) on a
  HyperV VM. Running through the installer itself seemed fine, but after
  rebooting GDM seemed to start but doesn't offer any users to login
  with. Not even an "Other" button. GDM itself has definitely started,
  as the current time is visible at the top of the screen, and the
  network and accessibility icons are visible at the top right of the
  screen. But the center of the screen is blank.

  If I manually mount the drive and examine the journal logs, I see a
  "JS Error" from gnome-shell that seems likely to be related:

  
  Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: Starting Authd!!!
  Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: JS ERROR: TypeError: 
this._button is undefined
  
_createSessionMenuButton@resource:///org/gnome/shell/gdm/loginDialog.js:663:13
  
_init@resource:///org/gnome/shell/gdm/loginDialog.js:589:14
  
LoginDialog@resource:///org/gnome/shell/gdm/loginDialog.js:487:4
  
_ensureUnlockDialog@resource:///org/gnome/shell/ui/screenShield.js:472:28
  
showDialog@resource:///org/gnome/shell/ui/screenShield.js:404:14
  
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:317:26
  
_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:764:18
  
_loadBackground/signalIdhttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061153/+subscriptions


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

[Desktop-packages] [Bug 2061364] Re: Remote login missing user list

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 2061153
   No login prompt or user list on login screen [JS ERROR: TypeError: 
this._button is undefined]

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

Title:
  Remote login missing user list

Status in gnome-remote-desktop package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Impact
  --
  When attempting to use Remote Login, the user list is missing from the login 
screen, making it impossible to log in

  Original Bug Report
  ---
  on 24.04 when RDP from a windows client it logs on but most of the gui dosnt 
load. There is some options for like poweroff /on but the have zero effect.

  Test Case
  -
  Remote Login at
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-remote-desktop 46.0-2
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 08:21:06 2024
  InstallationDate: Installed on 2024-04-14 (1 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: gnome-remote-desktop
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2061515] Re: gray screen presented upon rdp connection

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 2061364
   Remote login missing user list
** This bug has been marked a duplicate of bug 2061153
   No login prompt or user list on login screen [JS ERROR: TypeError: 
this._button is undefined]

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

Title:
  gray screen presented upon rdp connection

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

Bug description:
  When logging into a VM or a bare metal device running 24.04 over RDP
  Remote Login (new feature for gnome-remote-desktop 46), a gray screen
  is presented to the user. The time is written at the top, and there is
  the top bar controls for power off/restart etc, but no desktop icons
  are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-remote-desktop 46.0-2
  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: pass
  Date: Mon Apr 15 09:41:32 2024
  InstallationDate: Installed on 2024-04-12 (3 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: gnome-remote-desktop
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-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

[Daniel van Vugt]

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

1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

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

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

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

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

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

Title:
  crash in meta_wayland_transaction_commit

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/gnome-shell/+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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Daniel van Vugt]

https://salsa.debian.org/gnome-
team/mutter/-/commit/6cf0e31b3e23556edfbba7669f97935ba118895a

** Changed in: mutter (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
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 Committed
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 Committed

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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Daniel van Vugt]

The Nvidia driver version and Mutter version are unrelated to each other
so that doesn't sound like a problem.

-- 
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:
  In Progress
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:
  In Progress

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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Jan Visser]

I noticed another problem which makes me wonder if it's related to this.
When you unlock the keyring yourself it still fails to unlock ssh keys.

If you do:
$ export SSH_AUTH_SOCK=$XDG_RUNTIME_DIR/gcr/ssh
it starts working again.

Is this related or should I report a separate bug?

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  New
Status in gnome-keyring package in Ubuntu:
  Triaged

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 1825710] Re: Remove "Application is ready" notification

[Daniel van Vugt]

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

** Tags removed: fixed-in-gnome-shell-46
** Tags added: fixed-in-gnome-shell-46.rc

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

Title:
  Remove "Application is ready" notification

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

Bug description:
  The "Application is ready" notification is pointless, really. Say, I
  click on the open downloads folder button in Firefox and GNOME Shell
  gives me a notification saying "Application is ready" but doesn't open
  the notification. I'm totally expecting an app to open because I
  actively initiated it.

  As a workaround, I'm using a GNOME extensions "Focus my Window" which
  removes the "Application is ready" message and focuses the app window
  automatically. However, this cannot be treated as a solution.

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


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

[Desktop-packages] [Bug 2030963] Re: Window/app switcher highlights hard to see

[Daniel van Vugt]

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

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

Title:
  Window/app switcher highlights hard to see

Status in GNOME Shell:
  Fix Released
Status in Yaru Theme:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  In 22.04's default theme, it's almost impossible for me to make out
  which app or window is the currently selected one in the window
  switcher (alt-tab) or the application switcher (super-tab). The
  "highlighted" item is just a slightly different shade of grey. I mean,
  I can make it out if I squint at it, but ... that just isn't a
  *highlight*. This is a use where Ubuntu Orange shines, too. :-(

  "Ok, boomer, you're blind. I can see that just fine". Fair enough. Are
  you under thirty and (thus still) have 20:20 vision, by any chance?
  The point is, it isn't good UI design either way. What's worse, the
  high contrast accessibility setting doesn't touch any of it, and that
  is definitely a bug.

  ==

  EDIT: Rearranged the submission so that the bit this bug is meant to
  be primarily about is on top. The below bits are preserved so that the
  discussion still makes sense.

  Similarly, the active workspace in the workspace overview (?) does get
  an orange frame, but it's very thin, much too thin to see unless you
  look closely. Again, that's not a highlight. A highlight is supposed
  to pop out.

  In comparison, the highlighting for the current tab in Terminal is ok-
  ish. I'd *prefer* for the entire tab to become orange, or to become a
  lighter colour in addition to the orange bar, but it's usable.

  (I could go on. For example, windows' title bars are now white vs the iconic 
Ubuntu Brown, which makes it hard to tell where the title bar is vs the window 
contents. Many applications also have buttons in the title bar now. It's no 
longer possible to just grab a window and move it on auto-pilot ... If the 
title bar can't be a different colour any more, at least separate it with a 
thick line or something.
  In any case, 22.04 is a massive regression in terms of visual UI design vs 
18.04. Form should follow function, not the other way around.)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 10 12:58:31 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-02 (7 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1999924] Re: Unsupported buffer format 842094158 (NV12)

[Daniel van Vugt]

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

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Unsupported buffer format 842094158 (NV12)

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on
  Ubuntu 22.10 Wayland.

  When playing a h264 video, or a youtube video, I get:

  ```
  $ snap info chromium | grep installed
  installed:  107.0.5304.121-hwacc(2224) 171MB -
  $ chromium ~/sample.mp4
  Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality 
is provided by GTK natively. Please try to not load it.
  [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not 
supported, GL is egl, ANGLE is
  [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to 
initialize database.
  [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] 
libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: 
Unsupported buffer format 842094158

  Trace/breakpoint trap (core dumped)
  ```

  Test video: https://test-
  videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4

  I will try other hwacc versions and a non-hwacc version to see if they
  behave differently.

  OS: Ubuntu 22.10

  Desktop: Wayland

  GPU: Intel AlderLake-S GT1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+subscriptions


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

[Desktop-packages] [Bug 2036651] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from guess_category_value() from __dcigettext()

[Daniel van Vugt]

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

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from
  guess_category_value() from __dcigettext()

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

Bug description:
  Crash on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Sep 19 22:38:53 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-09-12 (7 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f706ee45e6d <__GI_getenv+77>:   cmp
(%rbx),%r12b
   PC (0x7f706ee45e6d) ok
   source "(%rbx)" (0x55fd90525) not located in a known VMA region (needed 
readable region)!
   destination "%r12b" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=name@entry=0x7f706efc0257 "LANGUAGE") at 
./stdlib/getenv.c:31
   guess_category_value (categoryname=0x7f706efa5493 <_nl_category_names+51> 
"LC_MESSAGES", category=5) at ./intl/dcigettext.c:1569
   __dcigettext (domainname=0x7f706f79e126 "glib20", msgid1=0x7f706f985c68 "The 
sockets address family to use for socket construction", msgid2=0x0, plural=0, 
n=0, category=5) at ./intl/dcigettext.c:647
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_type_class_ref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: Upgraded to mantic on 2023-09-18 (1 days ago)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg

[Daniel van Vugt]

** Changed in: mutter (Ubuntu Noble)
   Status: Fix Committed => 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/2054510

Title:
  Incomplete screen redraws in virtual machines running Xorg

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

Bug description:
  [ Impact ]

  When using software rendering on Xorg (so usually just in VMs), some
  parts of app windows may fail to redraw.

  https://gitlab.gnome.org/GNOME/mutter/-/issues/2880

  [ Test Plan ]

  1. Set up a virtual machine without graphics acceleration.
  2. Log into 'Ubuntu on Xorg'.
  3. Open Settings > About and verify Graphics = llvmpipe (or "Software 
Rendering"), and Windowing System = X11.
  4. sudo snap install chromium
  5. Open Chromium and find a web page with lots of text. Plain text without 
any links and staying at the top of the page will work best because you don't 
want to trigger any scrolling.
  6. Start selecting text with the mouse and while holding the button move the 
mouse up and down rapidly. Avoid triggering any page scrolling.
  7. Release the mouse button in roughly the middle of the area of text that 
was selected.
  8. Verify the remaining text selection is contiguous and not broken into 
multiple disconnected text selections (the bug).
  9. Repeat steps 7 and 8 several times to be sure.

  [ Where problems could occur ]

  The fix adds a new synchronization point between the compositor and X
  server. This should be inconsequential, although there is a "sync
  ring" in mutter used for this, and if a mistake occurs there then
  other parts of the desktop could appear to stop responding in Xorg
  sessions.

  [ Other Info ]

  This is a regression that started in 3.37.3 due to
  https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda.

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


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

[Desktop-packages] [Bug 2035096] Re: gnome-shell crashed with SIGSEGV in clutter_stage_emit_event()

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => 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/2035096

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

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

Bug description:
  https://errors.ubuntu.com/problem/ed14da5028cf683dd899169fc0c092c27703e62e
  https://errors.ubuntu.com/problem/13864618e249d119c794022eb8467fb70d7565cb
  https://errors.ubuntu.com/problem/430fb8d5733006abef7cc611f1b1ed57b0c6b0a5

  ---

  This occurred on startup - fresh system Chromebook HP G6 with
  Mr.Chromebook BIOS/UEFI. Installed from CD Image 23.10  release date -
  9/8/2023. No apparent issues after error.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 08:11:14 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-11 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   clutter_stage_process_event () from 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0
   _clutter_stage_process_queued_events () from 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_stage_process_event()
  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/mutter/+bug/2035096/+subscriptions


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

[Desktop-packages] [Bug 2036388] Re: Login screen grey background flickers

[Daniel van Vugt]

** Changed in: yaru-theme (Ubuntu)
   Status: Fix Committed => Fix Released

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

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

Title:
  Login screen grey background flickers

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Login screen grey background flickers on startup and again on login.
  It looks like it's trying to fade between two very similar shades of
  grey and there just aren't enough colours between them to fade
  smoothly.

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


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

[Desktop-packages] [Bug 2058005] Re: Black flicker on some systems between the login screen and desktop startup

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => 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/2058005

Title:
  Black flicker on some systems between the login screen and desktop
  startup

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  There is black flicker on some systems between the login screen and
  desktop startup.

  A fix is in progress:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3659

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


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

[Desktop-packages] [Bug 2042909] Re: keyboard backlight slider and automatic brightness causes gnome-shell to freeze (mostly on MacBooks)

[Daniel van Vugt]

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

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

Title:
  keyboard backlight slider and automatic brightness causes gnome-shell
  to freeze (mostly on MacBooks)

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

Bug description:
  Ubuntu 23.10
  Gnome Shell 45.0
  I expect gdm and the shell to be responsive but they freeze forcing me to 
reboot. Sometimes I'm able to use them but it takes some time to load.

  After taking a look at the journal, I see lots of messages like this:
  #0   564c4df768c8 i   resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 
@ 48)
  nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to run a JS callback 
during garbage collection. This is most likely caused by destroying a Clutter 
actor or GTK widget with ::destroy signal connected, or using the destroy(), 
dispose(), or remove() vfuncs. Because it would crash the application, it has 
been blocked.
 The offending callback was 
AsyncReadyCallback().
 == Stack trace for context 
0x564c4deaab90 ==
 #0   564c4df768c8 i   
resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48)
  nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
 The offending signal was 
g-properties-changed on GDBusProxy 0x564c4fec8670.
 == Stack trace for context 
0x564c4deaab90 ==

  On successful boots this seems to auto resolve, being followed by this 
message:
  nov 07 09:21:56 perseus dbus-daemon[1758]: [session uid=1000 pid=1758] 
Successfully activated service 'org.freedesktop.impl.portal.desktop.gnome'
  nov 07 09:21:56 perseus systemd[1722]: Started 
xdg-desktop-portal-gnome.service - Portal service (GNOME implementation).

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


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

[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

[Daniel van Vugt]

** Changed in: mutter (Ubuntu Noble)
   Status: Fix Committed => 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/2051074

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Mantic:
  Fix Released
Status in mutter source package in Noble:
  Fix Released

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

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


-- 
Mailing list: https://launchpad.net/~desktop-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?"

[Robin Bonicel]

I opened a similar bug and @vanvugt advised me to come here. 
I read everything and will try the PPA if need be. 

But I'm using a driver that nobody mentioned, which was selected by Dell who 
assembled the machine and installed the OS.
On Nvidia driver section, I'm using "Set the power ondemand mode by default 
from oem-fix-gfx-nvidia-ondemandmode". I also have drives 535 and 470 available 
in the menu, but when I install them, my default setting disappears. I had to 
fully reinstall the OS to get it back. Nvidia themselves advise on their 
download page to not necessarily use their proprietary drivers on some Linux 
distribs, so I stuck with my default driver. 

Will the PPA and the mutter downgrade be of use with this default setting ?
Also, installing proprietary pilot from the Software & update menu raised an 
error, so I aborted the process.

I'm running :

- Ubuntu 22.4.04 LTS
- GNOME 42.9 (latest official update)
- X11
- NVIDIA T400 4GB  

Thank you

-- 
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:
  In Progress
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:
  In Progress

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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Daniel van Vugt]

On second thoughts, 46.1 might not make it into the main release so
let's patch this in for Noble.

** Changed in: mutter (Ubuntu Noble)
   Status: Fix Committed => In Progress

-- 
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:
  In Progress
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:
  In Progress

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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Nathan Teodosio]

This is unlikely to be a problem in Gnome Keyring, as SDDM has no
problem unlocking in on log-in. I'm therefore adding here GDM3.

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

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

** No longer affects: gdm (Ubuntu)

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  New
Status in gnome-keyring package in Ubuntu:
  Triaged

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver

[Didier Roche-Tolomelli]

Confirming that it’s fixed on the same machine with 550.

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

Title:
  GTK-ngl (new default backend) rendering issues with the nvidia 470
  driver

Status in GTK+:
  New
Status in gtk4 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Invalid

Bug description:
  With nvidia driver, all GTK4 applications have label rendering issues.

  They are not refresh until passing the cursor over them, giving blank
  windows. The corner are white and not themed. Passing from one app
  scren to another one reproduces the issue.

  gnome-control-center or files, for instance, are blank by default.

  As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue.

  Related upstream bugs and discussions are:
  - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542

  
  --

  
  $ glxinfo
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  server glx vendor string: NVIDIA Corporation
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, 
  GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  client glx vendor string: NVIDIA Corporation
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, 
  GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, 
  GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_multisample_coverage, 
  GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, 
  GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  Memory info (GL_NVX_gpu_memory_info):
  Dedicated video memory: 4096 MB
  Total available memory: 4096 MB
  Currently available dedicated video memory: 3041 MB
  OpenGL vendor string: NVIDIA Corporation
  OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2
  OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06
  OpenGL core profile shading language version string: 4.60 NVIDIA
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, 
  GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, 
  GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, 
  GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, 
  GL_ARB_arrays_of_arrays, GL_ARB_base_instance,