[Desktop-packages] [Bug 2040977] Re: [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating on screen

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Status: Triaged => 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/2040977

Title:
  [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating
  on screen

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Using the touchpad on an X1 Carbon G10 with 90Hz OLED the mouse cursor
  stutters, unless something else is changing on screen (like running
  glmark2-wayland).

  Workaround:

  Put this in /etc/environment:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 15:48:28 2023
  InstallationDate: Installed on 2023-10-23 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only

[Daniel van Vugt]

I think this might be Ryzen bug 2034619. Can you try the workaround
mentioned there?

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => 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/2042973

Title:
   Desktop becomes unusable after changing window from fullscreen games
  on Wayland Only

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description: Ubuntu 23.10
  Release: 23.10
  gnome-shell 45.0-1ubuntu2

  Steps to reproduce:
  1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from 
steam, both using DXVK)
  2)Wait for them to fully load
  3)Press the Super button in order to go back to the desktop

  What should happen: A list of windows, the gnome desktop overview, is shown
  What happened: All the screen section from above the gnome taskbar became 
grey like the activity overview accent color and nothing else can be done, the 
desktop functionality is broken
  -

  Since I upgraded from 23.04 to 23.10 the desktop becomes unusable
  (video attached) 80% of the times when I switch from certain
  fullscreen games to the desktop using the super button.

  The gray color of the activity overview is shown above the shell
  taskbar on both screens and nothing else can be done.

  - The issue does not happen on an X11 session.
  - The notifications still work correctly, as clicking the gnome shell bar or 
even locking and unlocking the screen.
  - Right clicking and closing apps work. However, only the buttons from the 
shell itself only
  - Everything involving actively changing windows does not.
  - No matter the screen configuration the issue still persist.

  Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck.

  No workaround is discovered. Session can be terminated from the
  taskbar, as it works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 19:47:42 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-12 (87 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days ago)

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


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

[Desktop-packages] [Bug 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only

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

Title:
   Desktop becomes unusable after changing window from fullscreen games
  on Wayland Only

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description: Ubuntu 23.10
  Release: 23.10
  gnome-shell 45.0-1ubuntu2

  Steps to reproduce:
  1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from 
steam, both using DXVK)
  2)Wait for them to fully load
  3)Press the Super button in order to go back to the desktop

  What should happen: A list of windows, the gnome desktop overview, is shown
  What happened: All the screen section from above the gnome taskbar became 
grey like the activity overview accent color and nothing else can be done, the 
desktop functionality is broken
  -

  Since I upgraded from 23.04 to 23.10 the desktop becomes unusable
  (video attached) 80% of the times when I switch from certain
  fullscreen games to the desktop using the super button.

  The gray color of the activity overview is shown above the shell
  taskbar on both screens and nothing else can be done.

  - The issue does not happen on an X11 session.
  - The notifications still work correctly, as clicking the gnome shell bar or 
even locking and unlocking the screen.
  - Right clicking and closing apps work. However, only the buttons from the 
shell itself only
  - Everything involving actively changing windows does not.
  - No matter the screen configuration the issue still persist.

  Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck.

  No workaround is discovered. Session can be terminated from the
  taskbar, as it works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 19:47:42 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-12 (87 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days ago)

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


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

[Desktop-packages] [Bug 2042993] Re: overview sometimes stuck after pressing super

[Daniel van Vugt]

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

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

** This bug has been marked a duplicate of bug 2042973
Desktop becomes unusable after changing window from fullscreen games on 
Wayland Only

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

Title:
  overview sometimes stuck after pressing super

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I press super a lot to see progress of other applications or the system time 
from activities overview when in a fullscreen application, such as a steam game.
  Occasionally the activities overview will not show any applications nor the 
desktop, but only the gray background and the search bar (although applications 
on the dock will still be visible and selectable, just not interactable other 
than audio). The clock and quick settings are the only things that work 
normally in this state as not even the activities search bar is responsive. The 
only way I've been able to exit is by restarting the computer. I'm going to try 
using Xorg to restart gnome next time but I've not tested that yet.
  This issue hasn't seemed to occur in any situations other than running full 
