date:20240327

This bug was fixed in the package ubuntu-release-upgrader - 1:24.04.9

---
ubuntu-release-upgrader (1:24.04.9) noble; urgency=medium

  * Revert "tests: fix some more deb822 tests"
  * Run pre-build.sh: updating po files, mirrors, and demotions.

 -- Nick Rosbrook   Thu, 14 Mar 2024 14:18:50 -0400

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Edubuntu upgrade removed universe repo mantic -> noble

Status in software-properties package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  Upon upgrade from mantic to noble, my bare metal Edubuntu install
  removed the Universe repo from the installation and, therefore, did
  not upgrade any Edubuntu-specific packages. I suspect this was caused
  by the apt DEB-822 upgrade to the repo and not detecting the universe
  repo as required by the Edubuntu installation.

  As Edubuntu looks identical to Ubuntu Desktop in terms of installation
  on the surface due to it also being a GNOME desktop, I suspect an
  assumption may have been derived from this.

  Additionally, simply trying `add-apt-repository universe` was
  ineffective, so that might need some work as well.

  Will attach logs if I can find them, but please do advise what logs you need.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-03-04 (366 days ago)
  InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 
(20230304)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
  Tags: noble wayland-session dist-upgrade
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: Upgraded to noble on 2024-03-01 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2053228] Re: software-properties-gtk does not start

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

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

  * Handle backup and restore of deb822 sources (LP: #2053228)

software-properties (0.99.43) noble; urgency=medium

  * Fix autopkgtest: Make sure directory exists before trying to create file
in it (LP: #2058035).

 -- Julian Andres Klode   Wed, 20 Mar 2024 13:18:16
+0100

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

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2058035] Re: [SRU] Create directories for apt configuration files if they are absent

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

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

  * Handle backup and restore of deb822 sources (LP: #2053228)

software-properties (0.99.43) noble; urgency=medium

  * Fix autopkgtest: Make sure directory exists before trying to create file
in it (LP: #2058035).

 -- Julian Andres Klode   Wed, 20 Mar 2024 13:18:16
+0100

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

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

Title:
  [SRU] Create directories for apt configuration files if they are
  absent

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed

Bug description:
  Impact
  --

  The autopkgtest for 0.96.20.12, which introduces Ubuntu Pro in
  Xenial's software-properties, failed on Dbus tests[1].

  The failure is because, at some point in time, the .keep file were
  removed from the otherwise empty tests/aptroot/etc/apt/apt.conf.d/.
  This caused the Git repository to drop
  tests/aptroot/etc/apt/apt.conf.d/ and also its parent, which also
  became empty, and the tests try to directly create files in those
  directories, raising the error.

  It seems that previous uploaders did not use the Git checkout, as the
  offending commit was introduced in Jun 2019 and there were subsequent
  uploads that did contain those empty directories.

  Test case
  -

  Trigger an autopkgtest against the proposed package version. It must
  succeed.

  Regression Potential
  

  Although the introduced change is idempotent, there could be other
  part of the code assuming the directories didn't exist and trying to
  create them with a "fail if already exists" approach, causing a
  runtime regression.

  [1]
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  xenial/xenial/amd64/s/software-
  properties/20240301_100314_9e242@/log.gz

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


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

[Desktop-packages] [Bug 2059369] [NEW] gnome Control Center lockup when opening, and navigating to About, need to force quit

2024-03-27 Thread rue

Public bug reported:

When opening the Gnome Control Center first time I was able to navigate
to the About section, then it became unresponsive and I had to force
quit the application. Now every time I open Gnome Control Center it open
at the last section I was at which is About and insistently freezes and
I have to force quit.

Maybe unrelated but when I was in Live mode before installing, opening
Gnome Control Center and navigating to About, I would be prompted for a
new keyring.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-control-center 1:46~beta-1ubuntu1
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: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 15:43:08 2024
InstallationDate: Installed on 2024-03-28 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

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

Title:
  gnome Control Center lockup when opening, and navigating to About,
  need to force quit

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

Bug description:
  When opening the Gnome Control Center first time I was able to
  navigate to the About section, then it became unresponsive and I had
  to force quit the application. Now every time I open Gnome Control
  Center it open at the last section I was at which is About and
  insistently freezes and I have to force quit.

  Maybe unrelated but when I was in Live mode before installing, opening
  Gnome Control Center and navigating to About, I would be prompted for
  a new keyring.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46~beta-1ubuntu1
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 15:43:08 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2059341] Re: Xorg freeze

2024-03-27 Thread Daniel van Vugt

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

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

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

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

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

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

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

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  I have a server running ubuntu 22.04.4 LTS and the system boots fine and all 
the hardware is detected, but the HDMI output is freezing on the line: "r8169 
000:03:00.0 emp3s0: renamed from eth0". I have managed to get past this 
previously by adding "nomodeset" to the GRUB boot options but I need the 
graphics driver for hardware transcoding as that's its main use so need to try 
and think of another way around this issue. I can ssh into the server fine, it 
seems to be working fine otherwise. I've seen that it might be when the igpu 
takes over. Here is my hardware:
  CPU: i5-13500T, RAM: 64GB DDR4, MOBO: ASRock B760M-ITX, HDDs: 1TB m.2 gen3, 
12TB HDD, 8TB HDD, PSU: Corsair SF750.!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143
  Uname: Linux 5.15.0-101-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Wed Mar 27 22:51:48 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation AlderLake-S GT1 [1849:4680]
  InstallationDate: Installed on 2024-03-22 (5 days ago)
  InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release 
amd64 (20240216.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0033 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 2M/x2
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 14: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 14: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: ASRock B760M-ITX/D4 WiFi
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic 
root=UUID=1fdded36-c076-4a14-a7b9-ef9a6fe5a11f ro i915.alpha_support=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 3.05
  dmi.board.name: B760M-ITX/D4 WiFi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.05:bd06/09/2023:br5.27:svnASRock:pnB760M-ITX/D4WiFi:pvrToBeFilledByO.E.M.:rvnASRock:rnB760M-ITX/D4WiFi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: B760M-ITX/D4 WiFi
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: ASRock
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati:

[Desktop-packages] [Bug 1750146]

2024-03-27 Thread alexis.salin

I am also affected by this bug, can you fix it? Thank you.

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

Title:
  Xbox (One) Wireless Controller won't connect

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

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1750146]

2024-03-27 Thread alexis.salin

Hello, can you add drivers for the Xbox controller? It's one of the most
used controllers on PC and it's annoying because xpadneo disables secure
boot.

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

Title:
  Xbox (One) Wireless Controller won't connect

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

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1

2024-03-27 Thread Steve Langasek

c2esp autopkgtest still fails with the current cups in noble-proposed -
though it appears to fail differently now.

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

Title:
  proposed-migration for cups 2.4.7-1.2ubuntu1

Status in c2esp package in Ubuntu:
  New
Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  multiple cups-related packages are having test failures on armhf after time_t 
transition.
  https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf
  https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9

  I am suspecting a common cups-based issue.

  cups-browsed already has a separate bug open at
  https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089.

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


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

[Desktop-packages] [Bug 2059341] [NEW] Xorg freeze

2024-03-27 Thread George Hollis

Public bug reported:

I have a server running ubuntu 22.04.4 LTS and the system boots fine and all 
the hardware is detected, but the HDMI output is freezing on the line: "r8169 
000:03:00.0 emp3s0: renamed from eth0". I have managed to get past this 
previously by adding "nomodeset" to the GRUB boot options but I need the 
graphics driver for hardware transcoding as that's its main use so need to try 
and think of another way around this issue. I can ssh into the server fine, it 
seems to be working fine otherwise. I've seen that it might be when the igpu 
takes over. Here is my hardware:
CPU: i5-13500T, RAM: 64GB DDR4, MOBO: ASRock B760M-ITX, HDDs: 1TB m.2 gen3, 
12TB HDD, 8TB HDD, PSU: Corsair SF750.!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143
Uname: Linux 5.15.0-101-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Mar 27 22:51:48 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA 
controller])
   Subsystem: ASRock Incorporation AlderLake-S GT1 [1849:4680]
