[Desktop-packages] [Bug 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected

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

Title:
  Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme
  is selected

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

Bug description:
  1)Go to xorg
  2)Download Gnome Tweak Tool
  3)Select DMZ-white
  4)crash from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-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.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:38:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2024-04-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  MachineType: Acer Aspire A715-42G
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2063869] Re: Missing default cursor

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

Title:
  Missing default cursor

Status in Mutter:
  New
Status in dmz-cursor-theme package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse
  pointer works correctly when the pointer is over a window, but shows a
  pale grey square when over the desktop or Ubuntu top bar. This appears
  to happen because the /usr/share/icons/DMZ-White/cursors/default file
  (or symlink) is missing. Doing the following appears to fix the
  problem:

  1. cd /usr/share/icons/DMZ-White/cursors
  2. ln -s left_ptr default
  3. In gnome-tweaks change to some other mouse pointer.
  4. In gnome-tweaks change back to DMZ-White.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: dmz-cursor-theme 0.4.5ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 18:39:40 2024
  Dependencies:
   
  InstallationDate: Installed on 2020-07-14 (1382 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: dmz-cursor-theme
  UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago)

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


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

[Desktop-packages] [Bug 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

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

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

Title:
  Frequent boot to black display

Status in Plymouth:
  Fix Released
Status in SDDM:
  New
Status in systemd:
  New
Status in plymouth package in Ubuntu:
  Incomplete
Status in sddm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

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

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

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

Title:
  Frequent boot to black display

Status in Linux:
  Fix Released
Status in Plymouth:
  New
Status in SDDM:
  New
Status in systemd:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete
Status in sddm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

[Bug Watch Updater]

** Changed in: gnome-shell-extension-appindicator
   Status: Unknown => Fix Released

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

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


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

[Desktop-packages] [Bug 2063397] Re: extracting rar archives sometime incomplete

[Bug Watch Updater]

** Changed in: gnome-autoar
   Status: Unknown => New

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

Title:
  extracting rar archives sometime incomplete

Status in GNOME Autoar:
  New
Status in gnome-autoar package in Ubuntu:
  Triaged

Bug description:
  Extraction of rar files (v5) from the context menu ("Extract")
  occasionally results in one or more subfolders silently being skipped.

  This behavior is not systematic. Some rar archives extract properly,
  other ones do not.

  There is not any warning or error message when the problem manifests,
  which make it likely that the problem goes overlooked. I have
  effectively sustained data loss until I discovered that one of my
  extracted folders was much smaller than it should have been.

  I have unrar (non-free) and 7z installed.

  Applications like file-roller and arqiver appear to function properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 05:26:17 2024
  InstallationDate: Installed on 2022-03-27 (759 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   eiciel0.10.0-1build2
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2
   python3-nautilus  4.0-1build4

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


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

[Desktop-packages] [Bug 2059818] Re: Regression: Jammy to Noble, set_label no longer functions

[Bug Watch Updater]

** Changed in: gnome-shell-extension-appindicator
   Status: Unknown => Fix Released

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

Title:
  Regression: Jammy to Noble, set_label no longer functions

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, set_label can be used to set the text 
to display instead of an appindicator icon. In ubuntu noble set_label no longer 
functions at all.
  
https://gjs-docs.gnome.org/appindicator301~0.1/appindicator3.indicator#method-set_label

  [ Test Case ]

  - Download the test indicator and its dependencies:
* wget 
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js
* apt install gir1.2-appindicator3-0.1

  - Run the test indicator:
gjs -m testTool.js

  - Ensure the indicator icon shows up (it has an ubuntu icon)
  - Click on it and activate the "Set Label" item
  - A random numeric label should show next to the icon

  [ Regression potential ]

  The icon is not visible anymore

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


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

[Desktop-packages] [Bug 1786757] Re: Gnome Shell screencast doesn't work at desktop resolution 4880x1085

[Bug Watch Updater]

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

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

Title:
  Gnome Shell screencast doesn't work at desktop resolution 4880x1085

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/263

  ---

  Ubuntu 18 shows only black output on 3 monitor display screencast. I'm using 
desktop with videocard with 3 display output (HDMI, VGA, DVI). On dual monitor, 
screecast works fine while on 3 monitors the output is only black screen.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-06-08 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2058101] Re: Nautilus Move file dragging with the mouse no longer works

[Bug Watch Updater]

** Changed in: nautilus
   Status: Unknown => Fix Released

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

Title:
  Nautilus Move file dragging with the mouse no longer works

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Move file dragging with the mouse no longer works.
  see attached screencast

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46~beta-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 11:22:31 2024
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(733, 988)'
  InstallationDate: Installed on 2024-03-16 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240316)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.1-1
   nautilus-extension-gnome-terminal 3.51.90-1ubuntu1

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


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

[Desktop-packages] [Bug 2056772] Re: Properties of Audio Files Causes Lock Ups

[Bug Watch Updater]

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

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

Title:
  Properties of Audio Files Causes Lock Ups

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

Bug description:
  On SMB mounted file systems, right click properties on audio files
  causes the Nautilus to freeze. Force/Wait appears.

  The file system has read/write permission. Happens every time for
  large .flac files.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46~beta-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 11 10:33:22 2024
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'recursive-search' b"'always'"
   b'org.gnome.nautilus.preferences' b'show-directory-item-counts' b"'always'"
   b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1241, 1039)'
  InstallationDate: Installed on 2022-04-07 (704 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00
  usr_lib_nautilus:
   file-roller   43.1-1
   nautilus-extension-gnome-terminal 3.51.90-1ubuntu1
   nautilus-share0.7.5-0.3

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


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

[Desktop-packages] [Bug 2052996] Re: nautilus crashes when drag the image file

[Bug Watch Updater]

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

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

Title:
  nautilus crashes when drag the image file

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

Bug description:
  Repro Steps - `repro.webm` attached:

  1. Run nautilus
  2. Navigate to https://plugins.hex-rays.com/.
  3. Drag and drop the Hex-Rays logo onto the Desktop.
  4. SEGV at 0x000b

  
  Crash Report:

  ProblemType: Crash
  Signal: 11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 14:52:00 2024
  DistroRelease: Ubuntu 22.04
  JournalErrors:
   2월 13 14:51:57 dch3ck-Z790-UD nautilus[104092]: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_get_child: assertion 
'!g_path_is_absolute (name)' failed
2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_equal: assertion 
'G_IS_FILE (file2)' failed
2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_copy: assertion 
'G_IS_FILE (destination)' failed
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   LC_ADDRESS=ko_KR.UTF-8
   SHELL=/bin/bash
   LC_NAME=ko_KR.UTF-8
   LC_MEASUREMENT=ko_KR.UTF-8
   LC_TIME=ko_KR.UTF-8
   LC_MONETARY=ko_KR.UTF-8
   LANGUAGE=ko:en_AU:en_CA:en_GB:en_US:en
   LC_TELEPHONE=ko_KR.UTF-8
   LC_PAPER=ko_KR.UTF-8
   LC_NUMERIC=ko_KR.UTF-8
   PATH=(custom, no user)
   LANG=ko_KR.UTF-8
   LC_IDENTIFICATION=ko_KR.UTF-8

  * thread #7, name = 'pool-org.gnome.', stop reason = signal SIGSEGV: invalid 
address (fault address: 0x0)
  frame #0: 0x55b7dc24e624 nautilus`___lldb_unnamed_symbol4282 + 1140
  nautilus`___lldb_unnamed_symbol4282:
  ->  0x55b7dc24e624 <+1140>: movl   (%rax), %ebx
  0x55b7dc24e626 <+1142>: testl  %r12d, %r12d
  0x55b7dc24e629 <+1145>: je 0x55b7dc24ea60; <+2224>
  0x55b7dc24e62f <+1151>: movl   0x118(%rsp), %edx
  (lldb) bt
  * thread #7, name = 'pool-org.gnome.', stop reason = signal SIGSEGV: invalid 
address (fault address: 0x0)
* frame #0: 0x55b7dc24e624 nautilus`___lldb_unnamed_symbol4282 + 1140
  frame #1: 0x55b7dc24fdde nautilus`___lldb_unnamed_symbol4283 + 542
  frame #2: 0x7fb6019b1194 libgio-2.0.so.0`___lldb_unnamed_symbol5250 + 
116
  frame #3: 0x7fb6026876b4 libglib-2.0.so.0`___lldb_unnamed_symbol2565 
+ 116
  frame #4: 0x7fb602684a51 libglib-2.0.so.0`___lldb_unnamed_symbol2558 
+ 81
  frame #5: 0x7fb601294ac3 libc.so.6`start_thread(arg=) at 
pthread_create.c:442:8
  frame #6: 0x7fb601326850 libc.so.6`__clone3 at clone3.S:81
  (lldb) c
  Process 128770 resuming
  Process 128770 exited with status = 11 (0x000b)

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


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

[Desktop-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT

[Bug Watch Updater]

** Changed in: gnome-online-accounts
   Status: New => Fix Released

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

Title:
  goa-daemon crashed with SIGABRT

Status in gnome-online-accounts:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in librest package in Ubuntu:
  Fix Released
Status in librest source package in Kinetic:
  Fix Released

Bug description:
  * Impact

  The gnome-online-accounts sometime crash after resuming from suspend

  * Test case

  Install the librest update, restart your system and verify that
  configured online accounts keep working. Taking a Google account
  example, calendar events should show in gnome-calendar and the top
  panel widget, evolution should list your email account and nautilus
  should be able to browse your gdrive folder.

  We should also confirm that error reports stop with the library update

  * Regression potential

  The patch makes the code better handle an empty payload. The librest
  rdepends in the archive are gnome-initial-setup/gnome-online-
  accounts/gnome-maps so we should verify that those keep working as
  expected.

  -

  Unknown cause of this crash.  Was alerted to it after waking the
  system from sleep mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.45.2-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  Date: Mon Sep 19 19:26:29 2022
  ExecutablePath: /usr/libexec/goa-daemon
  InstallationDate: Installed on 2022-09-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917)
  ProcCmdline: /usr/libexec/goa-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 2063147] Re: No lower VRR range for display shown in Settings

[Bug Watch Updater]

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

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

Title:
  No lower VRR range for display shown in Settings

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

Bug description:
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  Package: mutter
  Version: 46.0-1ubuntu9

  
  mutter is built without libdisplay-info and this is required for having lower 
VRR range for display.

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


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

[Desktop-packages] [Bug 2060534] Re: Thunderbird doesn't always clean nstmp cache files

[Bug Watch Updater]

Launchpad has imported 38 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1878541.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-02-04T09:38:58+00:00 Omry Yadan wrote:

Created attachment 9378154
Screenshot_9.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 Edg/121.0.0.0

Steps to reproduce:

I am not sure how to trigger it.
I get system warnings about the disk being full and then I see a nstmp file 
using 1TB.
I deleted it, and hours later it happened again.
This have happened a few times for me in the past few weeks, but it seems to be 
happening more and more.

Additional context:
I am using imap. The entire mailbox on the server is 9.9GB.

Thunderbird 123.0b2 (64-bit)

OS:
Edition Windows 11 Pro
Version 22H2
Installed on‎22/‎01/‎2023
OS build22621.3007
Experience  Windows Feature Experience Pack 1000.22681.1000.0

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/0


On 2024-02-05T10:34:18+00:00 Mkmelin+mozilla wrote:

That's only used for compacting folders. 
https://searchfox.org/comm-central/rev/1452d8f1e1582cc44529f638e1eba1c7b3804fe4/mailnews/base/src/nsMsgFolderCompactor.cpp#393
The sent folder is also quite large, 50GB.

Is auto compact enabled, or do you do compaction only when it asks/or
manually?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/1


On 2024-02-05T11:19:45+00:00 Omry Yadan wrote:

> Is auto compact enabled, or do you do compaction only when it asks/or
manually?

I didn't change the setting, so I think it's probably enabled by default.
I dug through the settings now and was not able to locate it.

> The sent folder is also quite large, 50GB.
I noticed that too. I deleted it and it. The reconstructed file is 16GB.