screen applications. Although, given that I don't often use activities overview 
outside of fullscreen apps, that may not be required for the bug to occur.
  This bug started after upgrading to Ubuntu 23.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 23:01:44 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-03 (553 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-17 (22 days ago)

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


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

[Desktop-packages] [Bug 2042972] Re: Apps take minutes to launch

[Daniel van Vugt]

Can you say which apps exactly are affected?

** Summary changed:

- Display perfomance issue
+ Apps take minutes to launch

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

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

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

Title:
  Apps take minutes to launch

Status in Ubuntu:
  Incomplete

Bug description:
  After booting, sometimes I am not able to quickly open apps, it takes
  more than 5 mins to launch and in most of them dark mode is not shown.
  It used to come back to normal but now it stays the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-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  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 00:11:58 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TigerLake-H GT1 [UHD Graphics] [1043:13fc]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GA107M [GeForce RTX 3050 Mobile] 
[1043:13fc]
  InstallationDate: Installed on 2023-10-29 (9 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=5188fb64-a6dc-4300-a704-0666d8ca03ba ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2023
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FX506HCB.313
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506HCB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX506HCB.313:bd03/03/2023:br5.19:efr3.11:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506HCB_FX506HCB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506HCB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506HCB_FX506HCB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  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.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu

[Mate Kukri]

** Also affects: mesa (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Noble)
   Importance: Undecided
   Status: Confirmed

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

Title:
  GPU acceleration via VirGL is broken in qemu

Status in Release Notes for Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Mantic:
  New
Status in mesa source package in Noble:
  Confirmed

Bug description:
  This was reported by someone else upstream and is already fixed by
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions


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

[Desktop-packages] [Bug 2042972] Re: Display perfomance issue

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

A support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. 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, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  Display perfomance issue

Status in xorg package in Ubuntu:
  New

Bug description:
  After booting, sometimes I am not able to quickly open apps, it takes
  more than 5 mins to launch and in most of them dark mode is not shown.
  It used to come back to normal but now it stays the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-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  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 00:11:58 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TigerLake-H GT1 [UHD Graphics] [1043:13fc]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GA107M [GeForce RTX 3050 Mobile] 
[1043:13fc]
  InstallationDate: Installed on 2023-10-29 (9 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=5188fb64-a6dc-4300-a704-0666d8ca03ba ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2023
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FX506HCB.313
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506HCB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX506HCB.313:bd03/03/2023:br5.19:efr3.11:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506HCB_FX506HCB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506HCB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506HCB_FX506HCB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  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.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2042993] [NEW] overview sometimes stuck after pressing super

[Emeris Anders Mattson]

Public bug reported:

I press super a lot to see progress of other applications or the system time 
from activities overview when in a fullscreen application, such as a steam game.
Occasionally the activities overview will not show any applications nor the 
desktop, but only the gray background and the search bar (although applications 
on the dock will still be visible and selectable, just not interactable other 
than audio). The clock and quick settings are the only things that work 
normally in this state as not even the activities search bar is responsive. The 
only way I've been able to exit is by restarting the computer. I'm going to try 
using Xorg to restart gnome next time but I've not tested that yet.
This issue hasn't seemed to occur in any situations other than running full 
screen applications. Although, given that I don't often use activities overview 
outside of fullscreen apps, that may not be required for the bug to occur.
This bug started after upgrading to Ubuntu 23.10.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 23:01:44 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-05-03 (553 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45.0-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-10-17 (22 days ago)

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


** Tags: amd64 apport-bug mantic

** Attachment added: "Screenshot from 2023-10-25 21-06-03.png"
   
https://bugs.launchpad.net/bugs/2042993/+attachment/5717103/+files/Screenshot%20from%202023-10-25%2021-06-03.png

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

Title:
  overview sometimes stuck after pressing super

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I press super a lot to see progress of other applications or the system time 
from activities overview when in a fullscreen application, such as a steam game.
  Occasionally the activities overview will not show any applications nor the 
desktop, but only the gray background and the search bar (although applications 
on the dock will still be visible and selectable, just not interactable other 
than audio). The clock and quick settings are the only things that work 
normally in this state as not even the activities search bar is responsive. The 
only way I've been able to exit is by restarting the computer. I'm going to try 
using Xorg to restart gnome next time but I've not tested that yet.
  This issue hasn't seemed to occur in any situations other than running full 
screen applications. Although, given that I don't often use activities overview 
outside of fullscreen apps, that may not be required for the bug to occur.
  This bug started after upgrading to Ubuntu 23.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 23:01:44 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-03 (553 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-17 (22 days ago)

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


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

[Desktop-packages] [Bug 2042987] Re: The settings of different Wi-Fi adapters do NOT work separately.

[Larry Wei]

** Attachment added: "f9178fbfdedd6d6b7685198a25b84b085dd4d175_2_800x647.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2042987/+attachment/5717099/+files/f9178fbfdedd6d6b7685198a25b84b085dd4d175_2_800x647.png

** Tags added: desktop settings

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

Title:
   The settings of different Wi-Fi adapters do NOT work separately.

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The settings of different Wi-Fi adapters do NOT work separately.

  The Wi-Fi switch triggers all Wi-Fi adapters, and the Saved Networks lists do 
NOT be saved separately.
  Hope this bug can be fixed soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-settings 23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 08:54:37 2023
  InstallationDate: Installed on 2023-07-29 (101 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: Upgraded to mantic on 2023-08-16 (83 days ago)

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


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

[Desktop-packages] [Bug 2042987] [NEW] The settings of different Wi-Fi adapters do NOT work separately.

[Larry Wei]

Public bug reported:

The settings of different Wi-Fi adapters do NOT work separately.

The Wi-Fi switch triggers all Wi-Fi adapters, and the Saved Networks lists do 
NOT be saved separately.
Hope this bug can be fixed soon.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-settings 23.10.5
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 08:54:37 2023
InstallationDate: Installed on 2023-07-29 (101 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=tmux-256color
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-settings
UpgradeStatus: Upgraded to mantic on 2023-08-16 (83 days ago)

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


** Tags: amd64 apport-bug desktop mantic settings

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

Title:
   The settings of different Wi-Fi adapters do NOT work separately.

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The settings of different Wi-Fi adapters do NOT work separately.

  The Wi-Fi switch triggers all Wi-Fi adapters, and the Saved Networks lists do 
NOT be saved separately.
  Hope this bug can be fixed soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-settings 23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 08:54:37 2023
  InstallationDate: Installed on 2023-07-29 (101 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: Upgraded to mantic on 2023-08-16 (83 days ago)

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


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

[Desktop-packages] [Bug 2042979] Re: Noble spice-vdagent crash crashes xorg

[Mike Ferreira]

Note that KVM machine / OS templates, currently, only go to Ubuntu
23.10, which this one is set to. If I set them to VGA, instead of QXL,
it doesn't seem to happen.

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

Title:
  Noble spice-vdagent crash crashes xorg

Status in spice-vdagent package in Ubuntu:
  New

Bug description:
  This is on 'debian release' upgraded from Mantic to Noble, which I
  keep persistent to test the Noble Upgrades from day-to-day.

  Intermittent crashes, which results in the desktops crashing and
  returning back to the GDM3 graphical login.

  I am not sure if, since a VM, and Spice, if it is a KVM host problem, or if a 
Noble problem. The host is 22.04.3:
  >>>
  kvm --version
  QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15)
  Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

  virsh -c qemu:///system version --daemon 
  Compiled against library: libvirt 8.0.0
  Using library: libvirt 8.0.0
  Using API: QEMU 8.0.0
  Running hypervisor: QEMU 6.2.0
  Running against daemon: 8.0.0
  >>>
  Attaching crash report below

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: spice-vdagent 0.22.1-3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 12:25:52 2023
  InstallationDate: Installed on 2023-10-25 (13 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: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2042979/+subscriptions


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

[Desktop-packages] [Bug 2042979] Re: Noble spice-vdagent crash crashes xorg

[Mike Ferreira]

** Attachment added: "_usr_lib_xorg_Xorg.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2042979/+attachment/5717051/+files/_usr_lib_xorg_Xorg.1000.crash

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

Title:
  Noble spice-vdagent crash crashes xorg

Status in spice-vdagent package in Ubuntu:
  New

Bug description:
  This is on 'debian release' upgraded from Mantic to Noble, which I
  keep persistent to test the Noble Upgrades from day-to-day.

  Intermittent crashes, which results in the desktops crashing and
  returning back to the GDM3 graphical login.

  I am not sure if, since a VM, and Spice, if it is a KVM host problem, or if a 
Noble problem. The host is 22.04.3:
  >>>
  kvm --version
  QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15)
  Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

  virsh -c qemu:///system version --daemon 
  Compiled against library: libvirt 8.0.0
  Using library: libvirt 8.0.0
  Using API: QEMU 8.0.0
  Running hypervisor: QEMU 6.2.0
  Running against daemon: 8.0.0
  >>>
  Attaching crash report below

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: spice-vdagent 0.22.1-3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 12:25:52 2023
  InstallationDate: Installed on 2023-10-25 (13 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: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2042979/+subscriptions


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

[Desktop-packages] [Bug 2042979] [NEW] Noble spice-vdagent crash crashes xorg

[Mike Ferreira]

Public bug reported:

This is on 'debian release' upgraded from Mantic to Noble, which I keep
persistent to test the Noble Upgrades from day-to-day.

Intermittent crashes, which results in the desktops crashing and
returning back to the GDM3 graphical login.

I am not sure if, since a VM, and Spice, if it is a KVM host problem, or if a 
Noble problem. The host is 22.04.3:
>>>
kvm --version
QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

virsh -c qemu:///system version --daemon 
Compiled against library: libvirt 8.0.0
Using library: libvirt 8.0.0
Using API: QEMU 8.0.0
Running hypervisor: QEMU 6.2.0
Running against daemon: 8.0.0
>>>
Attaching crash report below

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: spice-vdagent 0.22.1-3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 12:25:52 2023
InstallationDate: Installed on 2023-10-25 (13 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: spice-vdagent
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: spice-vdagent (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "_usr_bin_spice-vdagent.1000.crash"
   
https://bugs.launchpad.net/bugs/2042979/+attachment/5717048/+files/_usr_bin_spice-vdagent.1000.crash

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

Title:
  Noble spice-vdagent crash crashes xorg

Status in spice-vdagent package in Ubuntu:
  New

Bug description:
  This is on 'debian release' upgraded from Mantic to Noble, which I
  keep persistent to test the Noble Upgrades from day-to-day.

  Intermittent crashes, which results in the desktops crashing and
  returning back to the GDM3 graphical login.

  I am not sure if, since a VM, and Spice, if it is a KVM host problem, or if a 
Noble problem. The host is 22.04.3:
  >>>
  kvm --version
  QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15)
  Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

  virsh -c qemu:///system version --daemon 
  Compiled against library: libvirt 8.0.0
  Using library: libvirt 8.0.0
  Using API: QEMU 8.0.0
  Running hypervisor: QEMU 6.2.0
  Running against daemon: 8.0.0
  >>>
  Attaching crash report below

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: spice-vdagent 0.22.1-3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 12:25:52 2023
  InstallationDate: Installed on 2023-10-25 (13 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: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2042979/+subscriptions


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

[Desktop-packages] [Bug 2042970] Re: no sound anywhere

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  no sound anywhere

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No problems up until recently.
  After upgrading to 23.04 (and then to 23.10) I have no more sound anywhere.
  I have investigated the usual suspects (I'm a Ubuntu newbie though): alas, I 
found nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  henkie 2542 F wireplumber
   /dev/snd/seq:henkie 2525 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 18:52:16 2023
  InstallationDate: Installed on 2022-04-19 (567 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (4 days ago)
  dmi.bios.date: 10/30/2009
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0F327M
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd10/30/2009:br1.8:efr1.8:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0F327M:rvr:cvnDellInc.:ct8:cvr:sku:
  dmi.product.name: Latitude E6500
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 2042970] [NEW] no sound anywhere

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

No problems up until recently.
After upgrading to 23.04 (and then to 23.10) I have no more sound anywhere.
I have investigated the usual suspects (I'm a Ubuntu newbie though): alas, I 
found nothing.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  henkie 2542 F wireplumber
 /dev/snd/seq:henkie 2525 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 18:52:16 2023
InstallationDate: Installed on 2022-04-19 (567 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to mantic on 2023-11-04 (4 days ago)
dmi.bios.date: 10/30/2009
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0F327M
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd10/30/2009:br1.8:efr1.8:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0F327M:rvr:cvnDellInc.:ct8:cvr:sku:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug mantic wayland-session
-- 
no sound anywhere
https://bugs.launchpad.net/bugs/2042970
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio 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 2042975] [NEW] Kisak-mesa fresh mpv crash

[Henry Wertz]

Public bug reported:

PPA affected is https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

I'll comment up top there's a patch to fix this issue, and a viable
workaround.  I decided to file a bug report primarily so if anyone else
comes across this issue they can see the workaround.  It's highly likely
Kisak doesn't have to do anything about this, that 23.2.2 will ship with
this fixed.

Running Mesa 23.2.1, mpv seg faults.  "Videos" video player doesn't
crash but doesn't play video either.

As a workaround I went to .config/mpv/mpv.conf and put in "vo=xv".  (I'm
not sure what the equivalent is if you're running Wayland.)

I found a bug report of this issue:

https://gitlab.freedesktop.org/mesa/mesa/-/issues/9922

It seems there were some changes made to AMD radeon driver, and both
radeon and Intel driver now have a few functions with the same names!
The link above has a backported patch from 24.0 development branch. I
assume 23.2.2 will most likely have a fix incorporated.

Thanks for the great work Kisak!!

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

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

Title:
  Kisak-mesa fresh mpv crash

Status in mesa package in Ubuntu:
  New

Bug description:
  PPA affected is https://launchpad.net/~kisak/+archive/ubuntu/kisak-
  mesa

  I'll comment up top there's a patch to fix this issue, and a viable
  workaround.  I decided to file a bug report primarily so if anyone
  else comes across this issue they can see the workaround.  It's highly
  likely Kisak doesn't have to do anything about this, that 23.2.2 will
  ship with this fixed.

  Running Mesa 23.2.1, mpv seg faults.  "Videos" video player doesn't
  crash but doesn't play video either.

  As a workaround I went to .config/mpv/mpv.conf and put in "vo=xv".
  (I'm not sure what the equivalent is if you're running Wayland.)

  I found a bug report of this issue:

  https://gitlab.freedesktop.org/mesa/mesa/-/issues/9922

  It seems there were some changes made to AMD radeon driver, and both
  radeon and Intel driver now have a few functions with the same names!
  The link above has a backported patch from 24.0 development branch. I
  assume 23.2.2 will most likely have a fix incorporated.

  Thanks for the great work Kisak!!

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


-- 
Mailing list: https://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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Steve Langasek]

On Tue, Nov 07, 2023 at 05:34:02PM -, Dave Jones wrote:
> Thanks for the quick review! Could someone set up a "mantic" branch

Done.

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

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


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

[Desktop-packages] [Bug 2042811] Re: [BPO] libreoffice 7.5.8 for jammy

[Rico Tzschichholz]

** Description changed:

  [Impact]
  
   * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release
  
   * This source packages matches the proposed SRU for lunar handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2041716
  
  [Scope]
  
   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.8-0ubuntu0.23.04.1
  
   * Backport target is Jammy/22.04 LTS releases to provide an official
  build of a more recent upstream version of LibreOffice
  
  [Testing]
  
   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).
  
    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_75/1762/
  
    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
  
   * Launchpad testing. The libreoffice packages include autopkgtests that
  were run and verified as passing.
  
     Jammy/22.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15363218/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231104_215443_4f9d7@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231105_003318_b15a5@/log.gz
- * [armhf] ...
+ * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/armhf/libr/libreoffice/20231106_141135_bbe65@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231104_222356_65e77@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231104_234922_f066c@/log.gz
  
   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented by:
  https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
  
  [Regression Potential]
  
   * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

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

Title:
  [BPO] libreoffice 7.5.8 for jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release

   * This source packages matches the proposed SRU for lunar handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2041716

  [Scope]

   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.8-0ubuntu0.23.04.1

   * Backport target is Jammy/22.04 LTS releases to provide an official
  build of a more recent upstream version of LibreOffice

  [Testing]

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

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

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

   * Launchpad testing. The libreoffice packages include autopkgtests
  that were run and verified as passing.

     Jammy/22.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15363218/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231104_215443_4f9d7@/log.gz
  * [arm64] 

[Desktop-packages] [Bug 2042972] [NEW] Display perfomance issue

[Astle Aloysius]

Public bug reported:

After booting, sometimes I am not able to quickly open apps, it takes
more than 5 mins to launch and in most of them dark mode is not shown.
It used to come back to normal but now it stays the same.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-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  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 00:11:58 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TigerLake-H GT1 [UHD Graphics] [1043:13fc]
 NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GA107M [GeForce RTX 3050 Mobile] [1043:13fc]
InstallationDate: Installed on 2023-10-29 (9 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=5188fb64-a6dc-4300-a704-0666d8ca03ba ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FX506HCB.313
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX506HCB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.11
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX506HCB.313:bd03/03/2023:br5.19:efr3.11:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506HCB_FX506HCB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506HCB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUS TUF Gaming F15
dmi.product.name: ASUS TUF Gaming F15 FX506HCB_FX506HCB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
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.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic performance 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/2042972

Title:
  Display perfomance issue

Status in xorg package in Ubuntu:
  New

Bug description:
  After booting, sometimes I am not able to quickly open apps, it takes
  more than 5 mins to launch and in most of them dark mode is not shown.
  It used to come back to normal but now it stays the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-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  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
 

[Desktop-packages] [Bug 2042973] [NEW] Desktop becomes unusable after changing window from fullscreen games on Wayland Only

[Luca Osvaldo Mastromatteo]

Public bug reported:

Description: Ubuntu 23.10
Release: 23.10
gnome-shell 45.0-1ubuntu2

Steps to reproduce:
1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from 
steam, both using DXVK)
2)Wait for them to fully load
3)Press the Super button in order to go back to the desktop

What should happen: A list of windows, the gnome desktop overview, is shown
What happened: All the screen section from above the gnome taskbar became grey 
like the activity overview accent color and nothing else can be done, the 
desktop functionality is broken
-

Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video
attached) 80% of the times when I switch from certain fullscreen games
to the desktop using the super button.

The gray color of the activity overview is shown above the shell taskbar
on both screens and nothing else can be done.

- The issue does not happen on an X11 session.
- The notifications still work correctly, as clicking the gnome shell bar or 
even locking and unlocking the screen.
- Right clicking and closing apps work. However, only the buttons from the 
shell itself only
- Everything involving actively changing windows does not.
- No matter the screen configuration the issue still persist.

Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck.

No workaround is discovered. Session can be terminated from the taskbar,
as it works correctly.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 19:47:42 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-08-12 (87 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45.0-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days ago)

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


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

** Attachment added: "Video showing the issue"
   
https://bugs.launchpad.net/bugs/2042973/+attachment/5717019/+files/senza%20titolo.mp4

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

Title:
   Desktop becomes unusable after changing window from fullscreen games
  on Wayland Only

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Description: Ubuntu 23.10
  Release: 23.10
  gnome-shell 45.0-1ubuntu2

  Steps to reproduce:
  1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from 
steam, both using DXVK)
  2)Wait for them to fully load
  3)Press the Super button in order to go back to the desktop

  What should happen: A list of windows, the gnome desktop overview, is shown
  What happened: All the screen section from above the gnome taskbar became 
grey like the activity overview accent color and nothing else can be done, the 
desktop functionality is broken
  -

  Since I upgraded from 23.04 to 23.10 the desktop becomes unusable
  (video attached) 80% of the times when I switch from certain
  fullscreen games to the desktop using the super button.

  The gray color of the activity overview is shown above the shell
  taskbar on both screens and nothing else can be done.

  - The issue does not happen on an X11 session.
  - The notifications still work correctly, as clicking the gnome shell bar or 
even locking and unlocking the screen.
  - Right clicking and closing apps work. However, only the buttons from the 
shell itself only
  - Everything involving actively changing windows does not.
  - No matter the screen configuration the issue still persist.

  Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck.

  No workaround is discovered. Session can be terminated from the
  taskbar, as it works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 19:47:42 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-12 (87 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days 

[Desktop-packages] [Bug 1428121]

[sb56637]

I can confirm that this bug affects me in Debian Bookworm (kernel 6.1) +
Pipewire with this hardware (and a DisplayPort -> HDMI adapter):


System:
  Host: T440s Kernel: 6.1.0-13-amd64 arch: x86_64 bits: 64 Desktop: Cinnamon
v: 5.6.8 Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: LENOVO product: 20AR006RUS v: ThinkPad T440s
  Mobo: LENOVO model: 20AR006RUS v: SDK0E50510 PRO
UEFI: LENOVO v: GJETA4WW (2.54 )
date: 03/27/2020
CPU:
  Info: dual core Intel Core i5-4300U [MT MCP] speed (MHz): avg: 805
min/max: 800/2900
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1366x768~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4400 (HSW
GT2)
Network:
  Device-1: Intel Ethernet I218-LM driver: e1000e
  Device-2: Intel Wireless 7260 driver: iwlwifi
  Device-3: Intel Bluetooth wireless interface type: USB driver: btusb



I also tried the Debian Backports 6.4 kernel with the same results.


The workaround suggested earlier in this report works:
> edit /etc/default/grub to add
> GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on,igfx_off"


However, it should be noted that openSUSE Tumbleweed + Pipewire on this same 
hardware does *NOT* have this bug.

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

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications 

[Desktop-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Dave Jones]

Thanks for the quick review! Could someone set up a "mantic" branch on
the lp:~ubuntu-desktop/ubuntu/+source/ubuntu-settings repository so I
can propose a merge to fix mantic too? (basically the same commit with a
lower version number)

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

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


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

[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]

[Daniel Mejares Teaño]

Im also affected with this bug

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

Title:
  Gnome 45 crash on restart in X11 session [Window manager error:
  Another compositing manager is already running on screen 0 on display
  “:0”]

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell package in Arch Linux:
  New

Bug description:
  Hello,

  Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer
  possible to restart gnome-shell without crashing the session. The only
  way not to crash it is to close all applications before restarting
  gnome-shell. I have verified this too.

  This has already been reported upstream: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050
  a tentative patch for mutter proposed: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598

  Please consider reviewing/testing this patch and pushing an update so
  people can restart gnome-shell session without crashing it.

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


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

[Desktop-packages] [Bug 2042956] [NEW] Error activating XKB configs (After sleep mode)

[Daniel LaSalle]

Public bug reported:

I have been getting this random error always when coming back from sleep
mode.

Random because it doesn't always pop-up at resume.

Also half of the suggestions displayed in the error message does not
seem to work so perhaps this problem is twofolds.

Problem 1: error activating XKB
Problem 2: update the "Please include" portion as it does not reflect the 
reality of 23.10

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: MATE
Date: Sun Nov  5 10:57:04 2023
DistUpgraded: 2023-10-12 22:24:13,551 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev df) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:87b7]
InstallationDate: Installed on 2023-02-23 (256 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=3e40054f-c010-4c20-834b-badb6d17cf88 ro splash splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (24 days ago)
dmi.bios.date: 12/29/2022
dmi.bios.release: 15.67
dmi.bios.vendor: AMI
dmi.bios.version: F.67
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B7
dmi.board.vendor: HP
dmi.board.version: 28.21
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 28.21
dmi.modalias: 
dmi:bvnAMI:bvrF.67:bd12/29/2022:br15.67:efr28.21:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.21:cvnHP:ct10:cvrChassisVersion:sku10M11UA#ABL:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-fq0xxx
dmi.product.sku: 10M11UA#ABL
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic ubuntu

** Attachment added: "Even though I was asked to run xprop-root | grep XKB it 
seems this is an old rustic way"
   
https://bugs.launchpad.net/bugs/2042956/+attachment/5716896/+files/Screenshot%20at%202023-11-05%2010-56-41.png

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

Title:
  Error activating XKB configs (After sleep mode)

Status in xorg package in Ubuntu:
  New

Bug description:
  I have been getting this random error always when coming back from
  sleep mode.

  Random because it doesn't always pop-up at resume.

  Also half of the suggestions displayed in the error message does not
  seem to work so perhaps this problem is twofolds.

  Problem 1: error activating XKB
  Problem 2: update the "Please include" portion as it does not reflect the 
reality of 23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sun Nov  5 10:57:04 2023
  DistUpgraded: 2023-10-12 22:24:13,551 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev df) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:87b7]
  InstallationDate: Installed on 2023-02-23 (256 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - 

[Desktop-packages] [Bug 2042762] Re: GNOME under Wayland does not start after updating to Ubuntu 23.10

[Daniel van Vugt]

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

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

Title:
  GNOME under Wayland does not start after updating to Ubuntu 23.10

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Hello Ubuntu community,

  I recently upgraded my system from Ubuntu 23.04 to 23.10 and since
  then (1 Week) I've had problems starting GNOME under Wayland. Here are
  the details of my system and the steps already taken:

  System information:

  Device: MS Surface Pro 5 (Intel Iris Plus Graphics 640)
  Ubuntu version: 10/23
  Kernel: Linux 6.5.6-surface

  Description of the problem:

  After updating to Ubuntu 23.10, the GNOME window manager no longer
  starts under Wayland. X.org, however, works fine. However, in my
  opinion the quality of the display is lower (screen tearing,
  flickering mouse, low fps)

  Screen resolution and scaling:

  I use an external monitor with 1920x1080px and 100% scaling. The
  built-in screen has a resolution of 2736x1824px and a scaling of 200%.
  Fractional scaling is enabled.

  Steps already taken:

  * All available updates have been installed.
  * Fractional scaling has been disabled.
  * I tried to "force" Wayland by adding "WaylandEnable=True" in the "gdm3 
custom.conf".
  * Automatic login (without entering a password) has been deactivated.
  * I tried reinstalling "libglib2.0-0".
  * Various Linux kernels tested: Linux 6.5.6-surface, Linux 6.3.2-surface, 
Linux 6.5.0-9-generic

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


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

[Desktop-packages] [Bug 1967456] Re: Jammy (and Mantic) doesn't use nvidia driver when executing firefox

[Gon Solo]

Ubuntu's firefox runs with llvmpipe as GPU. I downloaded firefox from
mozilla.org and it correctly uses my NVIDIA RTX 3060.

** Summary changed:

- Jammy didn't use nvidia driver when executing firefox
+ Jammy (and Mantic) doesn't use nvidia driver when executing firefox

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

Title:
  Jammy (and Mantic) doesn't use nvidia driver when executing firefox

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  [Reproduce step]

  1. Install Jammy beta.
  2. Install Nvidia driver by ubuntu-driver install.
  3. Connect monitor to dGPU output port.
  4. Run firefox, type "about:support" in url, and check column "GPU #1"

  [Expected result]

  should see nvidia driver info.

  [Actual result]

  still use llvmpipe

  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: HP Z2 Mini G5 workstation
  CID: 202008-28179

  Wayland in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1186 F pulseaudio
   /dev/snd/controlC1:  u  1186 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 00:07:47 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: HP HP Z2 Mini G5 Workstation
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: HP
  dmi.bios.version: S50 Ver. 01.00.01
  dmi.board.name: 8754
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.03
  dmi.chassis.type: 2
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV:
  dmi.product.family: 103C_53335X HP Workstation
  dmi.product.name: HP Z2 Mini G5 Workstation
  dmi.product.sku: 9JD38AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967456/+subscriptions


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

[Desktop-packages] [Bug 2042762] Re: GNOME under Wayland does not start after updating to Ubuntu 23.10

[Christian Köver-Draxl]

I managed to "solve" this problem by deleting the complete
~/.config/dconf/user file and reinstall every gnome extension i had
installed. Now i can start gnome on wayland, but also had to do again
every customisation i had. (Not sure if removing every extension was
necessary)

also see in: https://forum.garudalinux.org/t/gnome-45-wayland-
session/31493/5

Requested error logs:
1. :
--> wayland working since several boots: 
  journalctl -b0 > journal.txt
--> ~10 boots before -> wayland not working:
  journalctl -b-10 > prevjournal.txt
3. (most probably) 
https://errors.ubuntu.com/oops/45609b38-7049-11ee-b85d-fa163e171f02

(regrettably i dont have the old "faulty" dconf/user file anymore)

** Attachment added: "logs.zip"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042762/+attachment/5716874/+files/logs.zip

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

Title:
  GNOME under Wayland does not start after updating to Ubuntu 23.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello Ubuntu community,

  I recently upgraded my system from Ubuntu 23.04 to 23.10 and since
  then (1 Week) I've had problems starting GNOME under Wayland. Here are
  the details of my system and the steps already taken:

  System information:

  Device: MS Surface Pro 5 (Intel Iris Plus Graphics 640)
  Ubuntu version: 10/23
  Kernel: Linux 6.5.6-surface

  Description of the problem:

  After updating to Ubuntu 23.10, the GNOME window manager no longer
  starts under Wayland. X.org, however, works fine. However, in my
  opinion the quality of the display is lower (screen tearing,
  flickering mouse, low fps)

  Screen resolution and scaling:

  I use an external monitor with 1920x1080px and 100% scaling. The
  built-in screen has a resolution of 2736x1824px and a scaling of 200%.
  Fractional scaling is enabled.

  Steps already taken:

  * All available updates have been installed.
  * Fractional scaling has been disabled.
  * I tried to "force" Wayland by adding "WaylandEnable=True" in the "gdm3 
custom.conf".
  * Automatic login (without entering a password) has been deactivated.
  * I tried reinstalling "libglib2.0-0".
  * Various Linux kernels tested: Linux 6.5.6-surface, Linux 6.3.2-surface, 
Linux 6.5.0-9-generic

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


-- 
Mailing list: https://launchpad.net/~desktop-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: Gnome shell freezing and/or taking a long time to load

[Jesús Soto]

Nope, same issues

-- 
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:
  Gnome shell freezing and/or taking a long time to load

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/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 2042931] Re: Crashing frequently

[Sebastien Bacher]

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: nautilus (Ubuntu)
   Status: New => Incomplete

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

Title:
  Crashing frequently

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Crashing frequetnly

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 11:31:46 2023
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-09-07 (425 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu2
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

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


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

[Desktop-packages] [Bug 2041680] Re: Stack trace not included in GNOME Shell crash report in JournalErrors

[Daniel van Vugt]

Sorry I was trying to rush through 7 days of bugs and misread that.
Looks like gjs is to blame:

https://gitlab.gnome.org/GNOME/gjs/-/blob/master/gjs/stack.cpp?ref_type=heads#L25

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

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

Title:
  Stack trace not included in GNOME Shell crash report in JournalErrors

Status in gjs package in Ubuntu:
  New

Bug description:
  1. Use Ubuntu 23.10 with all updates
  2. kill gnome-shell: killall -11 gnome-shell
  3. log-in again
  4. Wait for the apport crash window for reporting
  5. Show details

  The JournalErrors does not contain the stack trace, but now I found it
  in ShellJournal:

   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: GNOME Shell crashed with 
signal 11
   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: == Stack trace for context 
0x56355c3ca0f0 ==
   [   87.745201] ubuntu-2304-2 gnome-shell[1048]: #0   56355c491fe8 i   
resource:///org/gnome/shell/ui/init.js:21 (2b3376570ba0 @ 48)

  The crash is not logged with a high enough severity to let it appear
  in JournalErrors.

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


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

[Desktop-packages] [Bug 2040977] Re: [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating on screen

[Bug Watch Updater]

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

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

Title:
  [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating
  on screen

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

Bug description:
  Using the touchpad on an X1 Carbon G10 with 90Hz OLED the mouse cursor
  stutters, unless something else is changing on screen (like running
  glmark2-wayland).

  Workaround:

  Put this in /etc/environment:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 15:48:28 2023
  InstallationDate: Installed on 2023-10-23 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2041680] Re: Stack trace not included in GNOME Shell crash report in JournalErrors

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: Invalid => 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/2041680

Title:
  Stack trace not included in GNOME Shell crash report in JournalErrors

Status in gjs package in Ubuntu:
  New

Bug description:
  1. Use Ubuntu 23.10 with all updates
  2. kill gnome-shell: killall -11 gnome-shell
  3. log-in again
  4. Wait for the apport crash window for reporting
  5. Show details

  The JournalErrors does not contain the stack trace, but now I found it
  in ShellJournal:

   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: GNOME Shell crashed with 
signal 11
   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: == Stack trace for context 
0x56355c3ca0f0 ==
   [   87.745201] ubuntu-2304-2 gnome-shell[1048]: #0   56355c491fe8 i   
resource:///org/gnome/shell/ui/init.js:21 (2b3376570ba0 @ 48)

  The crash is not logged with a high enough severity to let it appear
  in JournalErrors.

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


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

[Desktop-packages] [Bug 2040977] Re: [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating on screen

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3146
   https://gitlab.gnome.org/GNOME/mutter/-/issues/3146

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

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

Title:
  [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating
  on screen

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Using the touchpad on an X1 Carbon G10 with 90Hz OLED the mouse cursor
  stutters, unless something else is changing on screen (like running
  glmark2-wayland).

  Workaround:

  Put this in /etc/environment:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 15:48:28 2023
  InstallationDate: Installed on 2023-10-23 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2041680] Re: Stack trace not included in GNOME Shell crash report in JournalErrors

[Benjamin Drung]

This bug report is not about a too short stack trace. This report is
about the stack trace being logged with lower severity than error.

Will the logged stack trace be logged as error if there is a JavaScript
stack to display?

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

Title:
  Stack trace not included in GNOME Shell crash report in JournalErrors

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  1. Use Ubuntu 23.10 with all updates
  2. kill gnome-shell: killall -11 gnome-shell
  3. log-in again
  4. Wait for the apport crash window for reporting
  5. Show details

  The JournalErrors does not contain the stack trace, but now I found it
  in ShellJournal:

   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: GNOME Shell crashed with 
signal 11
   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: == Stack trace for context 
0x56355c3ca0f0 ==
   [   87.745201] ubuntu-2304-2 gnome-shell[1048]: #0   56355c491fe8 i   
resource:///org/gnome/shell/ui/init.js:21 (2b3376570ba0 @ 48)

  The crash is not logged with a high enough severity to let it appear
  in JournalErrors.

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


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

[Desktop-packages] [Bug 1884759] Re: [snap] U2f yubikey not recognized until unplugged and plugged back in

[qwertolo]

Thanks for the update Alex, is there any ETA for this?

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

Title:
  [snap] U2f yubikey not recognized until unplugged and plugged back in

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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


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

[Desktop-packages] [Bug 2040296] Re: On the top pannel which contains date and time the calendar popup when I click on the upcoming months date that is november 1, 2023 last two weeks are displayed ou

[Daniel van Vugt]

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

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

** This bug has been marked a duplicate of bug 1970800
   Clicking a calendar date in the bottom row of the panel calendar causes a 
graphical glitch

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

Title:
  On the top pannel which contains date and time the calendar popup when
  I click on the upcoming months date that is november 1, 2023 last two
  weeks are displayed outside the box which contains the weeks. I am
  reporting this bug on oct 24, 2023

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On the top pannel which contains date and time the calendar popup when I 
click on the upcoming months date that is november 1, 2023 last two weeks are 
displayed outside the box which contains the weeks. I am reporting this bug on 
oct 24, 2023. This is happening if i click the button of 1st november 2023 
without clicking after button, if click any other day and click the next month 
november date which follows after october it is ok, but if my first click is 
next month nov1, nov2, nov3, nov4, this problem is occuring.
  kindly fix this error community.

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


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

[Desktop-packages] [Bug 2041219] Re: GUI Freezes Randomly

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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


-- 
Mailing list: https://launchpad.net/~desktop-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: Gnome shell freezing and/or taking a long time to load

[Daniel van Vugt]

Now waiting to hear if deleting all local extensions has helped.

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

Title:
  Gnome shell freezing and/or taking a long time to load

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/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 2041660] Re: Icons for running apps are no longer added to the dashboard after some uptime in 23.10 (mantic)

[Daniel van Vugt]

See also bug 1890891 and bug 1936734

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

Title:
  Icons for running apps are no longer added to the dashboard after some
  uptime in 23.10 (mantic)

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

Bug description:
  Upgraded from 23.04 to 23.10 last week.

  Noticed today that after some uptime when starting new applications
  their icons wont show up in the dashboard to the left of the screen.
  However they will show up in alt+tab and they are running and
  functioning.

  They do show up after a reboot.

  Current uptime is 2 days and 9 hours, when starting (as an example)
  the game Klondike it wont show up in the dashboard. But it is working
  as expected otherwise and do show up in alt+tab.

  After reboot it will show up in the dashboard as a running app when
  started (and go away when closed).

  Waiting another day or two of uptime the icons will again not show up
  in the dashboard of newly started applications.

  Note this is about that running apps wont show up as icons. The static icons 
I have decided to stick as favorites to the dashboard works all the time.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell-extension-ubuntu-dock 87ubuntu1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-21 (6 days ago)
  UserGroups: adm cdrom davfs2 dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-12-28T12:18:23.468464
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell-extension-ubuntu-dock 87ubuntu1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-21 (6 days ago)
  UserGroups: adm cdrom davfs2 dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-12-28T12:18:23.468464

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


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

[Desktop-packages] [Bug 2041680] Re: Stack trace not included in GNOME Shell crash report in JournalErrors

[Daniel van Vugt]

This just means the process was not active in JavaScript. Most of the
time gnome-shell is running native C code (in mutter or in gnome-shell)
so there is no JavaScript stack to display.


** Tags added: mantic

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

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

Title:
  Stack trace not included in GNOME Shell crash report in JournalErrors

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  1. Use Ubuntu 23.10 with all updates
  2. kill gnome-shell: killall -11 gnome-shell
  3. log-in again
  4. Wait for the apport crash window for reporting
  5. Show details

  The JournalErrors does not contain the stack trace, but now I found it
  in ShellJournal:

   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: GNOME Shell crashed with 
signal 11
   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: == Stack trace for context 
0x56355c3ca0f0 ==
   [   87.745201] ubuntu-2304-2 gnome-shell[1048]: #0   56355c491fe8 i   
resource:///org/gnome/shell/ui/init.js:21 (2b3376570ba0 @ 48)

  The crash is not logged with a high enough severity to let it appear
  in JournalErrors.

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


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

[Desktop-packages] [Bug 2041690] Re: [nvidia] After using the secondary screen, the primary screen stops working

[Daniel van Vugt]

** Summary changed:

- Cannot open internal or screen laptop
+ [nvidia] After using the secondary screen, the primary screen stops working

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)

** Tags added: nvidia

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

Title:
  [nvidia] After using the secondary screen, the primary screen stops
  working

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  After I use the secondary screen, the primary screen stops working,
  and the problem is nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-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  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 23:58:39 2023
  DistUpgraded: 2023-10-14 21:42:04,522 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics] 
[1025:153b]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f9d] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [1025:1544]
  InstallationDate: Installed on 2023-05-20 (160 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=8806d2d2-440c-4fb8-bfae-fce3d6fc0f20 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (13 days ago)
  XorgConf:
   
  dmi.bios.date: 06/22/2022
  dmi.bios.release: 1.18
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kamiq_TLS
  dmi.board.vendor: TGL
  dmi.board.version: V1.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.18
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.18:bd06/22/2022:br1.18:efr1.10:svnAcer:pnNitroAN517-54:pvrV1.18:rvnTGL:rnKamiq_TLS:rvrV1.18:cvnAcer:ct10:cvrV1.18:sku:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN517-54
  dmi.product.sku: 
  dmi.product.version: V1.18
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  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.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2041690/+subscriptions


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

[Desktop-packages] [Bug 2037325] Re: [Lubuntu] Sudden screen freeze

[Daniel van Vugt]

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [Lubuntu] Sudden screen freeze

Status in lubuntu-meta package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Out of nowhere screen got frozen and didn't respond to any input,
  although I could get my pointer moving with touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Mon Sep 25 23:03:08 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5062]
  InstallationDate: Installed on 2023-04-20 (158 days ago)
  InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  MachineType: LENOVO 20HMS6XX00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2022
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET69W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS6XX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS6XX00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/lubuntu-meta/+bug/2037325/+subscriptions


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

[Desktop-packages] [Bug 2041715] Re: Sudden freeze/crash (with audio flickering)

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 2037325
   [Lubuntu] Sudden screen freeze

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

Title:
  Sudden freeze/crash (with audio flickering)

Status in xorg package in Ubuntu:
  New

Bug description:
  All of the sudden screen just got frozen (in that moment I was
  listening to the song and audio did not continue playing as usual, but
  started "flickering"). I put the note about audio here, because
  usually freeze affected only the screen itself and audio was playing
  as usual. I've been reporting the xorg freeze/hang a number of times,
  I thought it was about new kernel version. But recently I updated xorg
  package and today this happened. Will try to roll back and see what
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Sat Oct 28 15:18:01 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5062]
  InstallationDate: Installed on 2023-04-20 (190 days ago)
  InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HMS6XX00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-50-generic 
root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2022
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET69W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS6XX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS6XX00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/xorg/+bug/2041715/+subscriptions


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

[Desktop-packages] [Bug 2041853] Re: screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works)