InstallationDate: Installed on 2024-03-22 (5 days ago)
InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0033 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 2M/x2
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 14: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
 |__ Port 14: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: ASRock B760M-ITX/D4 WiFi
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic 
root=UUID=1fdded36-c076-4a14-a7b9-ef9a6fe5a11f ro i915.alpha_support=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 3.05
dmi.board.name: B760M-ITX/D4 WiFi
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.05:bd06/09/2023:br5.27:svnASRock:pnB760M-ITX/D4WiFi:pvrToBeFilledByO.E.M.:rvnASRock:rnB760M-ITX/D4WiFi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: B760M-ITX/D4 WiFi
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: ASRock
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
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

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


** Tags: amd64 apport-bug freeze jammy ubuntu uec-images

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a server running ubuntu 22.04.4 LTS and the system boots fine and all 
the hardware is detected, but the HDMI output is freezing on the line: "r8169 
000:03:00.0 emp3s0: renamed from eth0". I have managed to get past this 
previously by adding "nomodeset" to the GRUB boot options but I need the 
graphics driver for hardware transcoding as that's its main use so need to try 
and think of another way around this issue. I can ssh into the server fine, it 
seems to be working fine otherwise. I've seen that it might be when the igpu 
takes over. Here is my hardware:
  CPU: i5-13500T, RAM: 64GB DDR4, MOBO: ASRock B760M-ITX, HDDs: 1TB m.2 gen3, 
12TB HDD, 8TB HDD, PSU: Corsair SF750.!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04

[Desktop-packages] [Bug 2059335] Re: Update file-roller to 44

2024-03-27 Thread Jeremy Bícha

** Description changed:

  https://gitlab.gnome.org/GNOME/file-roller/-/blob/44/NEWS
+ 
+ file-roller 44 was released after Ubuntu 24.04 LTS Feature Freeze.
+ 
+ Sometimes, we request Feature Freeze Exceptions to get late features in,
+ but this change looks like it could be a problem for Ubuntu Budgie,
+ Ubuntu Unity, and Ubuntu Cinnamon which include file-roller by default:
+ 
+ - Retire AppMenu and remove redundant codes
+ 
+ file-roller 44 will be in Ubuntu 24.10.

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Update file-roller to 44

Status in file-roller package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/file-roller/-/blob/44/NEWS

  file-roller 44 was released after Ubuntu 24.04 LTS Feature Freeze.

  Sometimes, we request Feature Freeze Exceptions to get late features
  in, but this change looks like it could be a problem for Ubuntu
  Budgie, Ubuntu Unity, and Ubuntu Cinnamon which include file-roller by
  default:

  - Retire AppMenu and remove redundant codes

  file-roller 44 will be in Ubuntu 24.10.

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


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

[Desktop-packages] [Bug 2059335] [NEW] Update file-roller to 44

2024-03-27 Thread Jeremy Bícha

Public bug reported:

https://gitlab.gnome.org/GNOME/file-roller/-/blob/44/NEWS

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: upgrade-software-version

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

Title:
  Update file-roller to 44

Status in file-roller package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/file-roller/-/blob/44/NEWS

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


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

[Desktop-packages] [Bug 1750146] Re: Xbox (One) Wireless Controller won't connect

2024-03-27 Thread Alexis Salin

Hello, can you add drivers for the Xbox controller? It's one of the most
used controllers on PC and it's annoying because xpadneo disables secure
boot.

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

Title:
  Xbox (One) Wireless Controller won't connect

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

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1869655] Re: Boot animations start too late to be useful

This bug was fixed in the package initramfs-tools - 0.142ubuntu23

---
initramfs-tools (0.142ubuntu23) noble; urgency=medium

  [ Daniel van Vugt ]
  * hooks/framebuffer: Only add simple/tiny framebuffer drivers. This is to