> That's only used for compacting folders. https://searchfox.org/comm-
central/rev/1452d8f1e1582cc44529f638e1eba1c7b3804fe4/mailnews/base/src/nsMsgFolderCompactor.cpp#393

It looks like this function is not always cleaning up after itself.
For example, if an exception is thrown here,  CleanupTempFilesAfterError is 
never called:
https://searchfox.org/comm-central/rev/1452d8f1e1582cc44529f638e1eba1c7b3804fe4/mailnews/base/src/nsMsgFolderCompactor.cpp#411

Why not wrap it with a big "try finally" to always delete the file if it
exists when the function returns?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/2


On 2024-02-05T11:20:48+00:00 Omry Yadan wrote:

There is also the underlying question of why on earth the function is
creating a file that is 1TB in size. It sounds like there is a quadratic
usage of disk space in the compaction algorithm.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/3


On 2024-02-05T11:30:25+00:00 Omry Yadan wrote:

There is an attempt to clean up the file if it's still there in the destructor:
https://searchfox.org/comm-central/source/mailnews/base/src/nsMsgFolderCompactor.cpp#171-177

However, it only kicks in if NV_FAILED returns true.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/4


On 2024-02-05T13:11:17+00:00 Anjeyelf wrote:

Sounds like the Sent-1 file is so big it's not possible to do compacting
maybe because either Thunderbird is interrupted during the compacting
eg: shutdown, crash or receiving mail into the folder being compacted,
maybe another program is scanning the file or it's possible that you
might not be able to compact a large folder because you don't have
enough free disk space or memory or there is some type of corruption in
the file.  50GB is very large for a single text file and it looks like
it's been failing to compact for a while, so is full of old deleted
mail.