[Daniel van Vugt]

** Summary changed:

- screen goes blank, audio cuts out
+ screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works)

** Package changed: gnome-shell (Ubuntu) => linux-hwe-6.2 (Ubuntu)

** Changed in: linux-hwe-6.2 (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/2041853

Title:
  screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works)

Status in linux-hwe-6.2 package in Ubuntu:
  New

Bug description:
  I'm tracking down the multiple causes of screen flashes and audio 
interruption on my ubuntu 22.04 laptop. 
  Issue open with Lenovo : 
https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298

  
  This bug is one of the causes (log reversed : journalctl -r)

  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac8bfbc10] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd416dc0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996b860] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878ac50] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb009cc0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a610] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9f6a480] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd404df0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a2f0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb16d9a0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca446320] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acdf86f70] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996a4e0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6fd0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9e94de0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6350] is on because it needs an allocation.
  oct. 30 15:17:13 

[Desktop-packages] [Bug 2042931] [NEW] Crashing frequently

[Tony Stark]

Public bug reported:

Crashing frequetnly

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 11:31:46 2023
GsettingsChanges:
 
InstallationDate: Installed on 2022-09-07 (425 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince42.3-0ubuntu2
 file-roller   3.42.0-1
 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
 nautilus-share0.7.3-2ubuntu6

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


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  Crashing frequently

Status in nautilus package in Ubuntu:
  New

Bug description:
  Crashing frequetnly

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 11:31:46 2023
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-09-07 (425 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu2
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

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


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

[Desktop-packages] [Bug 2018134] Re: [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all on either built in speakers, headphones or HDMI audio. Multiple reinstalls of alsa and others,

[CoolhandWarrior]

I fix it like this:

1-Fresh install ubuntu 22.04.3 + update after install

2-as admin:
sudo echo "options snd-hda-intel model=clevo-p950" | sudo tee -a 
/etc/modprobe.d/alsa-base.conf

3-as admin:
sudo update-initramfs -u 

4-Reboot

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

Title:
  [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all on
  either built in speakers, headphones or HDMI audio. Multiple
  reinstalls of alsa and others, speaker levels in settings are moving
  yet no sound created

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  In settings when selecting the built in audio the levels are moving
  and it thinks it's outputting sound, but nothing. Same results when
  using headphones or as a troubleshooting I attempted to use the hdmi
  audio out as well. Already tried reinstalling alsa and pulseaudio, to
  no effect. When running lspci -v | grep -A7 -i "audio" I get the
  following audio devices.

  
  00:1f.3 Audio device: Intel Corporation Device 7a50 (rev 11)
  Subsystem: CLEVO/KAPOK Computer Device d702
  Flags: bus master, fast devsel, latency 32, IRQ 204, IOMMU group 14
  Memory at 620313 (64-bit, non-prefetchable) [size=16K]
  Memory at 620300 (64-bit, non-prefetchable) [size=1M]
  Capabilities: 
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  01:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1)
  Subsystem: NVIDIA Corporation Device 
  Physical Slot: 1
  Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 15
  Memory at 7400 (32-bit, non-prefetchable) [size=16K]
  Capabilities: 
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel`

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrik 3084 F pulseaudio
   /dev/snd/controlC1:  patrik 3084 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 11:07:13 2023
  InstallationDate: Installed on 2023-04-27 (1 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrik 3084 F pulseaudio
   /dev/snd/controlC1:  patrik 3084 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2023
  dmi.bios.release: 7.8
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.08RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: PD5x_7xSNC_SND_SNE
  dmi.board.vendor: NB01
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.08RTR1:bd04/12/2023:br7.8:efr7.4:svnSchenkerTechnologiesGmbH:pnXMGPRO(E23):pvrNotApplicable:rvnNB01:rnPD5x_7xSNC_SND_SNE:rvrNotApplicable:cvnSchenkerTechnologiesGmbH:ct10:cvrN/A:skuXPR15E23/XPR17E23:
  dmi.product.name: XMG PRO (E23)
  dmi.product.sku: XPR15E23 / XPR17E23
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SchenkerTechnologiesGmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2018134/+subscriptions


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

[Desktop-packages] [Bug 2024680] Re: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue

[Daniel Reiter]

Yes confirmed working with 23.10 - Also base conf was full of various
attempts so options snd-hda-intel model=generic finally got everything
recognised for the onboard sound on the xps.

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

Title:
  Dell XPS 9730 no sound, I have tried the 22.04 lts same issue

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've tried various fixes without success, I did manage to get the
  NVIDA HDMI in the sound options but I've never had the inbuilt Intel
  Media Hardware working for sound.  22.04 LTS had the same issue and
  I've upgraded to the new version 23.04 which looks good.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  Uname: Linux 6.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 2245 F wireplumber
   /dev/snd/seq:daniel 2241 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 22 17:30:27 2023
  InstallationDate: Installed on 2023-06-16 (5 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2023
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 067X4F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd03/23/2023:br1.2:efr1.1:svnDellInc.:pnXPS179730:pvr:rvnDellInc.:rn067X4F:rvrA00:cvnDellInc.:ct10:cvr:sku0BDB:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9730
  dmi.product.sku: 0BDB
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 2041732] Re: Touchpad is extra-sensitive on Wayland

[Daniel van Vugt]

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

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

Title:
  Touchpad is extra-sensitive on Wayland

Status in libinput package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Whenever I use Wayland, the touchpad is *much* more sensitive than on
  X11. I'm using the default settings for everything (sensitivity,
  acceleration profile, etc) and both X11 and Wayland are using
  libinput.

  Both normal mouse movement and two-finger scrolling are more
  sensitive.

  Here's the entry in libinput list-deviecs for my touchpad:

  Device:   ELAN06FA:00 04F3:3293 Touchpad
  Kernel:   /dev/input/event9
  Group:6
  Seat: seat0, default
  Size: 134x78mm
  Capabilities: pointer gesture
  Tap-to-click: disabled
  Tap-and-drag: enabled
  Tap drag lock:disabled
  Left-handed:  disabled
  Nat.scrolling:disabled
  Middle emulation: disabled
  Calibration:  n/a
  Scroll methods:   *two-finger edge 
  Click methods:*button-areas clickfinger 
  Disable-w-typing: enabled
  Disable-w-trackpointing: enabled
  Accel profiles:   flat *adaptive custom
  Rotation: n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libinput10 1.23.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-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  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 16:54:16 2023
  DistUpgraded: 2023-09-23 14:28:46,526 INFO cache.commit()
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 6.5.0-10-generic, x86_64: installed
   acpi-call/1.2.2, 6.5.0-9-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-10-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:3e53]
   NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] [10de:28e1] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GN21-X2 [17aa:3e53]
  InstallationDate: Installed on 2023-08-02 (88 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=ab9aefbd-ccde-4fe6-ae0c-5802f04e9528 ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: libinput
  UpgradeStatus: Upgraded to mantic on 2023-09-23 (35 days ago)
  XorgLogOld:
   
  dmi.bios.date: 07/25/2023
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MBCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Slim Pro 9 14IRP8
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrMBCN26WW:bd07/25/2023:br1.26:efr1.26:svnLENOVO:pn83BV:pvrLenovoSlimPro914IRP8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLenovoSlimPro914IRP8:skuLENOVO_MT_83BV_BU_idea_FM_SlimPro914IRP8:
  dmi.product.family: Slim Pro 9 14IRP8
  dmi.product.name: 83BV
  dmi.product.sku: LENOVO_MT_83BV_BU_idea_FM_Slim Pro 9 14IRP8
  dmi.product.version: Lenovo Slim Pro 9 14IRP8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
  

[Desktop-packages] [Bug 2041853] Re: screen goes blank, audio cuts out

[James Atack]

Thanks for looking at this. I have worked around the issue by reverting
my kernel to 5.15

There is no doubt an issue somewhere with the hardware/software stack I was 
using but I couldn't figure out what it was. For the record :
 - AMD Ryzen 7 PRO 6850U
 - Kernel 6.2.0-26
 - Ubuntu 22.04.3

You can close/delete this report.

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

Title:
  screen goes blank, audio cuts out

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm tracking down the multiple causes of screen flashes and audio 
interruption on my ubuntu 22.04 laptop. 
  Issue open with Lenovo : 
https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298

  
  This bug is one of the causes (log reversed : journalctl -r)

  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac8bfbc10] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd416dc0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996b860] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878ac50] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb009cc0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a610] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9f6a480] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd404df0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a2f0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb16d9a0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca446320] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acdf86f70] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996a4e0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6fd0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9e94de0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6350] is on because it needs an 

[Desktop-packages] [Bug 2042874] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only

[Daniel van Vugt]

Please open a new bug by running:

  ubuntu-bug gnome-shell

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

Title:
  Desktop becomes unusable after changing window from fullscreen games
  on Wayland Only

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 23.10
  Release:  23.10
  gnome-shell 45.0-1ubuntu2

  Steps to reproduce: 
  1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from 
steam, both using DXVK)
  2)Wait for them to fully load
  3)Press the Super button in order to go back to the desktop

  What should happen: A list of windows, the gnome desktop overview, is shown 
  What happened: All the screen section from above the gnome taskbar became 
grey like the activity overview accent color and nothing else can be done, the 
desktop functionality is broken 
  -

  
  Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video 
attached) 80% of the times when I switch from certain fullscreen games to the 
desktop using the super button. 

  The gray color of the activity overview is shown above the shell
  taskbar on both screens and nothing else can be done.

  - The issue does not happen on an X11 session.
  - The notifications still work correctly, as clicking the gnome shell bar or 
even locking and unlocking the screen.
  - Right clicking and closing apps work. However, only the buttons from the 
shell itself only
  - Everything involving actively changing windows does not.
  - No matter the screen configuration the issue still persist.

  Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck.

  No workaround is discovered. Session can be terminated from the
  taskbar, as it works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  Uname: Linux 6.5.10-x64v4-xanmod1 x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 21:43:01 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-12 (86 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (24 days ago)

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


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

[Desktop-packages] [Bug 2041736] Re: dm crypt unlock prompt doesn't respond to key presses in kernel 6.5 (but 6.2 works)

[Daniel van Vugt]

** Summary changed:

- dm crypt unlock prompt doesn't respond to key presses
+ dm crypt unlock prompt doesn't respond to key presses in kernel 6.5 (but 6.2 
works)

** Summary changed:

- dm crypt unlock prompt doesn't respond to key presses in kernel 6.5 (but 6.2 
works)
+ [MacbookPro 14,1] dm crypt unlock prompt doesn't respond to key presses in 
kernel 6.5 (but 6.2 works)

** Package changed: plymouth (Ubuntu) => linux (Ubuntu)

** Tags added: regression-release

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

Title:
  [MacbookPro 14,1] dm crypt unlock prompt doesn't respond to key
  presses in kernel 6.5 (but 6.2 works)

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading my MacbookPro 14,1 from 23.04 to 23.10 dm-crypt unlock prompt 
doesn't respond to key presses and I'm not able to type in my password to 
unlock the disk.
  The only option that works now is to boot with the kernel left from 23.04 
(6.2.0-35-generic).
  Any tips to troubleshoot the issue would be much appreciated.

  % lsb_release -a 
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: plymouth 22.02.122-3ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 10:25:26 2023
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2023-04-22 (190 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: Upgraded to mantic on 2023-10-27 (2 days ago)
  dmi.bios.date: 08/22/2022
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 499.40.2.0.0
  dmi.board.name: Mac-B4831CEBD52A0C4C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro14,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B4831CEBD52A0C4C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr499.40.2.0.0:bd08/22/2022:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro14,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Desktop-packages] [Bug 2041781] Re: error

[Daniel van Vugt]

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

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

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

** This bug has been marked a duplicate of bug 2027617
   Expose custom display modes in Wayland sessions like Xorg does

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

Title:
  error

Status in mutter package in Ubuntu:
  New

Bug description:
  i can't create resolutions.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 30 00:55:42 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor 
Family Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2023-10-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=671e14ce-7eda-4e62-954c-b9759f9e70eb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-DS2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/mutter/+bug/2041781/+subscriptions


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

[Desktop-packages] [Bug 2042874] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only

[Luca Osvaldo Mastromatteo]

Good morning, at the moment of writing I have created the apport when I
had the mesa PPA installed as an attempt to find if the issue was
related to the graphics drivers so that's why the PPA is shown.

It is already uninstalled now, as I said still happens, do you need
other logs?

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

Title:
  Desktop becomes unusable after changing window from fullscreen games
  on Wayland Only

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 23.10
  Release:  23.10
  gnome-shell 45.0-1ubuntu2

  Steps to reproduce: 
  1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from 
steam, both using DXVK)
  2)Wait for them to fully load
  3)Press the Super button in order to go back to the desktop

  What should happen: A list of windows, the gnome desktop overview, is shown 
  What happened: All the screen section from above the gnome taskbar became 
grey like the activity overview accent color and nothing else can be done, the 
desktop functionality is broken 
  -

  
  Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video 
attached) 80% of the times when I switch from certain fullscreen games to the 
desktop using the super button. 

  The gray color of the activity overview is shown above the shell
  taskbar on both screens and nothing else can be done.

  - The issue does not happen on an X11 session.
  - The notifications still work correctly, as clicking the gnome shell bar or 
even locking and unlocking the screen.
  - Right clicking and closing apps work. However, only the buttons from the 
shell itself only
  - Everything involving actively changing windows does not.
  - No matter the screen configuration the issue still persist.

  Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck.

  No workaround is discovered. Session can be terminated from the
  taskbar, as it works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  Uname: Linux 6.5.10-x64v4-xanmod1 x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 21:43:01 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-12 (86 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (24 days ago)

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


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

[Desktop-packages] [Bug 2041853] Re: screen goes blank, audio cuts out

[Daniel van Vugt]

There are a lot of errors coming from local extensions so please start
by removing those:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

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

Title:
  screen goes blank, audio cuts out

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm tracking down the multiple causes of screen flashes and audio 
interruption on my ubuntu 22.04 laptop. 
  Issue open with Lenovo : 
https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298

  
  This bug is one of the causes (log reversed : journalctl -r)

  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac8bfbc10] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd416dc0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996b860] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878ac50] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb009cc0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a610] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9f6a480] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd404df0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a2f0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb16d9a0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca446320] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acdf86f70] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996a4e0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6fd0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9e94de0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6350] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 

[Desktop-packages] [Bug 2041853] Re: screen goes blank, audio cuts out

[Daniel van Vugt]

Those warnings are not related to the main issue. The warnings are
covered by bug 1857392.

** Summary changed:

- screen goes blank, audio cuts out, cause Window manager warning: Overwriting 
existing binding of keysym messages
+ screen goes blank, audio cuts out

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

Title:
  screen goes blank, audio cuts out

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm tracking down the multiple causes of screen flashes and audio 
interruption on my ubuntu 22.04 laptop. 
  Issue open with Lenovo : 
https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298

  
  This bug is one of the causes (log reversed : journalctl -r)

  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac8bfbc10] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd416dc0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996b860] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878ac50] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb009cc0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a610] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9f6a480] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd404df0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a2f0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb16d9a0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca446320] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acdf86f70] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996a4e0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6fd0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9e94de0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6350] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't 

[Desktop-packages] [Bug 2039866] Re: I cannot use two screens on the Ubuntu system.

[Daniel van Vugt]

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

** Tags added: multimonitor

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

Title:
  I cannot use two screens on the Ubuntu system.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I cannot use two screens on the Ubuntu system. It was very good, and
  there were no problems with it. Only three days ago, I received a new
  notification regarding an update. I updated, and since then, the
  second screen has stuck and I cannot interact with it in any way. As a
  temporary solution, I With it, I disconnect the screen and connect it
  again, it works for no more than 10 minutes, then it hangs again, and
  I have to restart it again. I am fed up, but there are many updates
  that I received after that, and I say that perhaps this time this
  problem will be fixed, but no Something is going on, please help.

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


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

[Desktop-packages] [Bug 2042042] Re: Browser does not remember workspace after leaving full screen video

[Daniel van Vugt]

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

** Summary changed:

- Browser does not remember workspace after leaving full screen video
+ [MATE] Browser does not remember workspace after leaving full screen video

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

Title:
  [MATE] Browser does not remember workspace after leaving full screen
  video

Status in marco package in Ubuntu:
  New

Bug description:
  Using 2x screens in portrait mode, if I display my browser on the
  right-side panel of workspace 1, watch a video and full screen it,
  after I  off the video the browser will now be displayed on the
  left-side panel of workspace 1.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Oct 30 23:06:47 2023
  DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
  InstallationDate: Installed on 2023-04-14 (199 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off 
ipv6.disable=1 pcie_aspm=off
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (17 days ago)
  dmi.bios.date: 03/13/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6063
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.cron.daily.apport: [deleted]
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2042874] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only

[Daniel van Vugt]

Thanks for the bug report. Since your graphics packages are from the
unsupported 'oibaf' PPA we can't support it here. Please uninstall that
PPA from the system and if you have any more issues then open new bugs
for them.


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

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

Title:
  Desktop becomes unusable after changing window from fullscreen games
  on Wayland Only

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 23.10
  Release:  23.10
  gnome-shell 45.0-1ubuntu2

  Steps to reproduce: 
  1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from 
steam, both using DXVK)
  2)Wait for them to fully load
  3)Press the Super button in order to go back to the desktop

  What should happen: A list of windows, the gnome desktop overview, is shown 
  What happened: All the screen section from above the gnome taskbar became 
grey like the activity overview accent color and nothing else can be done, the 
desktop functionality is broken 
  -

  
  Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video 
attached) 80% of the times when I switch from certain fullscreen games to the 
desktop using the super button. 

  The gray color of the activity overview is shown above the shell
  taskbar on both screens and nothing else can be done.

  - The issue does not happen on an X11 session.
  - The notifications still work correctly, as clicking the gnome shell bar or 
even locking and unlocking the screen.
  - Right clicking and closing apps work. However, only the buttons from the 
shell itself only
  - Everything involving actively changing windows does not.
  - No matter the screen configuration the issue still persist.

  Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck.

  No workaround is discovered. Session can be terminated from the
  taskbar, as it works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  Uname: Linux 6.5.10-x64v4-xanmod1 x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 21:43:01 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-12 (86 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (24 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-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: Gnome shell freezing and/or taking a long time to load

[Daniel van Vugt]

The first one was backlight. I don't know how significant that is but it
would explain why the bug is machine-specific:

nov 07 09:14:06 perseus gnome-shell[1255]: 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 notify on 
Gjs_status_backlight_SliderItem 0x5620201502b0.
   == Stack trace for context 
0x56201e19fe50 ==
   #0   7ffccf769190 I   
resource:///org/gnome/shell/ui/status/backlight.js:57 (16688c028e70 @ 131)
   #1   7ffccf769ce0 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:687 (374b8fd9bec0 @ 
25)
   #2   7ffccf769d20 I   
resource:///org/gnome/shell/ui/status/backlight.js:197 (16688c02c420 @ 199)
   #3   7ffccf769d50 I   
resource:///org/gnome/shell/ui/status/backlight.js:157 (16688c02c2e0 @ 12)
   #4   56201e26c108 i   
resource:///org/gnome/shell/ui/init.js:21 (374b8fd70ba0 @ 48)


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

Title:
  Gnome shell freezing and/or taking a long time to load

Status in gnome-shell package in Ubuntu:
  New

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/ubuntu/+source/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 2042909] Re: Gnome shell freezing and/or taking a long time to load

[Jesús Soto]

Here it is

** Attachment added: "prevjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042909/+attachment/5716749/+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/2042909

Title:
  Gnome shell freezing and/or taking a long time to load

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/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 2040977] Re: [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating on screen

[Daniel van Vugt]

** Summary changed:

- Mouse cursor stutters if nothing else is animating on screen
+ [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating on 
screen

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

Title:
  [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating
  on screen

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Using the touchpad on an X1 Carbon G10 with 90Hz OLED the mouse cursor
  stutters, unless something else is changing on screen (like running
  glmark2-wayland).

  Workaround:

  Put this in /etc/environment:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 15:48:28 2023
  InstallationDate: Installed on 2023-10-23 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-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: Gnome shell freezing and/or taking a long time to load

[Daniel van Vugt]

Thanks for the bug report. Next time it happens please reboot
immediately and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.


** Tags added: mantic

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

Title:
  Gnome shell freezing and/or taking a long time to load

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/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 2042909] [NEW] Gnome shell freezing and/or taking a long time to load

[Jesús Soto]

Public bug reported:

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

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


** Tags: mantic

-- 
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:
  Gnome shell freezing and/or taking a long time to load

Status in gnome-shell package in Ubuntu:
  Incomplete

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/ubuntu/+source/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 2037604] Re: Backport packages for 22.04.4 HWE stack

[Sameer Sharma]

** Description changed:

  [Impact]
- The graphics HWE stack from kinetic needs to be backported for 22.04.4
+ The graphics HWE stack from mantic needs to be backported for 22.04.4
  
  directx-headers
  - build-dep of the new Mesa
  
  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..
  
  [Test case]
  Install the new mesa on various hw, see that everything still works like 
before or better.
  
  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  New
Status in mesa source package in Jammy:
  New
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  Install the new mesa on various hw, see that everything still works like 
before or better.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions


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