limit the size of initrd when FRAMEBUFFER=y is soon enabled for desktop
installations (LP: #1970069, #1869655).

  [ Benjamin Drung ]
  * autopkgtest: Increase QEMU timeouts on arm64/armhf
  * hooks/framebuffer:
- Move adding framebuffer drivers into auto_add_modules
- Drop looking in $MODULESDIR/initrd/ for kernel modules
- Support MODULES=dep in framebuffer hook

initramfs-tools (0.142ubuntu22) noble; urgency=medium

  * autopkgtest: update systemd-udevd path from /lib to /usr/lib

initramfs-tools (0.142ubuntu21) noble; urgency=medium

  [ Benjamin Drung ]
  * configure_networking:
- Increase minimum timeout to 30 seconds
- Fix configuring BOOTIF when using iSCSI (LP: #2056187)
- Set interface MTU if provided by the DHCP server (LP: #2056194)
- log sleep durations before retries
  * Copy /etc/passwd into the initramfs to allow dhcpcd running as dhcpcd user
  * Replace obsolete pkg-config build-dependency by pkgconf

  [ Dan Bungert ]
  * Restore nvdimm and dax pmem-related modules (LP: #1981385)

 -- Benjamin Drung   Thu, 21 Mar 2024 10:57:54 +0100

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Committed => 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/1869655

Title:
  Boot animations start too late to be useful

Status in Plymouth:
  New
Status in grub2 package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  In Progress

Bug description:
  Boot animations start too late to be useful

  Modern systems spend all their boot time (a couple of seconds)
  decompressing the kernel. During that time the user only sees the
  static BIOS logo (ACPI BGRT). Then when Plymouth can finally start
  animating, the startup process is already finished and there's
  virtually no time left to show any useful animations.

  This could be fixed in:

    grub: By adding a splash under the BIOS logo to show some progress
  _before_ a Linux kernel is even started

  and/or

    plymouth: By preferencing legacy framebuffer devices (like EFI) over
  DRM, if we find those are available a few seconds sooner. That would
  also fix bug 1868240 completely, and bug 1836858 mostly as the flicker
  moves to when the login screen starts.

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


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

[Desktop-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

This bug was fixed in the package initramfs-tools - 0.142ubuntu23

---
initramfs-tools (0.142ubuntu23) noble; urgency=medium

  [ Daniel van Vugt ]
  * hooks/framebuffer: Only add simple/tiny framebuffer drivers. This is to
limit the size of initrd when FRAMEBUFFER=y is soon enabled for desktop
installations (LP: #1970069, #1869655).

  [ Benjamin Drung ]
  * autopkgtest: Increase QEMU timeouts on arm64/armhf
  * hooks/framebuffer:
- Move adding framebuffer drivers into auto_add_modules
- Drop looking in $MODULESDIR/initrd/ for kernel modules
- Support MODULES=dep in framebuffer hook

initramfs-tools (0.142ubuntu22) noble; urgency=medium

  * autopkgtest: update systemd-udevd path from /lib to /usr/lib

initramfs-tools (0.142ubuntu21) noble; urgency=medium

  [ Benjamin Drung ]
  * configure_networking:
- Increase minimum timeout to 30 seconds
- Fix configuring BOOTIF when using iSCSI (LP: #2056187)
- Set interface MTU if provided by the DHCP server (LP: #2056194)
- log sleep durations before retries
  * Copy /etc/passwd into the initramfs to allow dhcpcd running as dhcpcd user
  * Replace obsolete pkg-config build-dependency by pkgconf

  [ Dan Bungert ]
  * Restore nvdimm and dax pmem-related modules (LP: #1981385)

 -- Benjamin Drung   Thu, 21 Mar 2024 10:57:54 +0100

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Committed => 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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in plymouth package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
    quiet splash loglevel=3 fastboot

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Desktop-packages] [Bug 2059293] [NEW] autopkgtests fail on i386 on the new testsuite

2024-03-27 Thread Simon Chopin

Public bug reported:

The autopkgtests fail on i386 for version 2:1.0.27-1. In the previous
version the test name was "stress" while the failing one is "testsuite",
so presumably this isn't a regression so much as the new testsuite
failing due to i386 being a partial arch.

Relevant parts of the logs:

506s config.status: creating tests/Makefile
506s config.status: executing depfiles commands
506s   CC   stress.o
507s   CC   testlib.o
507s   CCLD stress
507s /usr/bin/ld: cannot find -lusb-1.0: No such file or directory
507s collect2: error: ld returned 1 exit status

** Affects: libusb-1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  autopkgtests fail on i386 on the new testsuite

Status in libusb-1.0 package in Ubuntu:
  New

Bug description:
  The autopkgtests fail on i386 for version 2:1.0.27-1. In the previous
  version the test name was "stress" while the failing one is
  "testsuite", so presumably this isn't a regression so much as the new
  testsuite failing due to i386 being a partial arch.

  Relevant parts of the logs:

  506s config.status: creating tests/Makefile
  506s config.status: executing depfiles commands
  506s   CC   stress.o
  507s   CC   testlib.o
  507s   CCLD stress
  507s /usr/bin/ld: cannot find -lusb-1.0: No such file or directory
  507s collect2: error: ld returned 1 exit status

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


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

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

2024-03-27 Thread Bryce Harrington

** Changed in: spice-vdagent (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: virt-manager (Ubuntu Jammy)
   Status: New => In Progress

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

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  New
Status in libslirp source package in Focal:
  New
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  New
Status in spice source package in Focal:
  New
Status in spice-protocol source package in Focal:
  New
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  In Progress
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  New
Status in openvswitch source package in Jammy:
  New
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  Fix Committed
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  New
Status in spice-vdagent source package in Jammy:
  Fix Committed
Status in virglrenderer source package in Jammy:
  New
Status in virt-manager source package in Jammy:
  In Progress

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

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


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

[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed

2024-03-27 Thread corrado venturini

Thank a lot, I laboriously convinced a friend to use Ubuntu and it was
difficult for me to explain that Released was not 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/2047256

Title:
  Ubuntu 24.04 Some image thumbnails no longer displayed

Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  After recent updates on my Ubuntu Noble 24.04 nautilus does not show 
thumbnails of PDF and other image files.
  On a different partition same PC Ubuntu Noble 24.04 not recently updated 
image thumbnails are correctly displayed

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 16:15:59 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)'
  InstallationDate: Installed on 2023-12-10 (12 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210)
  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.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

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


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

[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed

I've changed it to fix commited now

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

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

Title:
  Ubuntu 24.04 Some image thumbnails no longer displayed

Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  After recent updates on my Ubuntu Noble 24.04 nautilus does not show 
thumbnails of PDF and other image files.
  On a different partition same PC Ubuntu Noble 24.04 not recently updated 
image thumbnails are correctly displayed

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 16:15:59 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)'
  InstallationDate: Installed on 2023-12-10 (12 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210)
  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.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

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


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

[Desktop-packages] [Bug 2058769] Re: proposed-migration for click 0.5.2-2

2024-03-27 Thread Steve Langasek

** Description changed:

- click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on ppc64el,
- s390x.
+ click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on all archs
+ except amd64.
  
  In order to be able to run the tests without all-proposed=1, glib 2.0 is
  needed, which is why I marked it as affected.
  
  Excerpt of the test logs:
  
  ERROR: test_list_simple 
(click_package.tests.integration.test_list.TestList.test_list_simple)
  --
  Traceback (most recent call last):
-   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
- self.click_install(path_to_click, name, user)
-   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py",
 line 99, in click_install
- subprocess.check_call(cmd)
-   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
- raise CalledProcessError(retcode, cmd)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
+ self.click_install(path_to_click, name, user)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py",
 line 99, in click_install
+ subprocess.check_call(cmd)
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '--allow-unauthenticated', 
'/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit 
status 1.
  
  ==
  ERROR: test_debsig_install_valid_signature 
(click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature)
  --
  Traceback (most recent call last):
-   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 207, in test_debsig_install_valid_signature
- subprocess.check_call(
-   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
- raise CalledProcessError(retcode, cmd)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 207, in test_debsig_install_valid_signature
+ subprocess.check_call(
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' 
returned non-zero exit status 1.
  
  ==
  ERROR: test_debsig_install_can_install_with_sig_override 
(click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override)
  --
  Traceback (most recent call last):
-   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 164, in test_debsig_install_can_install_with_sig_override
- subprocess.check_call(
-   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
- raise CalledProcessError(retcode, cmd)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 164, in test_debsig_install_can_install_with_sig_override
+ subprocess.check_call(
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--allow-unauthenticated', '--user=root', 
'/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero 
exit status 1.

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

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

Title:
  proposed-migration for click 0.5.2-2

Status in click package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on all
  archs except amd64.

  In order to be able to run the tests without all-proposed=1, glib 2.0
  is needed, which is why I marked it as affected.

  Excerpt of the test logs:

  ERROR: test_list_simple 
(click_package.tests.integration.test_list.TestList.test_list_simple)
  --
  Traceback (most recent call last):
    File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple

[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed

2024-03-27 Thread corrado venturini

Usually 'Fix Released' means RELEASED, when the fix is blocked in
proposed the status is 'Fix Committed' so 'Fix Released' is confusing.

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

Title:
  Ubuntu 24.04 Some image thumbnails no longer displayed

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  After recent updates on my Ubuntu Noble 24.04 nautilus does not show 
thumbnails of PDF and other image files.
  On a different partition same PC Ubuntu Noble 24.04 not recently updated 
image thumbnails are correctly displayed

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 16:15:59 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)'
  InstallationDate: Installed on 2023-12-10 (12 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210)
  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.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

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


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

[Desktop-packages] [Bug 2059281] [NEW] libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

2024-03-27 Thread Heinrich Schuchardt

Public bug reported:

libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

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


** Tags: time-t

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

Title:
  libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
  c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

Status in libcupsfilters package in Ubuntu:
  New

Bug description:
  libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
  c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

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


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

[Desktop-packages] [Bug 2059280] [NEW] libdbusmenu 18.10.20180917~bzr492+repack1-3.1ubuntu3 causes autopkgtest for ibus/1.5.29-1

2024-03-27 Thread Heinrich Schuchardt

Public bug reported:

libdbusmenu 18.10.20180917~bzr492+repack1-3.1ubuntu3 causes autopkgtest
failures for ibus/1.5.29-1

https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
noble/noble/amd64/i/ibus/20240322_073936_38284@/log.gz

https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
noble/noble/ppc64el/i/ibus/20240320_182640_df3bb@/log.gz

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

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

Title:
  libdbusmenu 18.10.20180917~bzr492+repack1-3.1ubuntu3 causes
  autopkgtest for ibus/1.5.29-1

Status in libdbusmenu package in Ubuntu:
  New

Bug description:
  libdbusmenu 18.10.20180917~bzr492+repack1-3.1ubuntu3 causes
  autopkgtest failures for ibus/1.5.29-1

  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/i/ibus/20240322_073936_38284@/log.gz

  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/ppc64el/i/ibus/20240320_182640_df3bb@/log.gz

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


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

[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed

there is need to keep adding new comments, that bug has a fix available
which is blocked in proposed, it doesn't need new information or
confirmation that it is broken while the fixed version didn't land in
the release pocket

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

Title:
  Ubuntu 24.04 Some image thumbnails no longer displayed

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  After recent updates on my Ubuntu Noble 24.04 nautilus does not show 
thumbnails of PDF and other image files.
  On a different partition same PC Ubuntu Noble 24.04 not recently updated 
image thumbnails are correctly displayed

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 16:15:59 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)'
  InstallationDate: Installed on 2023-12-10 (12 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210)
  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.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

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


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

[Desktop-packages] [Bug 2059267] [NEW] Ubuntu patch reverting another Ubuntu patch

Public bug reported:

Downstream Update-style-to-the-same-than-flutter-installer.patch[1] is
reverting a great deal of gis-apps-page.{c,ui} that are introduced by
(also downstream controlled) 0001-Add-Ubuntu-mode-with-special-
pages.patch[2].

I think that makes maintaining those patches more complex than necessary
and suggest to merge them together.

[1] 
https://git.launchpad.net/ubuntu/+source/gnome-initial-setup/tree/debian/patches/Update-style-to-the-same-than-flutter-installer.patch
[2] 
https://git.launchpad.net/ubuntu/+source/gnome-initial-setup/tree/debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch#n399

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

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

Title:
  Ubuntu patch reverting another Ubuntu patch

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

Bug description:
  Downstream Update-style-to-the-same-than-flutter-installer.patch[1] is
  reverting a great deal of gis-apps-page.{c,ui} that are introduced by
  (also downstream controlled) 0001-Add-Ubuntu-mode-with-special-
  pages.patch[2].

  I think that makes maintaining those patches more complex than
  necessary and suggest to merge them together.

  [1] 
https://git.launchpad.net/ubuntu/+source/gnome-initial-setup/tree/debian/patches/Update-style-to-the-same-than-flutter-installer.patch
  [2] 
https://git.launchpad.net/ubuntu/+source/gnome-initial-setup/tree/debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch#n399

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


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

[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed

2024-03-27 Thread corrado venturini

Still same problem on a fresh install from Ubuntu 24.04 LTS "Noble Numbat" - 
Daily amd64 (20240324)
corrado@corrado-n5-nn-0324:~$ apt list nautilus
Listing... Done
nautilus/noble,now 1:46~beta-0ubuntu3 amd64 [installed,automatic]

problem does not disappear deleting .cache/thumbnails/fail

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

Title:
  Ubuntu 24.04 Some image thumbnails no longer displayed

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  After recent updates on my Ubuntu Noble 24.04 nautilus does not show 
thumbnails of PDF and other image files.
  On a different partition same PC Ubuntu Noble 24.04 not recently updated 
image thumbnails are correctly displayed

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 16:15:59 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)'
  InstallationDate: Installed on 2023-12-10 (12 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210)
  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.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

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


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

[Desktop-packages] [Bug 2049672] Re: Should welcome screen be included?

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

** Changed in: gnome-initial-setup (Ubuntu)
   Status: New => Fix Released

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

Title:
  Should welcome screen be included?

Status in gnome-initial-setup package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 24.04 LTS with gnome-initial-setup 46 Alpha shows these
  screens:

  Help improve Ubuntu
  Privacy (Location Services)
  Done (You can use App Center to install apps)

  This is a change from Ubuntu 23.10 where the first screen was Online
  Accounts. See LP: #2049513

  Would it be useful to add an intro screen instead of immediately
  asking for permission to send data?

  GNOME Initial Setup has a page available. We may want to adjust the
  wording though since there is no "making an account" for existing
  users especially now that Online Accounts is no longer integrated
  here. Screenshot attached.

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


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

[Desktop-packages] [Bug 2059166] Re: Nautilus doesn't show hidden files under computer/>>>

Thank you for your bug report. Going through 'otherlocations' or
directly doing ctrl-L /etc shouldn't make a difference. It works fine
here, are you using listview or the iconview? Did you scroll at the end
of the list to check if they are there (the sorting can be counter-
intuitive but here they are listed at the end and not at what would be
their alphabetic order without the leading dot)

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Nautilus doesn't show hidden files under computer/>>>

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  In Nautilus, when I go to the file list under
  "otherlocations/computer", the hidden files will not display.  I have
  tried checking the "show hidden files", and the keyboard shortcut
  cntl+H , but they don't uncover the hidden file.  In the terminal if I
  go to say '/etc' and do "ls -a", all the hidden and not hidden files
  will show, but the hidden files do not have a period in front of them.

  I did submit ubuntu-bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: User Name 5.15.0-101.111-generic 5.15.143
  Uname: Linux 5.15.0-101-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 18:07:37 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper 
file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2023-09-14 (194 days ago)
  InstallationMedia: Ubuntu 20.04.4 gb3b LTS amd64 "Ip3 Focal Fossa" (20220425)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: Upgraded to jammy on 2024-03-25 (1 days ago)

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


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

[Desktop-packages] [Bug 2058769] Re: proposed-migration for click 0.5.2-2

2024-03-27 Thread Simon Chopin

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

** Description changed:

- click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on armhf,
- and possibly on all archs.
+ click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on ppc64el,
+ s390x.
  
- armhf binary will be removed from the release pocket.
+ In order to be able to run the tests without all-proposed=1, glib 2.0 is
+ needed, which is why I marked it as affected.
+ 
+ Excerpt of the test logs:
+ 
+ ERROR: test_list_simple 
(click_package.tests.integration.test_list.TestList.test_list_simple)
+ --
+ Traceback (most recent call last):
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
+ self.click_install(path_to_click, name, user)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py",
 line 99, in click_install
+ subprocess.check_call(cmd)
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
+ subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '--allow-unauthenticated', 
'/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit 
status 1.
+ 
+ ==
+ ERROR: test_debsig_install_valid_signature 
(click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature)
+ --
+ Traceback (most recent call last):
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 207, in test_debsig_install_valid_signature
+ subprocess.check_call(
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
+ subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' 
returned non-zero exit status 1.
+ 
+ ==
+ ERROR: test_debsig_install_can_install_with_sig_override 
(click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override)
+ --
+ Traceback (most recent call last):
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 164, in test_debsig_install_can_install_with_sig_override
+ subprocess.check_call(
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
+ subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--allow-unauthenticated', '--user=root', 
'/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero 
exit status 1.

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

Title:
  proposed-migration for click 0.5.2-2

Status in click package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on
  ppc64el, s390x.

  In order to be able to run the tests without all-proposed=1, glib 2.0
  is needed, which is why I marked it as affected.

  Excerpt of the test logs:

  ERROR: test_list_simple 
(click_package.tests.integration.test_list.TestList.test_list_simple)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
  self.click_install(path_to_click, name, user)
File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py",
 line 99, in click_install
  subprocess.check_call(cmd)
File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '--allow-unauthenticated', 
'/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit 
status 1.

  ==
  ERROR: test_debsig_install_valid_signature 
(click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 207, in

[Desktop-packages] [Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound

2024-03-27 Thread Hui Wang

About the issue of Redmi buds 4 active, what version of ubuntu are you
using? If it is 22.04, you need to collect pulseaudio log.

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

Title:
  [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since the last three weeks' updates, I have encountered several
  challenges with the audio functionality on my system. Primarily, upon
  starting my laptop, the audio often fails to work, displaying "Dummy
  Output." To resolve this, I find myself needing to restart the laptop
  two or three times before the audio becomes functional.

  Even when the audio is working, I've noticed a recurring issue where,
  after playing video or audio for approximately 2-3 minutes, the sound
  starts crackling and buzzing. The intensity of these distortions
  gradually increases, resembling the static interference on a radio
  station with a weak signal. This issue persists even when using 3.5mm
  headphones, requiring the use of a USB headset or Bluetooth headphones
  to enjoy distortion-free audio.

  Furthermore, I have observed that, regardless of the Ubuntu version
  (ranging from 22.04 to 22.04.3), I face difficulties changing the
  microphone output settings when an external audio peripheral, such as
  a USB headset, 3.5mm headphones, or Bluetooth headphones, is
  connected. The OS appears to exclusively utilize the microphone from
  the connected peripheral, making it impossible to switch to the
  laptop's built-in microphone.

  For your reference, here are the specifications of my laptop and the
  Ubuntu version I am currently using:

  Laptop: Dell Vostro 3400
  CPU: 11th Gen Intel i5-1135G7
  GPU: Intel TigerLake-LP GT2 Iris Xe
  Memory: 2490MiB / 19720MiB
  Resolution: 1920x1080
  OS: Ubuntu 22.04.3 LTS x86_64
  Kernel: 6.5.0-14-generic
  DE: GNOME 42.9
  Shell: bash 5.1.16
  Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42

  **UPDATE 12/02/2024 Noticed that every time my laptop fan starts spinning the 
crackling sound appears, after fan stops the crackling sound disappear.
  **UPDATE 19/03/2024 I did a software update to the linux kernel 6.5.0-26, now 
i get a dummy output in sound even if i restart the system many times, and if i 
use my Bluetooth headphone i can't use the mic, neither the mic of the laptop 
or of the headphone (there is no option is the settings to choose from) it's 
all blank.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galxy-a10   1437 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 17:50:44 2024
  InstallationDate: Installed on 2024-01-16 (13 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR 
whoopsie-upload-all[712]: INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash 
already marked for upload, skipping
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.27.1
  dmi.board.name: 0GGCMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3400
  dmi.product.sku: 0A23
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855

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


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

[Desktop-packages] [Bug 2059247] [NEW] Cheese does not list all webcams

2024-03-27 Thread srnissen

Public bug reported:

## Summary:

Cheese finds different webcams when run as "cheese" and "sudo cheese"

## Expected:

When running cheese without sudo, preferences->webcam lists all my
cameras, once each.

## Actual:

When running cheese without sudo, only the external camera is found, and
it is listed twice.

When running cheese with sudo, all cameras are found - and also listed
twice.

## Details:

Running normally, under preferences->webcam, cheese lists:

- CameraA (V4L2)
- CameraA (V4L2)

(Yes it lists the same camera twice.)

Running cheese with sudo, the same dropdown contains:

- Integrated Camera: Integrated C
- Integrated Camera: Integrated I
- CameraA
- Integrated Camera: Integrated C
- Integrated Camera: Integrated I
- CameraA

Again, it lists every camera twice (And for some reason strips "(V4L2)"
from the name of the external camera)

## Machine information

lsb_release -rd: Pop!_OS 22.04 LTS

Cheese version: 41.1-1build1 500

Running lshw with/wihtout sudo also results in two different lists -
without sudo, only CameraA is found. With sudo, the integrated camera
appears.

(Unfortunately, ubuntu-bug is weird on pop!_os or I'd report through
there)

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

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

Title:
  Cheese does not list all webcams

Status in cheese package in Ubuntu:
  New

Bug description:
  ## Summary:

  Cheese finds different webcams when run as "cheese" and "sudo cheese"

  ## Expected:

  When running cheese without sudo, preferences->webcam lists all my
  cameras, once each.

  ## Actual:

  When running cheese without sudo, only the external camera is found,
  and it is listed twice.

  When running cheese with sudo, all cameras are found - and also listed
  twice.

  ## Details:

  Running normally, under preferences->webcam, cheese lists:

  - CameraA (V4L2)
  - CameraA (V4L2)

  (Yes it lists the same camera twice.)

  Running cheese with sudo, the same dropdown contains:

  - Integrated Camera: Integrated C
  - Integrated Camera: Integrated I
  - CameraA
  - Integrated Camera: Integrated C
  - Integrated Camera: Integrated I
  - CameraA

  Again, it lists every camera twice (And for some reason strips
  "(V4L2)" from the name of the external camera)

  ## Machine information

  lsb_release -rd: Pop!_OS 22.04 LTS

  Cheese version: 41.1-1build1 500

  Running lshw with/wihtout sudo also results in two different lists -
  without sudo, only CameraA is found. With sudo, the integrated camera
  appears.

  (Unfortunately, ubuntu-bug is weird on pop!_os or I'd report through
  there)

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


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

[Desktop-packages] [Bug 1798967] Re: bubblewrap has wrong description after setuid bit was removed

2024-03-27 Thread Simon McVittie

This was fixed in 0.4.1-3 (2021).

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

Title:
  bubblewrap has wrong description after setuid bit was removed

Status in bubblewrap package in Ubuntu:
  Confirmed

Bug description:
  After setuid bit was removed from default installation in cosmic (and
  soon in bionic) the description doesn't match actual behavior anymore:

  "setuid wrapper for unprivileged chroot and namespace manipulation"

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


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

2024-03-27 Thread Bin Li

** Changed in: libmbim (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: libmbim (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Won't Fix
Status in libmbim package in Ubuntu:
  Invalid
Status in libmbim source package in Jammy:
  Invalid
Status in libmbim source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Fibocom WWAN cards (Intel XMM
  7560), and Lenovo are struggling to give a decent way to run the FCC
  unlock service without this.

  Until the device is unlocked, the end users are not able to use the
  SIM cards, and some of the affected devices have already been shipped.
  The end users now have to go to the Lenovo support website and
  download a few scripts and binaries to unlock the device to make their
  SIM cards work.

  The Lenovo wants this patch to be included in jammy, then they can
  provide the FCC unlock service and manage it in OEM-archive, so the
  end users can use SIM cards as soon as they receive the laptop.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
    - when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

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


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

[Desktop-packages] [Bug 2059177] Re: dev package doesn't include *Config.cmake files

2024-03-27 Thread Hans Joachim Desserud

** Tags added: noble packaging

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

Title:
  dev package doesn't include *Config.cmake files

Status in libogg package in Ubuntu:
  New

Bug description:
  For several years now, Ogg has supported auto-generated and exported
  CMake configuration, especially when building Ogg with CMake. Properly
  installed, this allows someone to merely use `find_package(Ogg)` in
  their CMake project without having to jump through hoops. An example
  where this is done well in Ubuntu is qtbase5-dev.

  $ dpkg -L qtbase5-dev |grep Config.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Concurrent/Qt5ConcurrentConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5DBus/Qt5DBusConfig.cmake
  
/usr/lib/x86_64-linux-gnu/cmake/Qt5EglFsKmsSupport/Qt5EglFsKmsSupportConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Network/Qt5NetworkConfig.cmake
  
/usr/lib/x86_64-linux-gnu/cmake/Qt5OpenGLExtensions/Qt5OpenGLExtensionsConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport/Qt5PrintSupportConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Sql/Qt5SqlConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Test/Qt5TestConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Xml/Qt5XmlConfig.cmake

  An example where this is done well for Ogg is Homebrew @
  https://github.com/Homebrew/homebrew-
  core/blob/175a655dbe76d08350ff941f9c9d7fd9ef2933d0/Formula/lib/libogg.rb

  Please include the `*Config.cmake` files (and friends) in the Ogg
  family of packages.

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


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

[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

2024-03-27 Thread Bin Li

** Tags added: originate-from-2047204 sutton

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Mantic:
  Fix Released
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Desktop-packages] [Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile

This bug was fixed in the package pulseaudio -
1:15.99.1+dfsg1-1ubuntu2.2

---
pulseaudio (1:15.99.1+dfsg1-1ubuntu2.2) jammy; urgency=medium

  [ Hui Wang ]
  * d/p/0001-backend-native-Handle-multi-AT-commands-in-a-buffer.patch
- Lenovo Thinkplus XT99 bluetooth headset supports mSBC and could
  issue multi AT commands when negotiating with pulseaudio, but
  pulseaudio couldn't handle multi AT commands when processing one
  buffer, this makes the HFP/HSP mode not work, cherry pick an
  upstream commit to fix this issue. (LP: #2051895)

 -- Hui Wang   Mon, 19 Feb 2024 11:08:35 +0800

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

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Released
Status in pulseaudio source package in Mantic:
  Fix Released
Status in pulseaudio source package in Noble:
  Fix Committed

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.

  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then 
upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my 
change only affects bluetooth audio devices, it will not bring any impact to 
non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices 
and 2 non-audio devices:

  BT audio devices (pairing, connection, re-connection, playback and capture 
all worked well):
  PLT_BBTGO2 (headset)
  Xiaomi Air3 SE (headset)
  Crusher Wireless (headset)
  SOAIY S18 (sound box)
  HK Soho Wireless (headset)
  Thinkplus XT99 (headset)
  Wl-1000X (headset)

  BT non-audio devices (pairing, connection, re-connection, key input all 
worked well):
  BT3.0 Keyboard
  The Pinao 2 keyboard

  
  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions


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

[Desktop-packages] [Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile

This bug was fixed in the package pulseaudio - 1:16.1+dfsg1-2ubuntu4.1

---
pulseaudio (1:16.1+dfsg1-2ubuntu4.1) mantic; urgency=medium

  [ Hui Wang ]
  * d/p/0001-backend-native-Handle-multi-AT-commands-in-a-buffer.patch
- Lenovo Thinkplus XT99 bluetooth headset supports mSBC and could
  issue multi AT commands when negotiating with pulseaudio, but
  pulseaudio couldn't handle multi AT commands when processing one
  buffer, this makes the HFP/HSP mode not work, cherry pick an
  upstream commit to fix this issue. (LP: #2051895)

 -- Hui Wang   Mon, 19 Feb 2024 11:19:58 +0800

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

** Changed in: pulseaudio (Ubuntu Jammy)
   Status: Fix Committed => 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/2051895

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Released
Status in pulseaudio source package in Mantic:
  Fix Released
Status in pulseaudio source package in Noble:
  Fix Committed

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.

  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then 
upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my 
change only affects bluetooth audio devices, it will not bring any impact to 
non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices 
and 2 non-audio devices:

  BT audio devices (pairing, connection, re-connection, playback and capture 
all worked well):
  PLT_BBTGO2 (headset)
  Xiaomi Air3 SE (headset)
  Crusher Wireless (headset)
  SOAIY S18 (sound box)
  HK Soho Wireless (headset)
  Thinkplus XT99 (headset)
  Wl-1000X (headset)

  BT non-audio devices (pairing, connection, re-connection, key input all 
worked well):
  BT3.0 Keyboard
  The Pinao 2 keyboard

  
  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions


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

[Desktop-packages] [Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile

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

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

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

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Released
Status in pulseaudio source package in Mantic:
  Fix Released
Status in pulseaudio source package in Noble:
  Fix Committed

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.

  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then 
upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my 
change only affects bluetooth audio devices, it will not bring any impact to 
non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices 
and 2 non-audio devices:

  BT audio devices (pairing, connection, re-connection, playback and capture 
all worked well):
  PLT_BBTGO2 (headset)
  Xiaomi Air3 SE (headset)
  Crusher Wireless (headset)
  SOAIY S18 (sound box)
  HK Soho Wireless (headset)
  Thinkplus XT99 (headset)
  Wl-1000X (headset)

  BT non-audio devices (pairing, connection, re-connection, key input all 
worked well):
  BT3.0 Keyboard
  The Pinao 2 keyboard

  
  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions


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

[Desktop-packages] [Bug 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main

Actually please hold that for a moment, I had forgotten to enable other
architectures in the PPA and a test is failing in Armhf.

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

Title:
  FFe: [MIR] freedp2 -> freerdp3 in main

Status in freerdp3 package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop package in Ubuntu:
  Fix Committed
Status in remmina package in Ubuntu:
  Fix Committed

Bug description:
  Feature Freeze Exception Request
  --
  There are only 2 packages in Ubuntu main that use freerdp2: remmina and 
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore 
only one version of freerdp will be in main. freerdp2 will be demoted to 
universe since many universe packages use it and are not prepared to switch to 
freerdp3.

  This also requests updating gnome-control-center to fully enable the
  features of gnome-remote-desktop 46.

  Impact
  --
  A headline feature of GNOME 46 is support as a Remote Desktop server without 
requiring someone to already be logged in locally ("headless" mode). This 
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires 
freerdp3.

  Impact if this does not happen
  --
  - We would need to patch gnome-control-center to use the older Remote Desktop 
panel (or at least hide the new tab for Remote Login)
  - We would need to keep using gnome-remote-desktop 45 instead of 46. The 
gnome-remote-desktop upstream maintainers would be unhappy with this decision. 
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may 
require changes in gnome-remote-desktop for things to work well although a 
simple test showed that basic remote desktop seems to work ok with the 
mismatch. (See comment #1 from upstream developer.)

  Why this did not land sooner
  ---
  It required the packaging of a new source package freerdp3. And we had to do 
this sooner than Debian. Sorry too many things to do before Feature Freeze and 
this did not make it.

  Affected Packages
  -
  - gnome-remote-desktop 45 -> 46
  - gnome-control-center (to update the Remote Desktop settings page)
  - remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not 
work  with freerdp 3.3 in my testing
  - gnome-connections (build-dependency swap): Not required by other changes 
and not in Main but makes sense to switch it also

  Affected Flavors
  
  Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center, 
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships 
gnome-control-center but this appears to be a bug since they ship 
cinnamon-control-center and is likely already fixed in noble-proposed)

  Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.

  gnome-connections has no reverse dependencies or recommends.

  Upstream Changes
  
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS

  https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md

  gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature 
Freeze. It will be updated to 46.0. The relevant part here is whether we use 
the 46~beta version of the Remote Desktop page or the 46.0 version.
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS

  Build Logs
  --
  I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA. 
The PPA currently has noble-proposed disabled so that it is easily possible to 
try this set of packages without dealing with the incomplete 32-bit time 
transition in noble-proposed. In addition, the PPA has the affected packages 
from this FFe.

  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages

  Testing Done
  ---
  1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect 
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46 
RC. Remote control worked.

  2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
  freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
  worked.

  3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
  with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
  control worked.

  4. I added a new Remote Login test case to
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
  verified that remote login worked. Notably, enabling this changes the
  port for the older service, now called "Desktop Sharing" to 3390.
  Since 3389 is the default port, users would then need to manually
  specific port 3390 for Desktop Sharing in their remote connection app
  (Remmina, GNOME Connections, etc.).

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


-- 
Mailing list:

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

2024-03-27 Thread Olivier Gayot

** Merge proposal linked:
   
https://code.launchpad.net/~ogayot/ubuntu-seeds/+git/ubuntu-seeds/+merge/463200

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

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

Status in subiquity package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

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

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

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

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

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

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

2024-03-27 Thread Steve Langasek

** Changed in: ubuntu-unity-backgrounds (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in budgie-desktop-environment package in Ubuntu:
  Fix Released
Status in budgie-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-unity-backgrounds package in Ubuntu:
  Triaged
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntucinnamon-environment package in Ubuntu:
  Fix Committed
Status in ubuntucinnamon-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntukylin-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Fix Released
Status in ubuntustudio-look package in Ubuntu:
  Fix Released

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

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


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

[Desktop-packages] [Bug 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main

The following debdiff enables the build tests and runs them as
autopkgtests, which as per [1] run successfully.

[1] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-nteodosio-
rebuilds/noble/amd64/f/freerdp3/20240326_213622_91f66@/log.gz

** Patch added: "freerdp3.diff"

https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2057842/+attachment/5759842/+files/freerdp3.diff

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

Title:
FFe: [MIR] freedp2 -> freerdp3 in main

Status in freerdp3 package in Ubuntu:
Fix Released
Status in gnome-remote-desktop package in Ubuntu:
Fix Committed
Status in remmina package in Ubuntu:
Fix Committed

Bug description:
Feature Freeze Exception Request
--
There are only 2 packages in Ubuntu main that use freerdp2: remmina and
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore
only one version of freerdp will be in main. freerdp2 will be demoted to
universe since many universe packages use it and are not prepared to switch to
freerdp3.

This also requests updating gnome-control-center to fully enable the
features of gnome-remote-desktop 46.

Impact
--
A headline feature of GNOME 46 is support as a Remote Desktop server without
requiring someone to already be logged in locally ("headless" mode). This
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires
freerdp3.

Impact if this does not happen
--
- We would need to patch gnome-control-center to use the older Remote Desktop
panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The
gnome-remote-desktop upstream maintainers would be unhappy with this decision.
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may
require changes in gnome-remote-desktop for things to work well although a
simple test showed that basic remote desktop seems to work ok with the
mismatch. (See comment #1 from upstream developer.)

Why this did not land sooner
---
It required the packaging of a new source package freerdp3. And we had to do
this sooner than Debian. Sorry too many things to do before Feature Freeze and
this did not make it.

Affected Packages
-
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not
work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes
and not in Main but makes sense to switch it also

Affected Flavors

Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center,
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships
gnome-control-center but this appears to be a bug since they ship
cinnamon-control-center and is likely already fixed in noble-proposed)

Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.

gnome-connections has no reverse dependencies or recommends.

Upstream Changes

https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS

https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md

gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature
Freeze. It will be updated to 46.0. The relevant part here is whether we use
the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS

Build Logs
--
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA.
The PPA currently has noble-proposed disabled so that it is easily possible to
try this set of packages without dealing with the incomplete 32-bit time
transition in noble-proposed. In addition, the PPA has the affected packages
from this FFe.

https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages

Testing Done
---
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46
RC. Remote control worked.

2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
worked.

3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
control worked.

4. I added a new Remote Login test case to
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
verified that remote login worked. Notably, enabling this changes the
port for the older service, now called "Desktop Sharing" to 3390.
Since 3389 is the default port, users would then need to manually

[Desktop-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

This bug was fixed in the package fontconfig - 2.15.0-1.1ubuntu1

---
fontconfig (2.15.0-1.1ubuntu1) noble; urgency=medium

  * Merge with Debian unstable. Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- debian/fontconfig-config.install:
  + Install fonts-conf.5.gz
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps-except-emoji.conf
- Add 0001-cache-If-nsec-is-zero-don-t-use-it-for-comparisons.patch
  + If nsec is zero, don't use it for comparisons
- Drop debian/fontconfig-config.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associated po files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- debian/fontconfig-config.maintscript:
  + Entries due to dropped Ubuntu patches and move from /etc to /usr
- debian/rules:
  + Config option to generate the 10-sub-pixel-rgb.conf symlink
- debian/control:
  + Make fontconfig-config break/replace kubuntu-settings-desktop
<< 1:23.04.3 to handle symlink conflict

fontconfig (2.15.0-1.1) unstable; urgency=high

  * Add fix-emoji-no-bitmap-font.patch and update
debian/fontconfig-config.config to allow emoji font when no bitmap fonts
are allowed (which has been Debian's default for many years)
(Closes: #1064267) (LP: #2054924)

 -- Jeremy Bícha   Sun, 10 Mar 2024 19:46:01 -0400

** Changed in: fontconfig (Ubuntu)
   Status: Fix Committed => 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:
  Fix Released
Status in fonts-noto-color-emoji package in Ubuntu:
  Fix Released
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 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed

Opened merge request for Snapd:
https://github.com/snapcore/snapd/pull/13757.

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

Title:
  Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 22.04 LTS Jammy x64


  I hope this is the correct package to assign this request to:

  In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
  decrypt its password store.

  This makes all stored passwords unavailable as soon as the system is
  upgraded from Plasma 5 to Plasma 6.

  Chromium writes the following error messages to the console:

  -
  [5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call 
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: 
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.113" (uid=1000 pid=5362 
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom" 
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet" 
member="isEnabled" error name="(unset)" requested_reply="0" 
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6 
--pam-login 13 14 " label="unconfined")
  [5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting 
kwalletd6 (isEnabled)
  [5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call 
method: org.kde.KLauncher.start_service_by_desktop_name: object_path= 
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.kde.klauncher was not provided by any .service files
  [5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting 
klauncher to start kwalletd6
  [5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call 
method: org.kde.KWallet.close: object_path= /modules/kwalletd6: 
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.113" (uid=1000 pid=5362 
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom" 
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet" 
member="close" error name="(unset)" requested_reply="0" 
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6 
--pam-login 13 14 " label="unconfined")
  [5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting 
kwalletd6 (close)
  -

  Followed by hundreds of messages as the following:

  -
  ERROR:login_database.cc(1046) Password decryption failed, encryption_result 
is 2
  -

  It appears to work to "just" whitelist the new kwalletd module name in

  /var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
  /var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)

  followed by

  $ systemctl restart apparmor
  $ systemctl restart snapd.apparmor
  $ systemctl restart apparmor

  (Not sure if both of these are necessary, and if so, in what order.)

  and completely restart Chromium.

  The new KWallet section looks as follows - I only added the ",6" to
  the patterns:

  -

  # KWallet's client API is still in use in KDE/Plasma. It's DBus API relies 
upon
  # member data for access to its 'folders' and 'entries' and it therefore does
  # not allow for application isolation via AppArmor. For details, see:
  # - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
  #
  dbus (receive, send)
  bus=session
  path=/modules/kwalletd{,5,6}
  interface=org.freedesktop.DBus.*
  peer=(label=unconfined),

  dbus (receive, send)
  bus=session
  path=/modules/kwalletd{,5,6}
  interface=org.kde.KWallet
  peer=(label=unconfined),

  -

  I hope that at least this report may be found by other people running
  into the same trouble I just did...

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


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

[Desktop-packages] [Bug 2051074] Update Released

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

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Mantic:
  Fix Released
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

This bug was fixed in the package mutter - 42.9-0ubuntu7

---
mutter (42.9-0ubuntu7) jammy; urgency=medium

  * Add build-Set-built-headers-as-libmutter_dep-sources.patch to prevent
occasional build failures depending on parallelism (LP: #2055530)
  * Add cogl-gl-framebuffer-Fix-inverted-test-in-ensure_bits_init.patch to
fix test failures in mutter:cogl+cogl/conform / framebuffer-get-bits
when Mesa >= 23.1.1 (LP: #2055519)

mutter (42.9-0ubuntu6) jammy; urgency=medium

  [ Kai-Heng Feng ]
  * Fix mirror mode on reduced blanking panel. (LP: #2051074)

  [ Daniel van Vugt ]
  * Add compositor-x11-Sync-again-at-the-end-of-before_paint.patch
to fix incomplete redraws in X11 virtual machines (LP: #2054510)
  * debian/control.in: Stop automatically reverting to the old uploaders.

 -- Daniel van Vugt   Fri, 01 Mar 2024
17:47:40 +0800

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

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Mantic:
  Fix Released
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg

This bug was fixed in the package mutter - 42.9-0ubuntu7

---
mutter (42.9-0ubuntu7) jammy; urgency=medium

  * Add build-Set-built-headers-as-libmutter_dep-sources.patch to prevent
occasional build failures depending on parallelism (LP: #2055530)
  * Add cogl-gl-framebuffer-Fix-inverted-test-in-ensure_bits_init.patch to
fix test failures in mutter:cogl+cogl/conform / framebuffer-get-bits
when Mesa >= 23.1.1 (LP: #2055519)

mutter (42.9-0ubuntu6) jammy; urgency=medium

  [ Kai-Heng Feng ]
  * Fix mirror mode on reduced blanking panel. (LP: #2051074)

  [ Daniel van Vugt ]
  * Add compositor-x11-Sync-again-at-the-end-of-before_paint.patch
to fix incomplete redraws in X11 virtual machines (LP: #2054510)
  * debian/control.in: Stop automatically reverting to the old uploaders.

 -- Daniel van Vugt   Fri, 01 Mar 2024
17:47:40 +0800

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

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

Title:
  Incomplete screen redraws in virtual machines running Xorg

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

Bug description:
  [ Impact ]

  When using software rendering on Xorg (so usually just in VMs), some
  parts of app windows may fail to redraw.

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

  [ Test Plan ]

  1. Set up a virtual machine without graphics acceleration.
  2. Log into 'Ubuntu on Xorg'.
  3. Open Settings > About and verify Graphics = llvmpipe (or "Software 
Rendering"), and Windowing System = X11.
  4. sudo snap install chromium
  5. Open Chromium and find a web page with lots of text. Plain text without 
any links and staying at the top of the page will work best because you don't 
want to trigger any scrolling.
  6. Start selecting text with the mouse and while holding the button move the 
mouse up and down rapidly. Avoid triggering any page scrolling.
  7. Release the mouse button in roughly the middle of the area of text that 
was selected.
  8. Verify the remaining text selection is contiguous and not broken into 
multiple disconnected text selections (the bug).
  9. Repeat steps 7 and 8 several times to be sure.

  [ Where problems could occur ]

  The fix adds a new synchronization point between the compositor and X
  server. This should be inconsequential, although there is a "sync
  ring" in mutter used for this, and if a mistake occurs there then
  other parts of the desktop could appear to stop responding in Xorg
  sessions.

  [ Other Info ]

  This is a regression that started in 3.37.3 due to
  https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda.

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


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

[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

This bug was fixed in the package mutter - 45.2-0ubuntu4

---
mutter (45.2-0ubuntu4) mantic; urgency=medium

  [ Kai-Heng Feng ]
  * Fix mirror mode on reduced blanking panel. (LP: #2051074)

  [ Daniel van Vugt ]
  * Add compositor-x11-Sync-again-at-the-end-of-before_paint.patch
to fix incomplete redraws in X11 virtual machines (LP: #2054510)

 -- Daniel van Vugt   Thu, 22 Feb 2024
16:32:33 +0800

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

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Mantic:
  Fix Released
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On systems equipped with reduced blanking panel, mirror mode can result to no 
image on external monitor.
  The reason is due to current fallback modes don't have pixelclock for reduced 
blanking, so inadequate refresh rate is used to mode set, and result with 
atomic commit failure.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449
  Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to 
meet pixelclock requirement in order to pick the right refresh rate.

  [Test]
  Connect an external monitor to affected system. Use the monitor hotkey to 
switch to mirror mode or use GNOME control center to choose mirror mode. With 
the patch included, the issue is no longer observed.

  [Where problems could occur]
  The modelines of reduced blanking have reversed Hsync and Vsync flags, so if 
the driver doesn't handle those flags correctly, the atomic modeset/commit may 
fail.

  I haven't observe any issue on Intel/AMD/Nvidia GPU so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Desktop-packages] [Bug 2054510] Update Released

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

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

Title:
  Incomplete screen redraws in virtual machines running Xorg

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

Bug description:
  [ Impact ]

  When using software rendering on Xorg (so usually just in VMs), some
  parts of app windows may fail to redraw.

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

  [ Test Plan ]

  1. Set up a virtual machine without graphics acceleration.
  2. Log into 'Ubuntu on Xorg'.
  3. Open Settings > About and verify Graphics = llvmpipe (or "Software 
Rendering"), and Windowing System = X11.
  4. sudo snap install chromium
  5. Open Chromium and find a web page with lots of text. Plain text without 
any links and staying at the top of the page will work best because you don't 
want to trigger any scrolling.
  6. Start selecting text with the mouse and while holding the button move the 
mouse up and down rapidly. Avoid triggering any page scrolling.
  7. Release the mouse button in roughly the middle of the area of text that 
was selected.
  8. Verify the remaining text selection is contiguous and not broken into 
multiple disconnected text selections (the bug).
  9. Repeat steps 7 and 8 several times to be sure.

  [ Where problems could occur ]

  The fix adds a new synchronization point between the compositor and X
  server. This should be inconsequential, although there is a "sync
  ring" in mutter used for this, and if a mistake occurs there then
  other parts of the desktop could appear to stop responding in Xorg
  sessions.

  [ Other Info ]

  This is a regression that started in 3.37.3 due to
  https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda.

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


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

[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg

This bug was fixed in the package mutter - 45.2-0ubuntu4

---
mutter (45.2-0ubuntu4) mantic; urgency=medium

  [ Kai-Heng Feng ]
  * Fix mirror mode on reduced blanking panel. (LP: #2051074)

  [ Daniel van Vugt ]
  * Add compositor-x11-Sync-again-at-the-end-of-before_paint.patch
to fix incomplete redraws in X11 virtual machines (LP: #2054510)

 -- Daniel van Vugt   Thu, 22 Feb 2024
16:32:33 +0800

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

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

Title:
  Incomplete screen redraws in virtual machines running Xorg

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

Bug description:
  [ Impact ]

  When using software rendering on Xorg (so usually just in VMs), some
  parts of app windows may fail to redraw.

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

  [ Test Plan ]

  1. Set up a virtual machine without graphics acceleration.
  2. Log into 'Ubuntu on Xorg'.
  3. Open Settings > About and verify Graphics = llvmpipe (or "Software 
Rendering"), and Windowing System = X11.
  4. sudo snap install chromium
  5. Open Chromium and find a web page with lots of text. Plain text without 
any links and staying at the top of the page will work best because you don't 
want to trigger any scrolling.
  6. Start selecting text with the mouse and while holding the button move the 
mouse up and down rapidly. Avoid triggering any page scrolling.
  7. Release the mouse button in roughly the middle of the area of text that 
was selected.
  8. Verify the remaining text selection is contiguous and not broken into 
multiple disconnected text selections (the bug).
  9. Repeat steps 7 and 8 several times to be sure.

  [ Where problems could occur ]

  The fix adds a new synchronization point between the compositor and X
  server. This should be inconsequential, although there is a "sync
  ring" in mutter used for this, and if a mistake occurs there then
  other parts of the desktop could appear to stop responding in Xorg
  sessions.

  [ Other Info ]

  This is a regression that started in 3.37.3 due to
  https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda.

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


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

[Desktop-packages] [Bug 2055530] Update Released

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

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

Title:
  Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-
  types.h: No such file or directory]

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

  Mutter failed to build, only once, on jammy amd64:

  In file included from ../src/backends/meta-backend-private.h:39,
   from ../src/backends/x11/meta-backend-x11.h:31,
   from ../src/backends/x11/nested/meta-backend-x11-nested.h:25,
   from ../src/tests/meta-backend-test.h:23,
   from ../src/tests/meta-backend-test.c:22:
  ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: 
meta/meta-enum-types.h: No such file or directory
     41 | #include "meta/meta-enum-types.h"
    | ^~~~
  compilation terminated.

  Seems like an old issue that you can hit at random in highly parallel
  builds. Because meta-enum-types.h is auto-generated its consumers need
  to declare stronger dependencies.

  [ Test Plan ]

  Build mutter.

  [ Where problems could occur ]

  More build failures or accidentally depending on meson features that
  don't exist in jammy.

  [ Other Info ]

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


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

[Desktop-packages] [Bug 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)

This bug was fixed in the package mutter - 42.9-0ubuntu7

---
mutter (42.9-0ubuntu7) jammy; urgency=medium

  * Add build-Set-built-headers-as-libmutter_dep-sources.patch to prevent
occasional build failures depending on parallelism (LP: #2055530)
  * Add cogl-gl-framebuffer-Fix-inverted-test-in-ensure_bits_init.patch to
fix test failures in mutter:cogl+cogl/conform / framebuffer-get-bits
when Mesa >= 23.1.1 (LP: #2055519)

mutter (42.9-0ubuntu6) jammy; urgency=medium

  [ Kai-Heng Feng ]
  * Fix mirror mode on reduced blanking panel. (LP: #2051074)

  [ Daniel van Vugt ]
  * Add compositor-x11-Sync-again-at-the-end-of-before_paint.patch
to fix incomplete redraws in X11 virtual machines (LP: #2054510)
  * debian/control.in: Stop automatically reverting to the old uploaders.

 -- Daniel van Vugt   Fri, 01 Mar 2024
17:47:40 +0800

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/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 Released

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 :

[Desktop-packages] [Bug 2055519] Update Released

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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 Released

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 2055530] Re: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]