Does it say anything in the Error console ?
Open Error console (Ctrl + Shift + J') or 'Tools' > 'Developer Tools' > 'Error 
Console'
Clear Error console - top left bin icon

right click on 'Sent' folder and select 'compact'
If compacting does not work - Sent-1 is still 50Gb and  nsmtp appears.
What do you see in Error Console - please post an image.

Either way you need a solution to overcome the current issue.

Suggestion:
- Create a new folder called 'Sent Store'.
- Move all the wanted sent emails into 'Sent Store' as a precaution to 

[Desktop-packages] [Bug 2037015] Re: Screen corruption of slides during install on Raspberry Pi

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.webkit.org/show_bug.cgi?id=272827.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-04-17T15:47:22+00:00 Webkitbug wrote:

Created attachment 470961
Image of the artifacts.

All pages do not render properly in both the Eiphany and surf browsers
(see attached example). This is on a Raspberry Pi 4, running NixOS.
Here's the output of webkit://gpu in the Eiphany browser:

```
{
"Version Information": {
"WebKit version": "WebKitGTK 2.44.1 (tarball)",
"Operating system": "Linux 6.1.63 #1-NixOS SMP Tue Jan  1 00:00:00 UTC 
1980 aarch64",
"Desktop": "XFCE",
"Cairo version": "1.18.0 (build) 1.18.0 (runtime)",
"GStreamer version": "1.22.9 (build) GStreamer 1.22.9 (runtime)",
"GTK version": "4.12.5 (build) 4.12.5 (runtime)"
},
"Display Information": {
"Identifier": "1",
"Type": "X11",
"Screen geometry": "0,0 1920x1080",
"Screen work area": "0,27 1920x1053",
"Depth": "24",
"Bits per color component": "8",
"DPI": "96",
"VBlank type": "Timer",
"VBlank refresh rate": "60Hz",
"DRM Device": "/dev/dri/card0",
"DRM Render Node": "/dev/dri/renderD128"
},
"API": "OpenGL ES 2 (libepoxy)",
"Hardware Acceleration Information": {
"Policy": "always",
"WebGL enabled": "Yes",
"Renderer": "DMABuf (Supported buffers: Hardware, Shared Memory)",
"Native interface": "None"
},
"Hardware Acceleration Information (Render process)": {
"Platform": "GBM",
"GL_RENDERER": "V3D 4.2.14",
"GL_VENDOR": "Broadcom",
"GL_VERSION": "OpenGL ES 3.1 Mesa 24.0.3",
"GL_SHADING_LANGUAGE_VERSION": "OpenGL ES GLSL ES 3.10",
"GL_EXTENSIONS": "GL_EXT_blend_minmax GL_EXT_multi_draw_arrays 
GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_s3tc 
GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc 
GL_EXT_texture_format_BGRA GL_OES_compressed_ETC1_RGB8_texture 
GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap 
GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8 
GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float 
GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float 
GL_EXT_draw_instanced GL_EXT_texture_sRGB_decode GL_OES_EGL_image 
GL_OES_depth_texture GL_AMD_performance_monitor GL_OES_packed_depth_stencil 
GL_EXT_texture_type_2_10_10_10_REV GL_NV_conditional_render 
GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer 
GL_EXT_read_format_bgra GL_NV_pack_subimage GL_EXT_frag_depth 
GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_EGL_sync 
GL_OES_vertex_array_object G
 L_ANGLE_pack_reverse_row_order GL_ANGLE_texture_compression_dxt3 
GL_ANGLE_texture_compression_dxt5 GL_EXT_occlusion_query_boolean 
GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer 
GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_APPLE_sync 
GL_EXT_draw_buffers GL_EXT_instanced_arrays GL_EXT_map_buffer_range 
GL_KHR_debug GL_KHR_texture_compression_astc_ldr GL_NV_generate_mipmap_sRGB 
GL_NV_pixel_buffer_object GL_OES_depth_texture_cube_map 
GL_OES_required_internalformat GL_OES_surfaceless_context 
GL_EXT_color_buffer_float GL_EXT_debug_label GL_EXT_sRGB_write_control 
GL_EXT_separate_shader_objects GL_EXT_shader_implicit_conversions 
GL_EXT_shader_integer_mix GL_EXT_base_instance 
GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_copy_image 
GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex 
GL_EXT_polygon_offset_clamp GL_EXT_primitive_bounding_box 
GL_EXT_shader_io_blocks GL_EXT_texture_border_clamp 
GL_EXT_texture_cube_map_array GL_EXT_textur
 e_view GL_KHR_context_flush_control GL_NV_image_formats 
GL_NV_shader_noperspective_interpolation GL_OES_copy_image 
GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex 
GL_OES_primitive_bounding_box GL_OES_shader_io_blocks 
GL_OES_texture_border_clamp GL_OES_texture_cube_map_array 
GL_OES_texture_stencil8 GL_OES_texture_storage_multisample_2d_array 
GL_OES_texture_view GL_EXT_buffer_storage GL_EXT_float_blend 
GL_EXT_geometry_point_size GL_EXT_geometry_shader GL_KHR_no_error 
GL_KHR_texture_compression_astc_sliced_3d GL_OES_EGL_image_external_essl3 
GL_OES_geometry_point_size GL_OES_geometry_shader GL_OES_shader_image_atomic 
GL_EXT_clear_texture GL_EXT_texture_compression_s3tc_srgb 
GL_MESA_shader_integer_functions GL_EXT_color_buffer_half_float 
GL_EXT_texture_mirror_clamp_to_edge GL_KHR_parallel_shader_compile 
GL_EXT_EGL_image_storage GL_MESA_framebuffer_flip_y 

[Desktop-packages] [Bug 2062418] Re: gedit ships obsolete /usr/bin/gnome-text-editor alternative

[Bug Watch Updater]

** Changed in: gedit (Debian)
   Status: Unknown => Fix Released

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

Title:
  gedit ships obsolete /usr/bin/gnome-text-editor alternative

Status in gedit package in Ubuntu:
  In Progress
Status in gedit package in Debian:
  Fix Released

Bug description:
  gedit ships an entry for Debian's alternatives system for
  /usr/bin/gnome-text-editor and a corresponding manpage.

  However, there is now a real app named gnome-text-editor that ships
  /usr/bin/gnome-text-editor

  Therefore we should remove the entry in Debian's alternative system.

  A few more details on the Debian bug.

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


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

[Desktop-packages] [Bug 597825] Re: Menu accelerators in Firefox don't follow the GNOME policy.

[Bug Watch Updater]

** Bug watch added: github.com/mozilla-mobile/fenix/issues #25894
   https://github.com/mozilla-mobile/fenix/issues/25894

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

Title:
  Menu accelerators in Firefox don't follow the GNOME policy.

Status in Mozilla Firefox:
  Confirmed
Status in One Hundred Papercuts:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  The current GNOME default is that menu accelerators are hidden, and
  shown when you press the ALT key.

  Firefox doesn't observe this policy and have their menu accelerators
  displayed all the time.

  Also, pressing ALT alone in GNOME and Firefox doesn't invoke any menu
  command.

  This inconsistent behavior is a usability issue and also makes Ubuntu
  desktop look unprofessional.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  Architecture: amd64
  Date: Wed Jun 23 21:37:05 2010
  EcryptfsInUse: Yes
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  ProcEnviron:
   PATH=(custom, user)
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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


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

[Desktop-packages] [Bug 2062178] Re: Disable location services in gnome-control-center

[Bug Watch Updater]

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

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

Title:
  Disable location services in gnome-control-center

Status in gnome-control-center:
  New
Status in Release Notes for Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center package in Debian:
  New

Bug description:
  Impact
  --
  Mozilla Location Services will be closed to all third parties (including 
Ubuntu, GNOME, KDE, etc.) on June 12, 2024.

  Unfortunately, there does not appear to be any suitable replacement
  for our typical desktop and laptop users. (Mobile devices like phones
  may have GPS that could be used but those devices would only rarely be
  using Ubuntu and gnome-control-center.)

  To avoid later UI changes and disruption only a few months from now,
  the Ubuntu Desktop team would prefer to disable location services
  before Ubuntu 24.04 LTS is released.

  Details
  ---
  Specifically, this hides
  - Privacy & Security > Location
  - Date & Time > Automatic Timezone
  - Displays > Night Light > Schedule > Sunrise to Sunset 
+ This last one wasn't done yet, but I expect it for gnome-control-center 
46.1 which will be an SRU
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3014

  Other Info
  --
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2959

  gnome-control-center 46.1 to be released in a few days will also
  disable Location Services by default but with a build-time option for
  distros who have different deadlines and user profiles.

  If an alternative location provider is found that works well enough
  for our users, we intend to re-enable this feature with a Stable
  Release Update if possible.

  Because of this issue, Ubuntu has disabled the Location page in gnome-
  initial-setup for 24.04 LTS already.

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


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

[Desktop-packages] [Bug 1530142] Re: [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all playback write error (DMA or IRQ trouble?)

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=112721.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-02-20T18:02:16+00:00 sapjsm wrote:

Hi Folks,

new laptop (Dell 5559), new installation.

No sound, either on headphones or internal speakers. Have been all over
forums, tried every fix I can find.

Sound is not muted, and I believe the settings are correct, but it's
hard to be sure, as each answer I find seems to have slightly differing
advice, albeit a lot in common.

Submitted bug to Canonical, and they have requested I raise it with you.

Information:

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: john 2107 F pulseaudio
CurrentDesktop: Unity
Date: Wed Dec 30 14:25:38 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-12-24 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_AlsaPlaybackTestStderr:
 W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r
  x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o 
r
  T r a n s f e r f a i l e d : I n p u t / o u t p u t e r r o r
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: john 2107 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.6
dmi.board.name: 0664DJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/5


On 2016-02-20T20:24:28+00:00 tiwai wrote:

The kernel is way too old.  Try the latest 4.4.x or 4.5-rc kernel at
first.

If it still doesn't work, give alsa-info.sh output for further analysis.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/6


On 2016-02-21T21:35:31+00:00 sapjsm wrote:

(In reply to Takashi Iwai from comment #1)
> The kernel is way too old.  Try the latest 4.4.x or 4.5-rc kernel at first.
> 
> If it still doesn't work, give alsa-info.sh output for further analysis.

Hi,

you're saying that the kernel for the current long-term release of
Ubuntu, version 14.04 (Trusty Tahr) is too old?

Does that mean I have to upgrade to Ubuntu 15.04?  Or can I just do a
kernel upgrade?

Best regards,

John

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/7


On 2016-02-22T09:52:53+00:00 tiwai wrote:

(In reply to John M from comment #2)
> (In reply to Takashi Iwai from comment #1)
> > The kernel is way too old.  Try the latest 4.4.x or 4.5-rc kernel at first.
> > 
> > If it still doesn't work, give alsa-info.sh output for further analysis.
> 
> Hi,
> 
> you're saying that the kernel for the current long-term release of Ubuntu,
> version 14.04 (Trusty Tahr) is too old?

Yes.

> Does that mean I have to upgrade to Ubuntu 15.04?  Or can I just do a kernel
> upgrade?

At best, build the kernel by yourself.  If the problem is still seen
with the latest upstream kernel, report back here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/8


On 2016-02-22T20:29:33+00:00 sapjsm wrote:

Created attachment 204351
Screen capture after attempted upgrade

Screen capture after attempted upgrade to 4.5-rc

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/9


On 2016-02-22T20:33:49+00:00 sapjsm wrote:

Hi there Iwai,

I tried upgrading to 4.5-rc, but got errors.  I followed the
instructions for 64-bit at:

https://websetnet.com/install-linux-

[Desktop-packages] [Bug 2062178] Re: Disable location services in gnome-control-center

[Bug Watch Updater]

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

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

Title:
  Disable location services in gnome-control-center

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center package in Debian:
  Unknown

Bug description:
  Impact
  --
  Mozilla Location Services will be closed to all third parties (including 
Ubuntu, GNOME, KDE, etc.) on June 12, 2024.

  Unfortunately, there does not appear to be any suitable replacement
  for our typical desktop and laptop users. (Mobile devices like phones
  may have GPS that could be used but those devices would only rarely be
  using Ubuntu and gnome-control-center.)

  To avoid later UI changes and disruption only a few months from now,
  the Ubuntu Desktop team would prefer to disable location services
  before Ubuntu 24.04 LTS is released.

  Details
  ---
  Specifically, this hides
  - Privacy & Security > Location
  - Date & Time > Automatic Timezone
  - Displays > Night Light > Schedule > Sunrise to Sunset 
+ This last one wasn't done yet, but I expect it for gnome-control-center 
46.1 which will be an SRU
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3014

  Other Info
  --
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2959

  gnome-control-center 46.1 to be released in a few days will also
  disable Location Services by default but with a build-time option for
  distros who have different deadlines and user profiles.

  If an alternative location provider is found that works well enough
  for our users, we intend to re-enable this feature with a Stable
  Release Update if possible.

  Because of this issue, Ubuntu has disabled the Location page in gnome-
  initial-setup for 24.04 LTS already.

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


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

[Desktop-packages] [Bug 2062146] Re: MiniBrowser crashed with SIGSEGV

[Bug Watch Updater]

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

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

Title:
  MiniBrowser crashed with SIGSEGV

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  MiniBrowser crashed immediately on Raspberry Pi 400.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: libwebkit2gtk-4.1-0 2.44.0-2
  ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1
  Uname: Linux 6.8.0-1002-raspi aarch64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:32:12 2024
  ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser
  JournalErrors: -- No entries --
  ProcCmdline: ./MiniBrowser
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: webkit2gtk
  StacktraceTop:
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /lib/aarch64-linux-gnu/libgbm.so.1
   ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0
  Title: MiniBrowser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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


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

[Desktop-packages] [Bug 2062144] Re: xserver-xorg-video-nouveau 1:1.0.17-3 FTBFS on armhf

[Bug Watch Updater]

** Changed in: xorg-server (Debian)
   Status: Unknown => Confirmed

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

Title:
  xserver-xorg-video-nouveau 1:1.0.17-3 FTBFS on armhf

Status in xorg-server package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  xserver-xorg-video-nouveau 1:1.0.17-3 fails to build on armhf:

  ```
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=3 -I/usr/include/xorg -fvisibility=hidden 
-I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm 
-I/usr/include/libdrm -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/xserver-xorg-video-nouveau-1:1.0.17-3
 -Wall -I/usr/include/xorg -fvisibility=hidden -I/usr/include/pixman-1 
-I/usr/include/X11/dri -I/usr/include/libdrm -c ../../src/nv_shadow.c  -fPIC 
-DPIC -o .libs/nv_shadow.o
  ../../src/nv_driver.c: In function ‘NVScreenInit’:
  ../../src/nv_driver.c:1451:23: error: implicit declaration of function 
‘wfbScreenInit’; did you mean ‘fbScreenInit’? 
[-Werror=implicit-function-declaration]
   1451 | ret = wfbScreenInit(pScreen, FBStart, pScrn->virtualX,
    |   ^
    |   fbScreenInit
  ```

  This failure is fixed upstream in xorg-server via
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1114

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


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

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

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

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

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

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

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

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

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


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

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

[Bug Watch Updater]

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

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

Title:
  Update pipewire to 1.0.5

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

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

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

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

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


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

[Desktop-packages] [Bug 2061070] Re: gnome-shell-extension-desktop-icons-ng: Error: destroy() breaks...

[Bug Watch Updater]

** Changed in: gnome-shell-extension-desktop-icons-ng
   Status: New => Fix Released

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

Title:
  gnome-shell-extension-desktop-icons-ng: Error: destroy() breaks...

Status in Gnome Shell Extension Desktop Icons Ng:
  Fix Released
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  In Progress

Bug description:
  If i try to open "gnome-shell-extension-desktop-icons-ng" to configure
  through the extension manager this show this error:

  "
  Error: destroy() breaks tracking open dialogs, use close() if you must

  Stack trace:

destroy@resource:///org/gnome/Shell/Extensions/js/extensionPrefsDialog.js:63:13

fillPreferencesWindow/<@file:///usr/share/gnome-shell/extensions/d...@rastersoft.com/prefs.js:37:50

OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:141:41

_init/<@resource:///org/gnome/Shell/Extensions/js/extensionPrefsDialog.js:29:31

_init/GLib.MainLoop.prototype.runAsync/
  SourcePackage: gnome-shell-extension-desktop-icons-ng
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/2061070/+subscriptions


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

[Desktop-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade

[Bug Watch Updater]

** Changed in: archlinux-lp
   Status: Unknown => Fix Released

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

Title:
  Yubikey stopped working after noble upgrade

Status in Arch Linux on Launchpad:
  Fix Released
Status in gnupg2 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  Invalid

Bug description:
  In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
  since upgrading to Noble I get the following trying to access it.

  $ gpg --card-status
  gpg: selecting card failed: No such device 
  gpg: OpenPGP card not available: No such device

  If I run this as root it works:

  $ sudo gpg --card-status
  Reader ...: 1050:0407:X:0
  Application ID ...: D27600012401000609082616
  Application type .: OpenPGP
  Version ..: 2.1
  Manufacturer .: Yubico
  Serial number : 
  Name of cardholder: [not set]
  Language prefs ...: [not set]
  Salutation ...: 
  URL of public key : [not set]
  Login data ...: [not set]
  Signature PIN : not forced
  Key attributes ...: rsa4096 rsa4096 rsa2048
  Max. PIN lengths .: 127 127 127
  PIN retry counter : 10 0 10
  Signature counter : 1172
  UIF setting ..: Sign=off Decrypt=off Auth=off
  Signature key : 
created : 
  Encryption key: 
created : 
  Authentication key: [none]
  General key info..: [none]

  If I manually run pcscd.service then it stops working both as root and
  a user.

  $ sudo pkill -9 scdaemon
  $ sudo systemctl start pcscd.service
  $ gpg --card-status
  gpg: selecting card failed: No such device
  gpg: OpenPGP card not available: No such device
  $ sudo gpg --card-status
  gpg: selecting card failed: No such device
  gpg: OpenPGP card not available: No such device

  It might be worth mentioning I'm accessing the machine over SSH, so I
  also did experiment with a polkit rule like this:

  polkit.addRule(function(action, subject) {
  if (action.id == "org.debian.pcsc-lite.access_card" &&
  subject.isInGroup("sudo")) {
  return polkit.Result.YES;
  }
  });
  polkit.addRule(function(action, subject) {
  if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
  subject.isInGroup("sudo")) {
  return polkit.Result.YES;
  }
  });

  Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
  polkit.service in case this was a polkit issue, but this didn't do
  anything.

  
  Versions in noble:
  pcscd: 2.0.3-1build1
  libpcslite1: 2.0.3-1build1
  gnupg: 2.4.4-2ubuntu17
  scdaemon: 2.4.4-2ubuntu17

To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions


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

[Desktop-packages] [Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

[Bug Watch Updater]

** Changed in: mod-auth-mellon
   Status: Unknown => Fix Released

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

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in mod_auth_mellon:
  Fix Released
Status in hplip package in Ubuntu:
  Fix Released
Status in libapache2-mod-auth-mellon package in Ubuntu:
  New
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in hplip source package in Jammy:
  Fix Released
Status in libapache2-mod-auth-mellon source package in Jammy:
  Triaged
Status in ssl-cert source package in Jammy:
  Fix Released
Status in ssl-cert package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/990228:

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/mod-auth-mellon/+bug/1945774/+subscriptions


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

[Desktop-packages] [Bug 2061584] Re: Rendering issues in VirtualBox with 3d on (GTK ngl backend)

[Bug Watch Updater]

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

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

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 2013544] Re: font names displayed in an unreadable way

[Bug Watch Updater]

** Changed in: gnome-font-viewer
   Status: Unknown => New

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

Title:
  font names displayed in an unreadable way

Status in GNOME Font Viewer:
  New
Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  Hi,

  in the attached screenshot, font names in the 4th row are displayed in
  a vertical way that is unreadable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-font-viewer 44.0-1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Mar 31 14:30:35 2023
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/2013544/+subscriptions


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

[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

[Bug Watch Updater]

** Changed in: gtk
   Status: Unknown => 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/2061118

Title:
  Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in gtk4 source package in Noble:
  Triaged
Status in mesa source package in Noble:
  Triaged
Status in open-vm-tools source package in Noble:
  Invalid

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

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


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

[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => 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/2061118

Title:
  Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

Status in GTK+:
  Fix Released
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in gtk4 source package in Noble:
  Triaged
Status in mesa source package in Noble:
  Triaged
Status in open-vm-tools source package in Noble:
  Invalid

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

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


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

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Bug Watch Updater]

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

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  New

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Desktop-packages] [Bug 959823] Re: text in the quickfilter toolbar disappear

[Bug Watch Updater]

** Changed in: thunderbird
   Status: Confirmed => Invalid

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

Title:
  text in the quickfilter toolbar disappear

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

Bug description:
  When you deactivate and activate the quickfilter bar in mozilla
  thunderbird the text next to the icons in the quickfilter bar
  disappears until you restart the program

  reproduce:

  1) start thunderbird
  2) uncheck "quickfilter" and check it again in the toolbar
  3) notice that the text written next to the icons disappeared
  4) restart thunderbird and the text will appear again.

  this bug is reproducable and occurs every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: thunderbird 11.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lun4tic2102 F pulseaudio
  BuildID: 20120313203910
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 45'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,14627345,0011'
 Controls  : 45
 Simple ctrls  : 21
  Channel: release
  Date: Tue Mar 20 01:21:43 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   EDS Contact Integration - ID=edsintegrat...@mozilla.com, Version=0.3.9, 
minVersion=7.0, maxVersion=11.0a1, Location=app-global, Type=extension, 
Active=Yes
   German Dictionary - ID=de...@dictionaries.addons.mozilla.org, Version=2.0.2, 
minVersion=1.9a8pre, maxVersion=2.0.*, Location=app-profile, Type=extension, 
Active=Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.6  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Profiles: Profile0 (Default) - LastVersion=11.0/20120313203910 (Running)
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to precise on 2012-03-14 (5 days ago)
  WifiSyslog:
   
  dmi.bios.date: 11/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.4
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7395
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.4:bd11/06/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7395:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7395:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7395
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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


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

[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

[Bug Watch Updater]

** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

Status in GTK+:
  Fix Released
Status in gnome-shell package in Ubuntu:
  New
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in gnome-shell source package in Noble:
  New
Status in open-vm-tools source package in Noble:
  Invalid

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

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


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

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

[Bug Watch Updater]

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

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

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

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

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

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

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

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

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

  
  --

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

[Desktop-packages] [Bug 392109] Re: Impress: Custom animation not exported to pdf

[Bug Watch Updater]

Launchpad has imported 11 comments from the remote bug at
http://qa.openoffice.org/issues/show_bug.cgi?id=79453.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2007-07-10T20:51:14+00:00 Julien-touche wrote:

like http://www.openoffice.org/issues/show_bug.cgi?id=16036, it would be great
that export pdf could support animation & transition.
this is supported by pdf

see chapter 8 and 9 of
http://www.adobe.com/devnet/pdf/pdf_reference.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/0


On 2007-07-17T10:18:49+00:00 Christian-guenther-v wrote:

We export slide transitions but we have much more transitions then Acrobat 
Reader.
Therefore it is possible that you see another slide transition in the Acrobat
Reader then the seleced in OOo.
I didn't found information about custom animations in PDF.
Please tell me where I can find information about custom animations in PDF.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/1


On 2007-07-17T12:59:09+00:00 Julien-touche wrote:

i think slides transitions can be soled as one of the following options chosen
by user
- export only one which exist in both
- same but default chosen transition when none exists in pdf
- no transition.

Main point is animation. i've seen a pdf magazine with a lot of them, but i need
to find again the link.
else in pdf reference, version 1.7, animations can be done, i believe, through
3D streams (9.5.2) and transition actions (p. 670).

i'll try to find the above example when i will have more time in a few
weeks.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/2


On 2007-08-03T12:00:32+00:00 Christian-guenther-v wrote:

This is an enhancement.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/3


On 2008-04-22T19:57:26+00:00 Aurelien Naldi wrote:

*** Issue 79453 has been confirmed by votes. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/4


On 2008-08-09T08:43:48+00:00 Julien-touche wrote:

Please note pdf could also have embedded video which, i believe, is not
supported at this time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/5


On 2009-04-21T07:39:45+00:00 Xiang wrote:

I consider this feature is much important since there isn't a portable Impress
Viewer. As a result, hardly for a people to take odp files with himself 
anywhere.

Animation in pdf, I think, should deal with one situation first. That is, some
contents are overlaid by a textbox which appears after an extra click.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/6


On 2010-01-26T21:07:43+00:00 Operon-1 wrote:

I would definitely use a pdf export option to place the simple appear/disappear 
animations on separate pages of the pdf file.  

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/11


On 2010-10-22T14:49:31+00:00 Stuart Rossiter wrote:

I would agree with david1313 that basic Appear animations are by far the most 
crucial and useful; and probably the simplest to code, since this is "just" 
looping through the appeared elements, generating a new PDF page for each 
"snapshot". (I appreciate that the OpenOffice internals might mean this is 
*not* 
so simple to code!)

And I'd also guess that Appears animations are by far the most common of all 
the 
custom animations.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/392109/comments/12


On 2011-05-23T09:15:35+00:00 Martin wrote:

(In reply to comment #8)
> I would agree with david1313 that basic Appear animations are by far the most 
> crucial and useful; and probably the simplest to code, since this is "just" 
> looping through the appeared elements, generating a new PDF page for each 
> "snapshot". 
The extension ExpandAnimations does exactly this with "appear" and "disappear" 
animations 
(http://github.com/downloads/monperrus/ExpandAnimations/ExpandAnimations-latest.oxt).

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

[Bug Watch Updater]

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1838902] Re: GNOME Control Center hangs for some time when I add other keyboard in settings

[Bug Watch Updater]

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

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

Title:
  GNOME Control Center hangs for some time when I add other keyboard in
  settings

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

Bug description:
  But then the list of languages opens and I can choose needing variant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.32.2-1ubuntu4
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  4 22:30:32 2019
  InstallationDate: Installed on 2019-08-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1991496] Re: Permission denied when trying to open a pdf file form Google Drive

[Bug Watch Updater]

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

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

Title:
  Permission denied when trying to open a pdf file form Google Drive

Status in Evince:
  New
Status in evince package in Ubuntu:
  Triaged

Bug description:
  I logged into Google Drive on Gnome Online Accounts, and I can access my 
Google Drive files from nautilus.
  However, when I try to open a pdf file from said folder, I can't open it. I 
get a "permission denied".

  Other files open fine. Okular is also able to open the pdf file.

  See attached screenshot with the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: evince 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  2 17:27:12 2022
  InstallationDate: Installed on 2022-02-02 (242 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: evince
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (3 days ago)

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


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

[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage

[Bug Watch Updater]

** Changed in: transmission (Debian)
   Status: New => Confirmed

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Fix Released
Status in transmission source package in Jammy:
  Fix Released
Status in transmission source package in Lunar:
  Fix Released
Status in transmission package in Debian:
  Confirmed

Bug description:
  [ Impact ]

  There is a memory leak in transmission-daemon that was introduced by a
  faulty openssl3 patch. It has been reported that it's noticeable after
  a few hours of seeding/downloading torrent files, less than a day.

  [ Test Plan ]

  Being a memory leak, there is no immediate/quick test that can be
  performed, other than letting it run for a few hours and measure
  memory consumption "before" and "after". comment #5 mentions about 1Gb
  of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not
  for how long it was running.

  comment #20 says that after 24h using the patched version from a PPA
  build, the memory consumption was steady at 300Mb.

  I'd suggest a 24h test and that it should stay under 1Gb of RAM.

  [ Where problems could occur ]

  The patch loads the default and legacy openssl3 providers. This will
  potentially change the set of algorithms available to the application,
  compared to what was there before. That being said, the legacy
  provider is a conservative approach, and the likely result is that
  *more* algorithms will become available, and not less. This is also
  the approach I have seen in other applications that were rebuilt using
  openssl3 instead of openssl1.1.

  It does seem safer than the original patch, which was manually
  handling ciphers, in particular RC4, and, well, introduced the memory
  leak.

  [ Other Info ]

  Patch came from gentoo.

  [ Original Description ]
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a 
Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  Description:Ubuntu 22.04 LTS
  Release:22.04

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


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

[Desktop-packages] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => Fix Released

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in xwayland package in Ubuntu:
  Triaged
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Released
Status in xwayland source package in Jammy:
  Fix Released
Status in xorg-server source package in Mantic:
  Fix Released
Status in xwayland source package in Mantic:
  Fix Released
Status in xorg-server source package in Noble:
  Triaged
Status in xwayland source package in Noble:
  Triaged

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (II) AIGLX: Suspending AIGLX clients for VT switch
  (EE) Server terminated with error (1). Closing log file.

  Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like
  security backports were done incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2060354/+subscriptions


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

[Desktop-packages] [Bug 2060319] Re: tracker failing autopkgtest on noble

[Bug Watch Updater]

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

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

Title:
  tracker failing autopkgtest on noble

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Confirmed

Bug description:
  tracker's autopkgtest is failing. I have reported this issue upstream.
  Our autopkgtest configuration is similar but not identical to our
  build test configuration which does pass.

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


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

[Desktop-packages] [Bug 1971076] Re: webkitgtk 2.36 doesn't work with orca anymore

[Bug Watch Updater]

** Changed in: gnome-orca
   Status: New => Fix Released

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

Title:
  webkitgtk 2.36 doesn't work with orca anymore

Status in gnome-orca:
  Fix Released
Status in orca package in Ubuntu:
  Fix Released
Status in orca source package in Focal:
  Fix Released
Status in orca source package in Impish:
  Fix Released
Status in orca source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  webkitgtk apps are no longer readable by Ubuntu's default screen reader.

  This regression was introduced with webkit2gtk 2.36. That version was
  a major security update and has been pushed to Ubuntu 20.04 LTS and
  Ubuntu 21.10.

  There are many apps that use webkitgtk: evolution, epiphany, yelp,
  etc.

  Test Case
  -
  1. Install evolution
  2. Open evolution and configure an email account.
  3. Install the update
  4. Open the Ubuntu/GNOME Settings app. In the left sidebar, select 
Accessibility.
  5. Click Screen Reader and turn it on.
  6. Open Evolution. Open an email in a new window. Select the body text area 
of the email.

  The Screen Reader should read the text on that line.

  What Could Go Wrong
  --
  For Ubuntu 21.10, we are just cherry-picking 2 commits from the stable 
gnome-40 branch.

  We are also cherry-picking those 2 commits to Ubuntu 20.04 LTS.

  Original Bug Report
  ---
  Since Ubuntu 22.04 I can not read the content of the yelp pages, le content 
of a mail from evolution or a web page from epiphany.
  This worked correctly for Ubuntu 21.10 or Ubuntu 20.04 LTS.
  This problem occurs if I migrate from a previous version, or if I reinstall 
from scrash.

  Is there a new setting that I don't aware of?
  This also could be related to webkitgtk I suppose.

  A work arround is to select all the texte and to copy it to a place
  that I can read (gedit).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: orca 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sun May  1 10:03:38 2022
  InstallationDate: Installed on 2022-04-03 (27 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: orca
  UpgradeStatus: Upgraded to jammy on 2022-04-12 (18 days ago)
  mtime.conffile..etc.xdg.autostart.orca-autostart.desktop: 
2022-04-17T10:13:33.207956

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


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

[Desktop-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures

[Bug Watch Updater]

** Changed in: gst-python1.0 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Debian:
  Fix Released

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

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


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

[Desktop-packages] [Bug 2060319] Re: tracker failing autopkgtest on noble

[Bug Watch Updater]

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

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

Title:
  tracker failing autopkgtest on noble

Status in Tracker:
  New
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Unknown

Bug description:
  tracker's autopkgtest is failing. I have reported this issue upstream.
  Our autopkgtest configuration is similar but not identical to our
  build test configuration which does pass.

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


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

[Desktop-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures

[Bug Watch Updater]

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

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Confirmed

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

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


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

[Desktop-packages] [Bug 2060282] Re: Giflib 5.2.2-1 fails to build

[Bug Watch Updater]

** Changed in: giflib (Debian)
   Status: Unknown => Confirmed

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

Title:
  Giflib 5.2.2-1 fails to build

Status in giflib package in Ubuntu:
  Fix Committed
Status in giflib package in Debian:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/721167206/buildlog_ubuntu-noble-
  amd64.giflib_5.2.2-1_BUILDING.txt.gz

  Upstream bug: https://sourceforge.net/p/giflib/bugs/170/

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


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

[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

[Bug Watch Updater]

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

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the
  code being modified.

  [ Original Description ]

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

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

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


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

[Desktop-packages] [Bug 2060319] Re: tracker failing autopkgtest on noble

[Bug Watch Updater]

** Changed in: tracker (Debian)
   Status: Unknown => Confirmed

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

Title:
  tracker failing autopkgtest on noble

Status in Tracker:
  New
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Confirmed

Bug description:
  tracker's autopkgtest is failing. I have reported this issue upstream.
  Our autopkgtest configuration is similar but not identical to our
  build test configuration which does pass.

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


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

[Desktop-packages] [Bug 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)

[Bug Watch Updater]

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

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

Title:
  [regression] Windows flicker to black when resizing (Intel Apollo
  Lake)

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  I see the black zones, small windows breaks. For additional details, I use 
eoan-proposed and eoan-backports packages.
  You can see this problem in my video: 
https://photos.app.goo.gl/3rvLkqJj6hZwSscw9

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  5 13:39:13 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (3 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2060028] Re: [Noble] No VRR is shown in GNOME Shell 46 for i915

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

Title:
  [Noble] No VRR is shown in GNOME Shell 46 for i915

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

Bug description:
  Hi,

  mutter (46.0-1ubuntu6)
  gnome-shell (46.0-0ubuntu3.1)
  VRR activated in dconf/mutter
  i915

  I do not get VRR in Display tab of g-c-c, for my external monitor or my 
laptop's display alone.
  I did restart my computer after VRR was activated in dconf.

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


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

[Desktop-packages] [Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11

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

Title:
  Input lag in native terminal on Nvidia desktops with X11

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

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

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

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


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

[Desktop-packages] [Bug 2059825] Re: Super key doesn't work when panel is selected

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/2059825

Title:
  Super key doesn't work when panel is selected

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Go to desktop.
  Press super key, and see that the workspace viewer shows up.
  Go back to desktop.
  Press the panel such that a popup appears (time to open 
notifications+calendar, system tray, keyboard switcher, accessibility menu).
  Press super key, and the workspace viewer does not show up.

  I think this is a bug, because the super key should always work to
  switch application, as it is a 'rescue' button for users who got lost
  and don't know what they are doing.

  Same happens for alt-tab and super-tab.

  Ubuntu 23.10
  GNOME version 45.2
  Wayland
  Linux Kernel 6.5.0-26-generic

  Unfortunately I can't make an account on askubuntu to report this bug
  there, because when I try to make an account, Launchpad asks for which
  type of access I would like to give askubuntu, I press the highest
  permissions level, then it says "launchpad error try logging in
  again".

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


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

[Desktop-packages] [Bug 1990630] Re: tracker-extract-3 crashed with signal 31 in __GI_epoll_create1()

[Bug Watch Updater]

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

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

Title:
  tracker-extract-3 crashed with signal 31 in __GI_epoll_create1()

Status in Tracker:
  Fix Released
Status in tracker-miners package in Ubuntu:
  Fix Released

Bug description:
  Impact
  --
  As seen by the number of duplicates, this is the most common tracker crash 
seen in Ubuntu 22.10.

  According to seeded-in-ubuntu, tracker-miners is included by default
  only in the Ubuntu Desktop flavor

  error after upgrade from 22.04 to 22.10

  https://errors.ubuntu.com/problem/4f257ae91411857c6bb9266de343d7f189a68474

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: tracker-extract 3.4.0-1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Sep 23 09:31:40 2022
  ExecutablePath: /usr/libexec/tracker-extract-3
  InstallationDate: Installed on 2022-05-11 (134 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcCmdline: /usr/libexec/tracker-extract-3
  Signal: 31
  SourcePackage: tracker-miners
  StacktraceTop:
   __GI_epoll_create1 () at ../sysdeps/unix/syscall-template.S:120
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: tracker-extract-3 crashed with signal 31 in __GI_epoll_create1()
  UpgradeStatus: Upgraded to kinetic on 2022-09-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 2043517] Re: gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)

[Bug Watch Updater]

** Changed in: xorg-server
   Status: New => Fix Released

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

Title:
  gnome-shell on non-active VT busy-loops through libwayland-server.so
  (sometimes)

Status in X.Org X server:
  Fix Released
Status in mutter package in Ubuntu:
  New
Status in xwayland package in Ubuntu:
  New

Bug description:
  I run several gnome sessions at once - different users on different
  Virtual Terminals.

  Sometimes, gnome-shell for a non-active VT starts using 100% CPU.  Or,
  actually 99% CPU because it's doing IPC as well.  And the
  corresponding XWayland uses 40% CPU.

  FWIW, sending SIGSTOP to either gnome-shell or XWayland stops the
  other one from busy-looping as well.

  If I switch back to the affected VT, it appears to function fine, but
  it is still using 100% + 40% CPU.

  
  Version numbers:

  Ubuntu 22.04.3 LTS
  gnome-shell 42.9-0ubuntu2
  xwayland 2:22.1.1-1ubuntu0.7

  
  $ ps -aux | grep 'alan .*gnome-shell$'
  alan9248 26.1  3.4 5492888 269136 ?  Rsl  19:54  30:26 
/usr/bin/gnome-shell

  $ sudo strace -p 9248 2>&1|head
  strace: Process 9248 attached
  epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}], 
32, 0) = 1
  recvmsg(21, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\1\0\0\0\0\0\f\0\3\0\0\0", iov_len=752}, {iov_base="", 
iov_len=3344}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 12
  write(4, "\1\0\0\0\0\0\0\0", 8) = 8
  sendmsg(21, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\3\0\0\0\0\0\f\0[\2\0\0\1\0\0\0\1\0\f\0\3\0\0\0", 
iov_len=24}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 
MSG_DONTWAIT|MSG_NOSIGNAL) = 24
  poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, 
{fd=19, events=POLLIN}, {fd=20, events=POLLIN}, {fd=23, events=POLLIN}, {fd=24, 
events=POLLIN}, {fd=25, events=POLLIN}, {fd=34, events=POLLIN}, {fd=36, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=54, events=POLLIN}, {fd=63, 
events=POLLIN}, {fd=66, events=POLLIN}], 14, 79809702) = 2 ([{fd=4, 
revents=POLLIN}, {fd=37, revents=POLLIN}])
  read(4, "\2\0\0\0\0\0\0\0", 16) = 8
  write(4, "\1\0\0\0\0\0\0\0", 8) = 8
  epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}], 
32, 0) = 1

  
  The recvmsg() call is here:

  #0  __libc_recvmsg (fd=21, msg=0x7fff1de64a50, flags=1073741888) at 
../sysdeps/unix/sysv/linux/recvmsg.c:35
  #1  0x7f2531ea5ad6 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #2  0x7f2531ea4eea in wl_event_loop_dispatch () at 
/lib/x86_64-linux-gnu/libwayland-server.so.0
  #3  0x7f2531d2b45b in wayland_event_source_dispatch (base=, callback=, data=)
  at ../src/wayland/meta-wayland.c:110
  #4  0x7f2532b42d3b in g_main_dispatch (context=0x55c0046cc8f0) at 
../../../glib/gmain.c:3419
  #5  g_main_context_dispatch (context=0x55c0046cc8f0) at 
../../../glib/gmain.c:4137
  #6  0x7f2532b98258 in g_main_context_iterate.constprop.0
  (context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1, 
self=) at ../../../glib/gmain.c:4213
  #7  0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at 
../../../glib/gmain.c:4413
  #8  0x7f2531cd0b79 in meta_context_run_main_loop 
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
  at ../src/core/meta-context.c:437
  #9  0x55c003cf4f12 in main (argc=, argv=) 
at ../src/main.c:650

  
  The sendmsg() call is here:

  Thread 1 "gnome-shell" hit Breakpoint 1, __libc_sendmsg (fd=21, 
msg=0x7fff1de64c50, flags=16448) at ../sysdeps/unix/sysv/linux/sendmsg.c:26
  26../sysdeps/unix/sysv/linux/sendmsg.c: No such file or directory.
  (gdb) where
  #0  __libc_sendmsg (fd=21, msg=0x7fff1de64c50, flags=16448) at 
../sysdeps/unix/sysv/linux/sendmsg.c:26
  #1  0x7f2531ea1c9d in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #2  0x7f2531ea565e in wl_display_flush_clients () at 
/lib/x86_64-linux-gnu/libwayland-server.so.0
  #3  0x7f2531d2b437 in wayland_event_source_prepare 
(base=base@entry=0x55c004a374d0, timeout=timeout@entry=0x7fff1de64dc4)
  at ../src/wayland/meta-wayland.c:97
  #4  0x7f2532b428e7 in g_main_context_prepare (context=0x55c0046cc8f0, 
priority=0x7fff1de64e50) at ../../../glib/gmain.c:3739
  #5  0x7f2532b98123 in g_main_context_iterate.constprop.0
  (context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1, 
self=) at ../../../glib/gmain.c:4193
  #6  0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at 
../../../glib/gmain.c:4413
  #7  0x7f2531cd0b79 in meta_context_run_main_loop 
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
  at ../src/core/meta-context.c:437
  #8  0x55c003cf4f12 in main (argc=, argv=) 
at ../src/main.c:650

To manage 

[Desktop-packages] [Bug 2028819] Re: File-Roller should depend on 7zip package instead of abandoned p7zip-full since version 43

[Bug Watch Updater]

** Changed in: file-roller (Debian)
   Status: New => Fix Released

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

Title:
  File-Roller should depend on 7zip package instead of abandoned p7zip-
  full since version 43

Status in file-roller package in Ubuntu:
  New
Status in file-roller package in Debian:
  Fix Released

Bug description:
  File-Roller switched from p7zip to official 7zip utility since version
  43.alpha , see

  
https://gitlab.gnome.org/GNOME/file-roller/-/commit/b798bbd96d3777c20026f1dc2d3e15ecb5bc853d
  and 
https://gitlab.gnome.org/GNOME/file-roller/-/commit/a4359d11e05023605c4270c67ad703bc8a71f8fd

  but File-Roller Ubuntu/Debian package version 43-1 still depends on abandoned 
by upstream p7zip-full, while it should depend on 7zip package instead of 
p7zip-full 
  or maybe better to have "Depends: 7zip | p7zip-full" ?

  There are lots of bugs in p7zip, for example some large zip files cannot be 
extract on 16.02 but can on 9.20, see 
https://sourceforge.net/p/p7zip/discussion/383044/ and
  http://bugs.debian.org/src:p7zip also 
https://bugs.launchpad.net/ubuntu/+source/p7zip

  It seems Debian developers planing to replace p7zip-full with official
  7zip package, see https://bugs.debian.org/991428

  Also there is a related note in NEWS file:
   - Distros will want to adjust the `data/packages.match` file.

  Some archive managers in Ubuntu/Debian already depends on official
  7zip package instead of p7zip, see arqiver for example.

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


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

[Desktop-packages] [Bug 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

[Bug Watch Updater]

** Changed in: mesa (Debian)
   Status: Confirmed => Fix Released

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Fix Released

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 1997553] Re: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed

[Bug Watch Updater]

** Changed in: network-manager
   Status: New => Fix Released

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

Title:
  network-manager fails to trigger dispatcher scripts with action
  dhcp4-change when dhcp lease is renewed

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  We rely on network-manager dispatcher scripts on our desktop and
  laptop computers. The dispatcher scripts are used to update DNS
  records with nsupdate when the dhcp lease is renewed.

  With jammy this is not working anymore. It seems that dispatcher
  scripts are run only when the interface comes up (with action 'up')
  and with the initial dhcp lease (with action 'dhcp4-change'), but when
  the lease is renewed, the dispatcher scripts are not run with any
  action. The only action the dispatcher scripts are run regularly with
  is 'connectivity-change', which seems to occur twice in a row every
  few hours.

  I have made a simple script to log how the dispatcher scripts are run:
  /etc/NetworkManager/dispatcher.d/99-test:
  #!/bin/bash
  PATH='/bin:/sbin:/usr/bin:/usr/sbin'

  echo $(date) 0: $0 IFACE: $1 ACTION: $2 >> /tmp/nm.log

  This script proves that action 'dhcp4-change' only occurs when I
  manually restart NetworkManager.service or unplug and replug the
  ethernet cable.


  network-manager version: 1.36.6-0ubuntu2

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


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

[Desktop-packages] [Bug 2059033] Re: Xorg crashes with SIGABRT

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => 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/2059033

Title:
  Xorg crashes with SIGABRT

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915
  graphics driver.  I am seeing random Xorg crashes due to SIGABRT,
  which kicks me back to the login screen.

  Ubuntu version: 22.04
  Kernel version: 5.19.0-50-generic
  libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 

  I am seeing this message in kern.log:

  i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617]

  I have also gotten a core dump; here is the track trace:

  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140131874372224) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=6, threadid=140131874372224) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #3  0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #4  0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79
  #5  0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352
  #6  0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879
  #7  0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal 
%d (%s). Server aborting\n") at ../../../../os/log.c:1017
  #8  0x560c5cc72abd in OsSigHandler (unused=, 
sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156
  #9  OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at 
../../../../os/osinit.c:110
  #10 
  #11 __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140131874372224) at ./nptl/pthread_kill.c:44
  #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at 
./nptl/pthread_kill.c:78
  #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79
  #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, 
file=, line=) at 
../src/gallium/drivers/iris/iris_batch.c:1116
  #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, 
out_fence=0x0, flags=) at 
../src/gallium/drivers/iris/iris_fence.c:267
  #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at 
../src/mesa/state_tracker/st_cb_flush.c:60
  #19 st_glFlush (ctx=, gallium_flush_flags=0) at 
../src/mesa/state_tracker/st_cb_flush.c:94
  #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, 
timeout=0x713af054) at ../../../../glamor/glamor.c:285
  #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, 
timeout=0x713af054) at 
../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701
  #22 0x560c5cb01095 in BlockHandler 
(pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394
  #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:201
  #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492
  #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, 
envp=) at ../../../../dix/main.c:272
  #26 0x7f72fec29d90 in __libc_start_call_main 
(main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, 
argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58
  #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , 
argc=11, argv=0x713af268, init=, fini=, 
rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392
  #28 0x560c5cae9605 in _start ()

  This post describes a similar issue:
  https://gitlab.freedesktop.org/drm/intel/-/issues/4858

  I tried using a workaround from the above link, to set GPU to max
  frequency using command "intel_gpu_frequency -m", this seemed to
  reduce the rate of occurrence from once per day to once every 3 days,
  but this is not a permanent solution.

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


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

[Desktop-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

[Bug Watch Updater]

** Changed in: gobject-introspection (Debian)
   Status: New => Fix Released

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Debian:
  Fix Released

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+subscriptions


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

[Desktop-packages] [Bug 1988754] Re: libreoffice writer crashes when edit the page break

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Fix Released => Confirmed

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

Title:
  libreoffice writer crashes when edit the page break

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+subscriptions


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

[Desktop-packages] [Bug 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Fix Released

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions


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

[Desktop-packages] [Bug 192056] Re: [Upstream] [hardy] Cannot Open password-encrypted MS Office 2003 files

[Bug Watch Updater]

Launchpad has imported 37 comments from the remote bug at
http://qa.openoffice.org/issues/show_bug.cgi?id=46307.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2005-03-30T15:25:29+00:00 Thomas-hovezak wrote:

when trying to open an password-encrypted ppt you get following message:

read error
the loading of password-encrypted Microsoft PowerPoint presentation is not
supported..

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/0


On 2005-03-30T15:31:59+00:00 Thomas-hovezak wrote:

Created attachment 24419
the ppt file which caused the issue

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/1


On 2005-03-30T16:13:16+00:00 Wolframgarten wrote:

Changed to defect, reassigned.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/2


On 2005-04-06T15:16:11+00:00 Christian-guenther-v wrote:

set to new and change the target.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/3


On 2005-04-06T15:20:00+00:00 Christian-guenther-v wrote:

With the internal bug 115982 you fixed something about password protected 
PPT-Files.
Why can't we load this file.
Has  this file another encryption?
Please have a look.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/4


On 2005-04-26T11:11:54+00:00 Sven-jacobi wrote:

sj->cgu: As you can read in 115982 PowerPoint is providing RC4 encryption only,
and RC4 is not be supported by OOo. That time I added the new error message"read
error the loading of password-encrypted Microsoft PowerPoint presentation is not
supported.." so that you are not getting the general io error if trying to load
protected files.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/5


On 2005-05-02T18:40:41+00:00 Christian-guenther-v wrote:

OOo should support RC4 encryption to load Password protected PPT-Files.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/6


On 2005-05-23T13:54:49+00:00 Bettina-haberer wrote:

Set issue type, target and keywords.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/7


On 2006-03-09T09:03:44+00:00 Christian-guenther-v wrote:

*** Issue 62955 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/8


On 2006-05-15T08:47:49+00:00 Wolframgarten wrote:

*** Issue 65376 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/9


On 2007-12-19T09:05:43+00:00 Marcelly-bernard wrote:

We can see in various OOo forums that PowerPoint files password protected for 
modifications, but not protected for reading, are becoming common.

Windows users (Win 200 and above) can display them with the free PowerPoint 
Viewer 
2007.
But users of other OS (Linux, Mac) cannot read these PowerPoint files.

This is a real lack of compatibility for OpenOffice.org in the non-
Microsoft world.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/10


On 2008-04-07T09:18:17+00:00 Wolframgarten wrote:

*** Issue 61691 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/17


On 2008-04-07T09:18:38+00:00 Wolframgarten wrote:

*** Issue 87922 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/18


On 2008-04-07T09:28:22+00:00 Cno wrote:

added 'Powerpoint' to the issues summary

Reply at:

[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript

[Bug Watch Updater]

** Changed in: firefox
   Status: Confirmed => Fix Released

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

Title:
  [snap] chromium snap does not allow to read symlinks to
  /usr/share/javascript

Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1) Install chromium snap
  snap install chromium
  2) Install openjdk-21 documentation
  sudo apt install openjdk-21-doc
  3) Browse API documentation
  chromium /usr/share/doc/openjdk-21-doc/api/index.html

  The search bar is inactive and dev console contains:
  jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND

   
  $ls -l 
/usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js
  lrwxrwxrwx 1 root root 43 Mar 17 13:31 
/usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> 
../../../../javascript/jquery/jquery.min.js

  cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js
  prints the file contents

  Downloaded version of chrome opens documentation with active search bar and 
no javascript errors
  /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html

  Expected results:

  Chromium snap should be able to follow symlink into
  /usr/share/javascript and correctly load OpenJDK API documentation.

  Note: this probably should be a specific exclusion for Debian-based
  systems.

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


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

[Desktop-packages] [Bug 1826544] Re: media button to disable touchpad not working

[Bug Watch Updater]

** Changed in: gnome-settings-daemon
   Status: New => Fix Released

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

Title:
  media button to disable touchpad not working

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I have an ASUS UX305CA laptop and after upgrading to 18.04 I am no
  longer able to disable the touchpad by hitting Fn+F9 .  When I hit
  Fn+F9 it shows the graphic indicating that it's disabling the
  touchpad, but the touchpad continues to work.  I tried using a LiveUSB
  copy of 18.04 and it the button works fine, so there seems to be
  something related to upgrading.  I upgrading from 16.04 where it
  worked fine before.

  I'm not sure which package to file this bug against, sorry.

  Here are some details:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  $ lsmod | grep asus
  asus_nb_wmi28672  0
  asus_wmi   28672  1 asus_nb_wmi
  sparse_keymap  16384  1 asus_wmi
  wmi24576  1 asus_wmi
  video  45056  2 asus_wmi,i915
  asus_wireless  16384  0
  $ dconf read /org/gnome/desktop/peripherals/touchpad/send-events
  'enabled'
   
  I also went through a diff between gsettings on the LiveUSB and my current 
install and nothing stood out to me as being related.  I do have 
`org.gnome.desktop.interface gtk-im-module 'ibus'` which differs from LiveUSB 
which is set to 'gtk-im-context-simple', but I don't know if it's related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1826544/+subscriptions


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

[Desktop-packages] [Bug 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

[Bug Watch Updater]

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

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Confirmed

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 2057851] Re: abseil: FTBFS on arm{el,hf}:

[Bug Watch Updater]

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

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

Title:
  abseil: FTBFS on arm{el,hf}:

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

Bug description:
  Imported from Debian bug http://bugs.debian.org/1065770:

  Source: abseil
  Version: 20220623.1-3.1
  Severity: serious
  Tags: ftbfs
  Justification: fails to build from source (but built successfully in the past)
  X-Debbugs-Cc: sramac...@debian.org

  
https://buildd.debian.org/status/fetch.php?pkg=abseil=armel=20220623.1-3.1=1709076797=0

  182/182 Test  #83: absl_random_beta_distribution_test
  .   Passed  110.45 sec

  98% tests passed, 3 tests failed out of 182

  Total Test time (real) = 113.40 sec

  The following tests FAILED:
165 - absl_mutex_test (Subprocess aborted)
166 - absl_notification_test (Failed)
167 - absl_per_thread_sem_test (Failed)
  Errors while running CTest
  make[2]: *** [Makefile:74: test] Error 8

  Cheers
  -- 
  Sebastian Ramacher

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


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

[Desktop-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

[Bug Watch Updater]

** Changed in: gobject-introspection
   Status: New => Fix Released

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Debian:
  New

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+subscriptions


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

[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386

[Bug Watch Updater]

** Changed in: openjdk-8 (Debian)
   Status: New => Fix Released

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

Title:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386

Status in java-atk-wrapper package in Ubuntu:
  New
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Debian:
  Fix Released

Bug description:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to
  dependency on java-atk-bridge.

  This dependency was introduced by dropping condition present in 392:
  --
    ifeq ($(derivative),Ubuntu)
  ifeq ($(DEB_HOST_ARCH),i386)
    ifeq (,$(filter $(distrel),precise trusty xenial bionic))
  with_bridge =
    endif
  endif
    endif
  --

  Note:
   java-atk-wrapper is present in noble on i386

  This is a regression introduced in 8u402-ga-2:

    * Restore M-A installability of focal/i386 package (LP#1916327)
  by adding xenial, bionic, focal, jammy to the list of releases
  built with the ATK bridge, but not enabling it by default;
  keep jessie on, stretch and sid and mantic/noble off the list:
  please report bugs for issues with the bridge, so sthibault
  can find, debug, fix them

  See LP: #1916327

  The alternative is to publish atk-wrapper for i386 in mantic, jammy
  and focal.

  Options:
   a) rollback the fix in Ubuntu
   b) publish atk-wrapper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions


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

[Desktop-packages] [Bug 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

[Bug Watch Updater]

** Changed in: evolution-ews
   Status: New => Fix Released

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  Fix Released
Status in evolution-ews package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  Earlier I could add outlook.com to gnome calendar with exchange in
  Gnome online accounts and evolution-ews installed, now Microsoft has
  changed something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

  edit 10.3.24: upgraded to Ubuntu 23.10 and it still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+subscriptions


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

[Desktop-packages] [Bug 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

[Bug Watch Updater]

** Changed in: mesa (Debian)
   Status: Unknown => 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/2054851

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Confirmed

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures

[Bug Watch Updater]

** Changed in: gst-python1.0 (Debian)
   Status: Unknown => Confirmed

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  New
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Confirmed

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

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


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

[Desktop-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures

[Bug Watch Updater]

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

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  New
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Unknown

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

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


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

[Desktop-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

[Bug Watch Updater]

** Changed in: gobject-introspection (Debian)
   Status: Unknown => New

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  New
Status in gobject-introspection package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gobject-introspection package in Debian:
  New

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+subscriptions


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

[Desktop-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

[Bug Watch Updater]

** Changed in: gobject-introspection
   Status: Unknown => New

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  New
Status in gobject-introspection package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gobject-introspection package in Debian:
  Unknown

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+subscriptions


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

[Desktop-packages] [Bug 2039801] Re: Locate pointer not working when animations are disabled

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/2039801

Title:
  Locate pointer not working when animations are disabled

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2056671] Re: Mouse pointer toggle in the screenshot/screencast dialog is hard to discover

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/2056671

Title:
  Mouse pointer toggle in the screenshot/screencast dialog is hard to
  discover

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Press the Print Screen button, select the Record Screen option and
  then press capture [1]. The screen recording works as expected however
  does not display the mouse cursor making it hard to use the screen
  capture for a tutorial without using a third-party capture device.

  The screen cast should capture the mouse pointer by default. Or [1]
  you include an option to show/hide the mouse pointer in the recording.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 12:04:47 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06b9]
  InstallationDate: Installed on 2024-03-10 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Dell Inc. OptiPlex 7040
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=6b60e9f2-5ca2-4299-85bd-4fb992af91dd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 096JG8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd07/14/2022:br1.24:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn096JG8:rvrA01:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

[Bug Watch Updater]

** Changed in: fontconfig (Debian)
   Status: Confirmed => Fix Released

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Fix Released

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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

[Desktop-packages] [Bug 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

[Bug Watch Updater]

** Changed in: evolution-ews
   Status: Fix Released => New

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  New
Status in evolution-ews package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  Earlier I could add outlook.com to gnome calendar with exchange in
  Gnome online accounts and evolution-ews installed, now Microsoft has
  changed something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

  edit 10.3.24: upgraded to Ubuntu 23.10 and it still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+subscriptions


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

[Desktop-packages] [Bug 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

[Bug Watch Updater]

** Changed in: evolution-ews
   Status: Unknown => Fix Released

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  Fix Released
Status in evolution-ews package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  
  Earlier I could add outlook.com to gnome calendar with exchange in Gnome 
online accounts and evolution-ews installed, now Microsoft has changed 
something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+subscriptions


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

[Desktop-packages] [Bug 1825227] Re: gnome-calendar overcompensates time zone difference in web ics calendar

[Bug Watch Updater]

** Changed in: gnome-calendar
   Status: New => Fix Released

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

Title:
  gnome-calendar overcompensates time zone difference in web ics
  calendar

Status in GNOME Calendar:
  Fix Released
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  Upon adding a web ics calendar (via Evolution due to Bug #1825224),
  the events from this calendar were not properly time-compensated for
  my time zone. While Evolution and Gnome Shell displayed the time of my
  events properly, gnome-calendar displayed the events 7 hours in the
  past, likely attempting to compensate for my time zone (GMT -7).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:47:17 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2043517] Re: gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => New

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

Title:
  gnome-shell on non-active VT busy-loops through libwayland-server.so
  (sometimes)

Status in X.Org X server:
  New
Status in mutter package in Ubuntu:
  New
Status in xwayland package in Ubuntu:
  New

Bug description:
  I run several gnome sessions at once - different users on different
  Virtual Terminals.

  Sometimes, gnome-shell for a non-active VT starts using 100% CPU.  Or,
  actually 99% CPU because it's doing IPC as well.  And the
  corresponding XWayland uses 40% CPU.

  FWIW, sending SIGSTOP to either gnome-shell or XWayland stops the
  other one from busy-looping as well.

  If I switch back to the affected VT, it appears to function fine, but
  it is still using 100% + 40% CPU.

  
  Version numbers:

  Ubuntu 22.04.3 LTS
  gnome-shell 42.9-0ubuntu2
  xwayland 2:22.1.1-1ubuntu0.7

  
  $ ps -aux | grep 'alan .*gnome-shell$'
  alan9248 26.1  3.4 5492888 269136 ?  Rsl  19:54  30:26 
/usr/bin/gnome-shell

  $ sudo strace -p 9248 2>&1|head
  strace: Process 9248 attached
  epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}], 
32, 0) = 1
  recvmsg(21, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\1\0\0\0\0\0\f\0\3\0\0\0", iov_len=752}, {iov_base="", 
iov_len=3344}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 12
  write(4, "\1\0\0\0\0\0\0\0", 8) = 8
  sendmsg(21, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\3\0\0\0\0\0\f\0[\2\0\0\1\0\0\0\1\0\f\0\3\0\0\0", 
iov_len=24}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 
MSG_DONTWAIT|MSG_NOSIGNAL) = 24
  poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, 
{fd=19, events=POLLIN}, {fd=20, events=POLLIN}, {fd=23, events=POLLIN}, {fd=24, 
events=POLLIN}, {fd=25, events=POLLIN}, {fd=34, events=POLLIN}, {fd=36, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=54, events=POLLIN}, {fd=63, 
events=POLLIN}, {fd=66, events=POLLIN}], 14, 79809702) = 2 ([{fd=4, 
revents=POLLIN}, {fd=37, revents=POLLIN}])
  read(4, "\2\0\0\0\0\0\0\0", 16) = 8
  write(4, "\1\0\0\0\0\0\0\0", 8) = 8
  epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}], 
32, 0) = 1

  
  The recvmsg() call is here:

  #0  __libc_recvmsg (fd=21, msg=0x7fff1de64a50, flags=1073741888) at 
../sysdeps/unix/sysv/linux/recvmsg.c:35
  #1  0x7f2531ea5ad6 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #2  0x7f2531ea4eea in wl_event_loop_dispatch () at 
/lib/x86_64-linux-gnu/libwayland-server.so.0
  #3  0x7f2531d2b45b in wayland_event_source_dispatch (base=, callback=, data=)
  at ../src/wayland/meta-wayland.c:110
  #4  0x7f2532b42d3b in g_main_dispatch (context=0x55c0046cc8f0) at 
../../../glib/gmain.c:3419
  #5  g_main_context_dispatch (context=0x55c0046cc8f0) at 
../../../glib/gmain.c:4137
  #6  0x7f2532b98258 in g_main_context_iterate.constprop.0
  (context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1, 
self=) at ../../../glib/gmain.c:4213
  #7  0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at 
../../../glib/gmain.c:4413
  #8  0x7f2531cd0b79 in meta_context_run_main_loop 
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
  at ../src/core/meta-context.c:437
  #9  0x55c003cf4f12 in main (argc=, argv=) 
at ../src/main.c:650

  
  The sendmsg() call is here:

  Thread 1 "gnome-shell" hit Breakpoint 1, __libc_sendmsg (fd=21, 
msg=0x7fff1de64c50, flags=16448) at ../sysdeps/unix/sysv/linux/sendmsg.c:26
  26../sysdeps/unix/sysv/linux/sendmsg.c: No such file or directory.
  (gdb) where
  #0  __libc_sendmsg (fd=21, msg=0x7fff1de64c50, flags=16448) at 
../sysdeps/unix/sysv/linux/sendmsg.c:26
  #1  0x7f2531ea1c9d in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #2  0x7f2531ea565e in wl_display_flush_clients () at 
/lib/x86_64-linux-gnu/libwayland-server.so.0
  #3  0x7f2531d2b437 in wayland_event_source_prepare 
(base=base@entry=0x55c004a374d0, timeout=timeout@entry=0x7fff1de64dc4)
  at ../src/wayland/meta-wayland.c:97
  #4  0x7f2532b428e7 in g_main_context_prepare (context=0x55c0046cc8f0, 
priority=0x7fff1de64e50) at ../../../glib/gmain.c:3739
  #5  0x7f2532b98123 in g_main_context_iterate.constprop.0
  (context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1, 
self=) at ../../../glib/gmain.c:4193
  #6  0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at 
../../../glib/gmain.c:4413
  #7  0x7f2531cd0b79 in meta_context_run_main_loop 
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
  at ../src/core/meta-context.c:437
  #8  0x55c003cf4f12 in main (argc=, argv=) 
at ../src/main.c:650

To manage notifications about this 

[Desktop-packages] [Bug 2056331] Re: [SRU] fix suspend/resume when there are no input devices

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => Fix Released

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

Title:
  [SRU] fix suspend/resume when there are no input devices

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  Bug is impacting the suspend/resume flow when there is no input device
  connected to machine. xorg hangs in this case.

  [Where problems could occur]

  The problem could occur in places where there is no input device
  connected to the system but a suspend/resume is triggered.

  [Test Case]

  * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed)
  * Update xorg-server to the version in -proposed: sudo apt install -t 
jammy-proposed xorg-server
  * Unplug all USB devices such as USB drive, keyboard, mouse, etc.
  * Set RTC timer and suspend the system via UART console
  $ echo 8 > /proc/sys/kernel/printk
  $ sudo rtcwake -v -m no -s 240
  $ sudo systemctl suspend

  [Regression Potential]

  The patch defines a default behavior in systemd_logind_drop_master
  function so there is a possibility that there might be a regression
  that may affect all the systems that utilizes
  systemd_logind_drop_master

  
  Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2056331/+subscriptions


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

[Desktop-packages] [Bug 2055762] Re: Closing window button doesn't appear correctly on the second display

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/2055762

Title:
  Closing window button doesn't appear correctly on  the second display

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  If toggle it to the Activity task, its closing window button on second 
display (other monitor) is showed as well, however if toggle it to the Program 
Menu then the X button doesn't show completely.
  I attached a recorded explains it. Please observe the left screen's X button.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-23 (469 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ko_KR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags: jammy wayland-session third-party-packages
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom cvdnetwork dip kvm libvirt lpadmin lxd plugdev render 
sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2052913] Re: Large Performance Regression in fullscreen windows from Ubuntu Jammy to Ubuntu Noble

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

Title:
  Large Performance Regression in fullscreen windows from Ubuntu Jammy
  to Ubuntu Noble

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

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

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported

[Bug Watch Updater]

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

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2056079] Re: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Bug Watch Updater]

** Changed in: gst-plugins-good
   Status: Unknown => New

** Changed in: pipewire
   Status: Unknown => Fix Released

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

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

Status in gst-plugins-good:
  New
Status in PipeWire:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 release, to the outdated Pulseaudio
  16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even if pipewire is used as
  desktop sound server in recent Ubuntu releases, given that many audio
  applications still access pipewire via its pulseaudio frontend
  (package pipewire-pulse). See pipewire bug
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

  The bug in libpulse.so.0, reported against Pulseaudio 16 in
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
  been fixed for the Pulseaudio 17 release.

  See the following merge request for the following trivial one-liner
  patch that would need to be backported to Ubuntu's current
  implementation:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

  I hoped that Pulseaudio 17 would be included in Debian in time for
  integration into Ubuntu 24.04-LTS, but apparently not much maintenance
  of pulseaudio is happening on the Debian side at the moment.

  Given that this bug affects all Ubuntu versions since Ubuntu
  22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio
  15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at
  least for the upcoming 24.04-LTS.

  Alternatively it would have been great to get Pulseaudio upgraded to
  version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
  apparently that is too late now, according to
  https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

  Thanks,
  -mario

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/2056079/+subscriptions


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

[Desktop-packages] [Bug 2022954] Re: RDP and VNC fail when headless with no monitor (but work otherwise!)

[Bug Watch Updater]

** Changed in: gnome-remote-desktop
   Status: New => Fix Released

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

Title:
  RDP and VNC fail when headless with no monitor (but work otherwise!)

Status in GNOME Remote Desktop:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  *  Install fresh Ubuntu 22.04.2 LTS
  *  Enable RDP and VNC via sharing control panel
  *  Test RDP and VNC, verify working
  *  Unplug monitor
  *  Try RDP.  Authenticate, then connection closed with no display
  *  Try VNC.  Authenticate, then connection closed with no display
  *  Plug monitor back in
  *  Try RDP.  Works!
  *  Try VNC.  Works!
  *  Unplug monitor
  *  Try RDP.  AUthenticate, then connection closed with no display
  *  Try VNC.  Authenticate, then connection closed with no display
  *  GOTO 10

  Symptoms are present with both wayland and X11.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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 Jun  5 11:02:41 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: ZOTAC International (MCO) Ltd. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [19da:b301]
  InstallationDate: Installed on 2023-06-01 (4 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ZOTAC ZBOX-CI323NANO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_j45abz@/vmlinuz-5.19.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_j45abz ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B301P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI323NANO
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB301P027:bd09/11/2019:br5.11:svnZOTAC:pnZBOX-CI323NANO:pvrXX:rvnZOTAC:rnZBOX-CI323NANO:rvrXX:cvnDefaultstring:ct3:cvrDefaultstring:skuN/A:
  dmi.product.family: N/A
  dmi.product.name: ZBOX-CI323NANO
  dmi.product.sku: N/A
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~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.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-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/gnome-remote-desktop/+bug/2022954/+subscriptions


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

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

[Bug Watch Updater]

** Changed in: thunderbird
   Status: New => Expired

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Fix Released
Status in Mozilla Thunderbird:
  Expired
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

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


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

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.altlinux.org/show_bug.cgi?id=29591.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-11-18T17:19:32+00:00 Norbert wrote:

Description of problem:
In previous GNOME versions (for example, in 3.4) I was able to set keyboard 
layout switching to Alt+Shift, Ctrl+Shift, both Shifts, etc. In AltLinux p7 I 
can't set it from gnome-control-center keyboard.
This bug come from GNOME.

Version-Release number of selected component (if applicable):
gnome-control-center 3.8.6-alt0.M70P.1

How reproducible:
Go to gnome-control-center keyboard and try to set Alt+Shift or Ctrl+Shift as 
layout switching keys.


Steps to Reproduce:
1. Go to gnome-control-center keyboard (Shortcuts -> Typing)
2. Try to set Alt+Shift or Ctrl+Shift at 'Switch to next input source'
3. Get 'Disabled' in 'Switch to next input source'. 

If you set default Super+Space - it set and work normally, but it is not
comfortable and universal for all users.

This bug is very hot in Ubuntu 13.10 too (689 users are affected, see
https://bugs.launchpad.net/bugs/1218322), but Canonical fixed it.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/365


On 2013-11-19T09:35:16+00:00 Aris-x wrote:

Shortcuts -> Typing -> Modifiers-only switch to next source

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/367


On 2013-11-19T09:52:54+00:00 Norbert wrote:

Спасибо, Юрий!
Но сочетания Ctrl+Shift+C/V на русской раскладке в терминале и выделение текста 
по Ctrl+Shift+стрелки не работают если переключение поставлено на привычное 
Ctrl+Shift. Мне создать новый багрепорт здесь или писать сразу в апстрим?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/369


On 2013-11-19T11:42:45+00:00 Aris-x wrote:

Это у вас с одной стороны не работает, -- используйте другую. В апстрим 
написать можете, но проще приспособиться. 
Мне, например, правым Ctrl-ом удобно переключаться.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/371


On 2013-11-19T12:42:09+00:00 Norbert wrote:

Спасибо! Действительно "другая сторона" работает. Но в апстрим я все-
таки написал (https://bugzilla.gnome.org/show_bug.cgi?id=712667).

Этот (29591) баг можем закрывать. Спасибо!

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/372


On 2024-02-29T18:28:11+00:00 Lav-7 wrote:

(Ответ для Nikolay Strelkov на комментарий #2)
> Спасибо, Юрий!
> Но сочетания Ctrl+Shift+C/V на русской раскладке в терминале и выделение
> текста по Ctrl+Shift+стрелки не работают если переключение поставлено на
> привычное Ctrl+Shift. Мне создать новый багрепорт здесь или писать сразу в
> апстрим?
Есть задача и патч, исправляющий поведение (делает переключение раскладки при 
_отжатии_ клавиш):
https://bugzilla.altlinux.org/34900
Также эта проблема не актуальна для wayland.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/549


** Changed in: gnome-control-center (ALT Linux)
   Status: Unknown => Invalid

** Changed in: gnome-control-center (ALT Linux)
   Importance: Unknown => Medium

** Bug watch added: bugzilla.gnome.org/ #712667
   https://bugzilla.gnome.org/show_bug.cgi?id=712667

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

  - 

[Desktop-packages] [Bug 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)

[Bug Watch Updater]

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

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

Title:
  Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform /
  framebuffer-get-bits (due to Mesa >= 23.1.1)

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

Bug description:
  [ Impact ]

  Mutter's test cases fail on jammy since Mesa got updated:

  mutter:cogl+cogl/conform / framebuffer-get-bits

  [ Test Plan ]

  Build mutter and run its tests (done automatically during packaging)

  [ Where problems could occur ]

  More tests fail.

  [ Other Info ]

  27/113 mutter:cogl+cogl/conform / framebuffer-get-bits
RUNNING
  >>> RUN_TESTS_QUIET=1 
PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py 
/<>/cogl/tests/run-tests.sh 
/<>/obj-s390x-linux-gnu/cogl/tests/config.env 
cogl/tests/conform/test-conformance test_framebuffer_get_bits
  ― ✀  ―
  Starting D-Bus daemons (session & system)...
  Starting mocked services...
  Running test case...
     Test GL+GLSL  GL3   ES2
   test_framebuffer_get_bits: ok FAIL   n/a
  Traceback (most recent call last):
    File "/<>/src/tests/meta-dbus-runner.py", line 184, in 
  test_case.wrap_call(rest[1:])
    File "/<>/src/tests/meta-dbus-runner.py", line 171, in 
wrap_call
  self.assertEqual(p.wait(), 0)
    File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual
  assertion_func(first, second, msg=msg)
    File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual
  raise self.failureException(msg)
  AssertionError: 134 != 0
  ――
   27/113 mutter:cogl+cogl/conform / framebuffer-get-bits   
 FAIL 2.35s   exit status 1

  and

   27/113 mutter:cogl+cogl/conform / framebuffer-get-bits   
 RUNNING
  >>> MALLOC_PERTURB_=159 
PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py 
/<>/cogl/tests/run-tests.sh 
/<>/obj-aarch64-linux-gnu/cogl/tests/config.env 
cogl/tests/conform/test-conformance test_framebuffer_get_bits
  ― ✀  ―
  Starting D-Bus daemons (session & system)...
  Starting mocked services...
  Running test case...
     Test GL+GLSL  GL3   ES2
   test_framebuffer_get_bits: ok FAIL   n/a
  Traceback (most recent call last):
    File "/<>/src/tests/meta-dbus-runner.py", line 184, in 
  test_case.wrap_call(rest[1:])
    File "/<>/src/tests/meta-dbus-runner.py", line 171, in 
wrap_call
  self.assertEqual(p.wait(), 0)
    File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual
  assertion_func(first, second, msg=msg)
    File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual
  raise self.failureException(msg)
  AssertionError: 134 != 0
  ――
   27/113 mutter:cogl+cogl/conform / framebuffer-get-bits   
 FAIL 0.83s   exit status 1

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


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

[Desktop-packages] [Bug 2036388] Re: Login screen grey background flickers

[Bug Watch Updater]

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

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

Title:
  Login screen grey background flickers

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  Login screen grey background flickers on startup and again on login.
  It looks like it's trying to fade between two very similar shades of
  grey and there just aren't enough colours between them to fade
  smoothly.

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


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

[Desktop-packages] [Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears

[Bug Watch Updater]

** Changed in: yaru
   Status: Unknown => 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/1872594

Title:
  Ubuntu logo shifts vertically when the login screen appears

Status in Yaru Theme:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in plymouth package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  Ubuntu logo shifts upward about 1px when the purple login screen
  appears.

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


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

[Desktop-packages] [Bug 1962566] Re: gnome-shell crash after resume from suspend in gdm/util.js:154

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  gnome-shell crash after resume from suspend in gdm/util.js:154

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  ### Affected version
  * Your OS and version: ubuntu 22.04 (dev series, before release)
  * Affected GNOME Shell version: 41.3-1ubuntu1
  * Issue appears in Wayland

  ### Bug summary

  Sometimes gnome-shell hangs when I open the laptop to login from the
  suspend state, preventing the rest of gdm to load. Because I am
  running wayland, I cannot open another tty either. If I close the
  laptop lid again and wait 30s or so and reopen to retry, it will work.

  ### Steps to reproduce
  Not 100% reproducible, happens sometimes.
  1. open laptop to login from suspend
  2. see login screen with time and all looks normal but is unresponsive

  ### What happened

  
  The login screen is hung and unresponsive to clicks/touches(touchscreen)/any 
keyboard input events.

  ### What did you expect to happen

  The login screen should be responsive to input.

  ### Relevant logs, screenshots, screencasts etc.

  After a successful login, I see a crash in journalctl:

  ```
  Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error 
calling StartServiceByName for net.reactivated.Fprint: Failed to activate 
service 'net.reactivated.>
    
_injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25
    
_makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17
    
ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31
    
_init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30
    
_ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28
    
_showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14
    
vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14
  ```

  

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.2-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Tue Mar  1 09:58:16 2022
  ExecutablePath: /usr/libexec/fprintd
  ExecutableTimestamp: 1645749862
  InstallationDate: Installed on 2020-06-29 (609 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/libexec/fprintd
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: fprintd
  UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago)
  UserGroups: N/A

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


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

[Desktop-packages] [Bug 2036388] Re: Login screen grey background flickers

[Bug Watch Updater]

** Changed in: yaru
   Status: Unknown => 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/2036388

Title:
  Login screen grey background flickers

Status in Yaru Theme:
  New
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in yaru-theme package in Ubuntu:
  In Progress

Bug description:
  Login screen grey background flickers on startup and again on login.
  It looks like it's trying to fade between two very similar shades of
  grey and there just aren't enough colours between them to fade
  smoothly.

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


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

[Desktop-packages] [Bug 1825710] Re: Remove "Application is ready" notification

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  Remove "Application is ready" notification

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  The "Application is ready" notification is pointless, really. Say, I
  click on the open downloads folder button in Firefox and GNOME Shell
  gives me a notification saying "Application is ready" but doesn't open
  the notification. I'm totally expecting an app to open because I
  actively initiated it.

  As a workaround, I'm using a GNOME extensions "Focus my Window" which
  removes the "Application is ready" message and focuses the app window
  automatically. However, this cannot be treated as a solution.

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


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

[Desktop-packages] [Bug 1949291] Re: LibreOffice has started displaying a donation nag

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Fix Released

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

Title:
  LibreOffice has started displaying a donation nag

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I just opened up a spreadsheet (technically a CSV file, but who's
  counting), to discover LibreOffice displaying an eye-catching blue
  "Your donations support our worldwide community." banner just below
  the toolbars and about a toolbar and a half tall.

  This irritating nag is apparently supposed to display every 90 to 180
  days with no in-application means to disable it permanently, and
  there's apparently also a "Help us make LibreOffice even better!"
  banner that can appear too.

  According to this blog post...

  https://www.remembertheusers.com/2019/11/0580-libreoffice-nag-
  notices.html

  ...it is not responsive to configuration overrides within the user
  profile and the only apparent solution that doesn't require patching
  the source and rebuilding is to create a file containing the following
  markup in `$BASEDIR/share/registry`
  (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu
  package):

  
  http://www.w3.org/2001/XMLSchema; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:oor="http://openoffice.org/2001/registry;>

http://openoffice.org/2004/installation; oor:name="Setup" 
oor:package="org.openoffice">
  

  0


  0

  

  

  Regardless of how it's achieved, I think it's tasteless, irritating,
  and probably doesn't give a very good image to any office customers
  Ubuntu may have downstream for random employees to be receiving nag
  banners like that in IT-installed software.

  Please consider patching it out or otherwise ensuring it never
  triggers in distro-provided builds of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 04:32:03 2021
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1949291/+subscriptions


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

[Desktop-packages] [Bug 2054667] Re: Displays in the settings app can't be overlapped

[Bug Watch Updater]

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

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

Title:
  Displays in the settings app can't be overlapped

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

Bug description:
  I have three displays: the laptop internal display and two 24"
  external displays. In the Gnome settings app, the displays can be
  overlapped, but then the Apply button is greyed out so I can't press
  it.

  The error message is "Changes Cannot be Applied, This could be due to
  hardware limitations."

  I wasn't actually trying to overlap the displays originally, but just
  change the arrangement of the displays. I found the solution
  accidentally, i.e. I didn't overlap the displays, and then the Apply
  button worked.

  1) Ubuntu 22.04.4 LTS
  2) gnome-control-center: Installed: 1:41.7-0ubuntu0.22.04.8

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 10:29:16 2024
  InstallationDate: Installed on 2024-02-21 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

[Bug Watch Updater]

** Changed in: fontconfig (Debian)
   Status: New => Confirmed

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Confirmed

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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

[Desktop-packages] [Bug 2054769] Re: Boot animation and login screen use different display scales

[Bug Watch Updater]

** Changed in: plymouth
   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/2054769

Title:
  Boot animation and login screen use different display scales

Status in Plymouth:
  New
Status in mutter package in Ubuntu:
  Won't Fix
Status in plymouth package in Ubuntu:
  Fix Committed

Bug description:
  Boot animation and login screen use different display scales, on some
  (not many) machines.

  For example on a Microsoft Surface Laptop 4, Plymouth seems to use
  scale 2 for the boot screen while GNOME selects scale 1 for the login
  screen. This means the Ubuntu logo shrinks.

  I've tried a few laptops and so far it's only the Surface Laptop 4
  that has the problem: 13.5" 2256x1504, 201 PPI

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


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