[Desktop-packages] [Bug 2060389] Re: Lock screen doesn't prevent media keys from working

[Jussi Lind]

** Information type changed from Private Security to Public Security

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

Title:
  Lock screen doesn't prevent media keys from working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Open a music player e.g. Audacious with some music content
  2) Lock the screen
  3) Press Play/Pause media button (I'm using an Apple USB keyboard)

  What happens:

  Audacious starts playing music.

  What should happen:

  Nothing, because the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
  Uname: Linux 5.15.0-100-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 17:55:16 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-09 (1610 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2023-01-02 (460 days ago)

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


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

[Desktop-packages] [Bug 2060613] [NEW] Gedit sometimes crashes by segmentation fault at closure

[Zalán Hári]

Public bug reported:

When I do not wait until the document is fully saved (or I only wait a
short interval) gedit crashes with segmentation fault after a few
seconds. It has not lead to data loss yet, but it is truly unpleasant,
let alone if we include that otherwise it floods the terminal with
critical GTK errors... (bug #2055010)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gedit 46.2-1build1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 07:16:42 2024
InstallationDate: Installed on 2023-07-05 (279 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

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


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

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

Title:
  Gedit sometimes crashes by segmentation fault at closure

Status in gedit package in Ubuntu:
  New

Bug description:
  When I do not wait until the document is fully saved (or I only wait a
  short interval) gedit crashes with segmentation fault after a few
  seconds. It has not lead to data loss yet, but it is truly unpleasant,
  let alone if we include that otherwise it floods the terminal with
  critical GTK errors... (bug #2055010)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gedit 46.2-1build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 07:16:42 2024
  InstallationDate: Installed on 2023-07-05 (279 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

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


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

[Desktop-packages] [Bug 2060423] Re: gnome-shell crashes ("Oh no! Something has gone wrong.") instead of displaying a login screen (mutter-common package version mismatch)

[Daniel van Vugt]

I'm hoping this might also explain something of bug 2054761

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

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

Title:
  gnome-shell crashes ("Oh no! Something has gone wrong.") instead of
  displaying a login screen (mutter-common package version mismatch)

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  gnome-shell crashes instead of displaying a login screen:

  gnome-shell[1954]: Running GNOME Shell (using mutter 45.3) as a Wayland 
display server
  gnome-shell[1954]: Settings schema 'org.gnome.mutter.x11' is not installed

  It seems the cause is a package version mismatch in mutter-common:

  ii  gir1.2-mutter-13:amd64 45.3-1ubuntu1  
   amd64GObject introspection data for Mutter
  ii  libmutter-13-0:amd64   45.3-1ubuntu1  
   amd64window manager library from the Mutter window 
manager
  ii  libmutter-13-dev:amd64 45.3-1ubuntu1  
   amd64Development files for the Mutter window manager
  ii  libmutter-test-13  45.3-1ubuntu1  
   amd64Test helper library for GNOME's window manager 
library
  ii  mutter 45.3-1ubuntu1  
   amd64Example window manager using GNOME's window manager 
library
  ii  mutter-13-tests45.3-1ubuntu1  
   amd64Tests for GNOME's window manager library
  ii  mutter-common  46.0-1ubuntu6  
   all  shared files for the Mutter window manager
  ii  mutter-common-bin  45.3-1ubuntu1  
   amd64shared programs for the Mutter window manager

  Downgrading mutter-common to
  
https://launchpad.net/ubuntu/+source/mutter/45.3-1ubuntu1/+build/27621415/+files/mutter-
  common_45.3-1ubuntu1_all.deb appears to fix it.

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


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

[Desktop-packages] [Bug 2060611] [NEW] I get login keyring unlock problem every startup

[Zalán Hári]

Public bug reported:

I am using Noble Numbat alpha. I was hoping that I get the beta version
and everything will be more stable. But the beta has been delayed, and
after an upgrade at April 5 2024, something has gone wrong. Now, every
time I log in after startup, I get the following message:

„The login keyring did not get unlocked when you logged into your
computer”.


Fixing that bug would probably improve the user experience a bit.

GDM version: 46.0


PS: It is possible that it is a problem with gnome-session rather than GDM.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 46.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 07:07:53 2024
InstallationDate: Installed on 2023-07-05 (279 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.apport: [modified]
modified.conffile..etc.pam.d.gdm-password: [modified]
mtime.conffile..etc.gdm3.custom.conf: 2023-08-04T18:46:39.585253
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
mtime.conffile..etc.pam.d.gdm-password: 2023-08-04T18:47:38.965793

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


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

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

Title:
  I get login keyring unlock problem every startup

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I am using Noble Numbat alpha. I was hoping that I get the beta
  version and everything will be more stable. But the beta has been
  delayed, and after an upgrade at April 5 2024, something has gone
  wrong. Now, every time I log in after startup, I get the following
  message:

  „The login keyring did not get unlocked when you logged into your
  computer”.

  
  Fixing that bug would probably improve the user experience a bit.

  GDM version: 46.0

  
  PS: It is possible that it is a problem with gnome-session rather than GDM.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdm3 46.0-2ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 07:07:53 2024
  InstallationDate: Installed on 2023-07-05 (279 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  modified.conffile..etc.pam.d.gdm-password: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2023-08-04T18:46:39.585253
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  mtime.conffile..etc.pam.d.gdm-password: 2023-08-04T18:47:38.965793

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


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

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

[Steve Beattie]

** Also affects: xorg-server (Ubuntu Noble)
   Importance: High
   Status: Triaged

** Also affects: xwayland (Ubuntu Noble)
   Importance: High
   Status: Triaged

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

** Also affects: xwayland (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: xorg-server (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu Focal)
   Status: New => In Progress

** Changed in: xorg-server (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: xorg-server (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu Mantic)
   Status: New => In Progress

** No longer affects: xwayland (Ubuntu Focal)

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

** Changed in: xwayland (Ubuntu Jammy)
   Status: New => In Progress

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

** Changed in: xwayland (Ubuntu Mantic)
   Status: New => In Progress

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

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

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged
Status in xwayland package in Ubuntu:
  Triaged
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Jammy:
  In Progress
Status in xwayland source package in Jammy:
  In Progress
Status in xorg-server source package in Mantic:
  In Progress
Status in xwayland source package in Mantic:
  In Progress
Status in xorg-server source package in Noble:
  Triaged
Status in xwayland source package in Noble:
  Triaged

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

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

[Desktop-packages] [Bug 2060555] Re: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones

[Daniel van Vugt]

See also bug 205 having trouble with the same chip.

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

** Changed in: linux-hwe-6.5 (Ubuntu)
   Status: New => Incomplete

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

Title:
  [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl
  headpones

Status in bluez package in Ubuntu:
  Incomplete
Status in linux-hwe-6.5 package in Ubuntu:
  Incomplete

Bug description:
  The keyboard and mouse are dell brand and they were able to connect to
  my system and now they cannot. My headdpone are JBL ear pods and they
  were able to be detected but never connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 09:42:46 2024
  InstallationDate: Installed on 2024-03-31 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: HP HP ProBook x360 435 G7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2023
  dmi.bios.release: 13.0
  dmi.bios.vendor: HP
  dmi.bios.version: S80 Ver. 01.13.00
  dmi.board.name: 8735
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.2D.00
  dmi.chassis.asset.tag: 5CG0340N3Z
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.45
  dmi.modalias: 
dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA:
  dmi.product.family: 103C_5336AN HP ProBook x360
  dmi.product.name: HP ProBook x360 435 G7
  dmi.product.sku: 17G39UT#ABA
  dmi.sys.vendor: HP
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 1C:BF:C0:C6:9F:CA  ACL MTU: 1021:6  SCO MTU: 255:12
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:173926 acl:0 sco:0 events:4200 errors:0
TX bytes:58386 acl:0 sco:0 commands:1483 errors:0

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


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

[Desktop-packages] [Bug 2060458] Re: ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap

[Daniel van Vugt]

Those errors are coming from some custom Xorg driver ("ARMSOC"?), not
from the Ubuntu archive AFAICS. Perhaps from LP-PPA-tchavadar-xilinx

But we should be using Wayland on Xilinx now, since I implemented it a
couple of years ago... Please try Wayland and tell us if any similar
failures occur.

** Tags added: xilinx

** Package changed: gdm3 (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 gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2060458

Title:
  ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap

Status in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I see the following messages keeps being logged in /var/log/syslog:
  ```
  Apr  8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:04:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:04:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:05:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:05:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:06:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:06:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:07:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:07:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:08:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:08:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:09:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:09:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:10:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:10:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:11:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:11:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:12:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:12:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:13:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:13:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  Apr  8 10:14:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:14:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu7.22.04.4
  ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136
  Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: config-disk (/dev/mmcblk1p1)
  Date: Mon Apr  8 10:15:18 2024
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2023-09-20T10:06:31

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


-- 
Maili

[Desktop-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C

[Kai-Heng Feng]

OK, it's likely caused by mutter upgrade, but let's make sure that's the
case. Can you please downgrade the mutter to verify the old version
works?

Please run `sudo apt install libmutter-10-0=42.9-0ubuntu5 mutter-
common=42.9-0ubuntu5 gir1.2-mutter-10=42.9-0ubuntu5` to downgrade
related packages.

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

Title:
  Resolution drop on third monitor on USB C

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  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 23.0.4-0ubuntu1~22.04.1
  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

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


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

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

[Launchpad Bug Tracker]

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

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

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

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

Status in gnome-keyring package in Ubuntu:
  Confirmed

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

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

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

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


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

[Desktop-packages] [Bug 2052436] Re: Thunderbird calendar notifications close themselves

[Launchpad Bug Tracker]

[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Thunderbird calendar notifications close themselves

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  I was sitting and staring at my computer when a Thunderbird calendar
  notification decided to close itself and poof! it was gone.

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


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

[Desktop-packages] [Bug 2052740] Re: Crossed circle keeps popping up on my screen

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Crossed circle keeps popping up on my screen

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I noticed this crossed circle when i started using linux (pop_os).
  Initially it seemed insignificant and harmless, but over time it
  started affecting typing with my keyboard. It also affected my video
  playback - always pausing the video.

  I installed the ubuntu distro with hopes of eliminating the problem,
  but it still persists. The only improvement is that the crossed circle
  doesn't interfer with my keyboard and video playback for now, despite
  it still appears on my screen. But i believe it's just a matter of
  time before the interference resumes.

  I have attached a screenshot to this report containing the crossed
  circle symbol.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  8 22:38:11 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 03) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GeminiLake [UHD Graphics 605] 
[103c:84d4]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 04f3:250e Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 002: ID 0bda:58ed Realtek Semiconductor Corp. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs2xx
  ProcEnviron:
   LANGUAGE=en_NG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NG
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_3903w5@/vmlinuz-6.2.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_3903w5 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2022
  dmi.bios.release: 15.71
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.71
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84D4
  dmi.board.vendor: HP
  dmi.board.version: 94.30
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 94.30
  dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd11/14/2022:br15.71:efr94.30:svnHP:pnHPLaptop15-bs2xx:pvrType1ProductConfigId:rvnHP:rn84D4:rvr94.30:cvnHP:ct10:cvrChassisVersion:sku4ND16UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs2xx
  dmi.product.sku: 4ND16UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2052750] Re: gnome-shell high cpu utilization

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  gnome-shell high cpu utilization

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  gnome-shell high cpu usage

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  8 15:34:04 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-12-28 (42 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Daniel van Vugt]

Nathan, if you experience corruption then please see bug 1876632.

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

[Desktop-packages] [Bug 2011404] Re: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire

[Guillaume Pothier]

** Tags added: noble

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

Title:
  vanilla-gnome-desktop depends on pulseaudio which conflicts with
  pipewire

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in ubuntu-gnome-meta package in Ubuntu:
  Confirmed

Bug description:
  Package vanilla-gnome-desktop 0.97 depends on pulseaudio which
  conflicts with pipewire-alsa and pipewire-audio which in turn are
  required for upgrading gnome to version 43.

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


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

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

[Daniel van Vugt]

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

** Changed in: xwayland (Ubuntu)
   Status: New => Triaged

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

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

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

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged
Status in xwayland package in Ubuntu:
  Triaged

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

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

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

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


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

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

[Tim Richardson]

@sbeattie I tested the package you built for 22.04 and it fixes the
problem for me.

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

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

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged
Status in xwayland package in Ubuntu:
  Triaged

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

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

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

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


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

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

[Tim Richardson]

@sbeattie It's broken in mantic too. In xwayland, the window dies. in
xorg, the session crashes, badly.

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

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

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

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

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

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

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


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

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

[Daniel van Vugt]

Are the unresolved issues only occurring with multi-monitor or multi-GPU
systems?

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

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

[Daniel van Vugt]

** Also affects: xorg-server via
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659
   Importance: Unknown
   Status: Unknown

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Triaged

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

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

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

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

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

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

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


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

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

[Steve Beattie]

I have prepared test packages for ubuntu 22.04 LTS/jammy in the
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages PPA for both xorg-server:

  https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+sourcepub/15921802/+listing-archive-extra

and for xwayland:

  https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+sourcepub/15921798/+listing-archive-extra

I was able to reproduce the crash under Xwayland in a jammy vm with both
intellij and the glyph_memleak.c reproducer, and using the proposed
upstream patch seems to address the crash, but more testing is welcome.

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

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

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

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

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

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

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


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

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

[Steve Beattie]

The reproducer https://bugs.freedesktop.org/attachment.cgi?id=28621 from
the original 2009 bug report
https://bugs.freedesktop.org/show_bug.cgi?id=23286 does seem to work at
triggering this issue, at least under Xwalyand.

** Bug watch added: freedesktop.org Bugzilla #23286
   https://bugs.freedesktop.org/show_bug.cgi?id=23286

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

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

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

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


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

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

[Steve Beattie]

Are people seeing this issue with any other Ubuntu releases, which also
received updates addressing CVE-2024-31083, or is this strictly
affecting the version in 22.04/jammy?

It looks like
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1476 has a
proposed fix, in
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1476.patch
.

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

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

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

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


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

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

[Bryce Harrington]

** Changed in: meson (Ubuntu Jammy)
   Status: New => Won't Fix

** Changed in: openvswitch (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: spice-protocol (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: virglrenderer (Ubuntu Jammy)
   Status: New => Fix Committed

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

-- 
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:
  Won't Fix
Status in openvswitch source package in Jammy:
  In Progress
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:
  Fix Committed
Status in spice-vdagent source package in Jammy:
  Fix Committed
Status in virglrenderer source package in Jammy:
  Fix Committed
Status in virt-manager source package in Jammy:
  Fix Committed

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 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

[Tim Richardson]

Yeah, for me it crashed 100% of the time with no changes, and removing a
configuration file (which among other things removed my non-default
preference for grayscale antialias) completely stopped the crashing.
This is in a kvm/qemu VM. So from my perspective, and from a few others
users, it looks like the cause and a good workaround. But other people
in the set of JetBrains tickets report intermittent, unpredictable
crashing that doesn't benefit from such a settings change. I think think
upstream is talking about race conditions.


So far in the bug report (the Ubuntu one) I don't understand what the proposed 
course of action is.

I think this is the upstream bug report:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1659
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659

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

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

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

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


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

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

[Nathan Bryant]

threadbareobserve, the nvidia driver can be downgraded to 535 without
too much work. I'd make sure all the related packages are removed before
installing 535.

Might help the developers to know what version of Ubuntu you're running.

I'm running a 22.04 desktop with a 4070 card, and the PPA does *not* fix
the problem for me. It removes the lag, but that means the corrupted
screen just happens faster. This is a bit intermittent and hard to pin
down, but I've particularly noticed this after attempting to paste text
into Gnome-Terminal; only the first few pasted characters might be
echoed, then it gets into a state where keyboard input is processed but
not all of it is echoed.

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

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

[Alex Murray]

Public bug reported:

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

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

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

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


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

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

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

Status in gnome-keyring package in Ubuntu:
  New

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

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

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

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


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

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

[Steve Langasek]

** Changed in: c2esp (Ubuntu)
   Status: New => Fix Committed

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

Title:
  proposed-migration for cups 2.4.7-1.2ubuntu1

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

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 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

[Steve Langasek]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to c2esp 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 c2esp package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Fix Released

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/c2esp/+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 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

[Ian Mackenzie]

After kernel + x.org updates this week, firefox is now displaying
properly using xserver-xorg on the Athlon 200GE.

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

[threadbareobserve]

I have no reverted back to downgrading mutter as per previous posted and
lag has subsided however I can't use NVIDIA 550 driver with the old
mutter for some reason so I am stuck using intel graphics which doesn't
do a great job driving all 3 screens I have. NVIDA not downgrading is a
different issue though mover the freezing/lagging still exist even
though mutter was fixed.

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

[Desktop-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C

[Robby ROUDON]

Join displays

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

Title:
  Resolution drop on third monitor on USB C

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  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 23.0.4-0ubuntu1~22.04.1
  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

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


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

[Desktop-packages] [Bug 2019951] Re: [MIR] libmysofa

[Seth Arnold]

** Changed in: libmysofa (Ubuntu)
   Status: New => Won't Fix

** Changed in: libmysofa (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] libmysofa

Status in libmysofa package in Ubuntu:
  Won't Fix

Bug description:
  [Availability]
  The package libmysofa is already in Ubuntu universe.
  The package libmysofa build for the architectures it is designed to work on.
  It currently builds and works for architetcures: amd64 arm64 armhf i386 
ppc64el riscv64 s390x
  Link to package https://launchpad.net/ubuntu/+source/libmysofa

  [Rationale]
  - The package libmysofa is required in Ubuntu main as a (optional) depends of 
pipewire
  - the library parses spatial audio files which are used by 3D audio systems
  - the libmysofa1 binary needs to be promoted

  - There is no other/better way to solve this that is already in main or
    should go universe->main instead of this.

  - The package libmysofa is required in Ubuntu main no later than August 17th
    due to mantic feature freeze

  [Security]
  - Had 15 security issues in the past which seemed all addressed now in the 
current serie, https://ubuntu.com/security/cves?package=libmysofa
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16095
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16094
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16093
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16092
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16091
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10672
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3756
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6860
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20063
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20016
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36152
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36151
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36150
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36149
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36148

  those are also listed in https://security-
  tracker.debian.org/tracker/source-package/libmysofa

  - no `suid` or `sgid` binaries
  - no executables in `/sbin` and `/usr/sbin`
  - Package does not install services, timers or recurring jobs
  - Packages does not open privileged ports (ports < 1024)
  - Packages does not contain extensions to security-sensitive software

  [Quality assurance - function/usage]
  - The package works well right after install

  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu/Upstream and only has minor 
open bugs
    - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libmysofa/+bug
    - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libmysofa
    - Upstream https://github.com/hoene/libmysofa/issues
  - The package does not deal with exotic hardware we cannot support

  [Quality assurance - testing]
  - The package runs a test suite on build time, if it fails
    it makes the build fail, link to build log 
https://launchpadlibrarian.net/31466/buildlog_ubuntu-mantic-amd64.libmysofa_1.3.1~dfsg0-1ubuntu1_BUILDING.txt.gz

  - The package runs an autopkgtest, and is currently passing on
    amd64 arm64 armhf ppc64el s390x
  https://autopkgtest.ubuntu.com/packages/libm/libmysofa

  - The tests fail on i386 due to installability issues of depends which
  isn't an issue

  [Quality assurance - packaging]
  - debian/watch is present and works

  - debian/control defines a correct Maintainer

  - This package has no lintian warnings

  - Please link to a recent build log of the package
  
https://launchpadlibrarian.net/632293649/buildlog_ubuntu-lunar-amd64.libmysofa_1.3.1~dfsg0-1_BUILDING.txt.gz
  - Please attach the full output you have got from `lintian --pedantic`

  # lintian --pedantic libmysofa_1.3.1~dfsg0-1_amd64.changes
  #

  - Lintian overrides are not present

  - This package does not rely on obsolete or about to be demoted packages.
  - This package has no python2 or GTK2 dependencies

  - The package will be installed by default, but does not ask debconf
  questions

  - Packaging and build is easy, link to debian/rules
  https://salsa.debian.org/multimedia-
  team/libmysofa/-/blob/master/debian/rules

  [UI standards]
  - Application is not end-user facing (does not need translation)

  [Dependencies]
  - No further depends or recommends dependencies that are not yet in main

  [Standards compliance]
  - This package correctly follows FHS and Debian Policy

[Desktop-packages] [Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64

[Chris Peterson]

Yes, a no-change rebuild fixes the issue.

Please see attached debdiff for the fix.

I have provided a PPA with the build and tests:

PPA: https://launchpad.net/~cpete/+archive/ubuntu/upower

arm64 autopkgtest log:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete-
upower/noble/arm64/u/upower/20240407_191552_37f4e@/log.gz

arm64 autopkgtests artifacts:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete-
upower/noble/arm64/u/upower/20240407_191552_37f4e@/artifacts.tar.gz



** Patch added: "upower_1.90.2-8build3_1.90.2-8build4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+attachment/5762206/+files/upower_1.90.2-8build3_1.90.2-8build4.debdiff

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

Title:
  upower/1.90.2-8build3 autopkgtest failure on arm64

Status in upower package in Ubuntu:
  In Progress

Bug description:
  autopkgtests fail, only on arm64, after a no-change-rebuild, with the
  following output:

  689s TI:22:39:23 Handling SIGTERM
  689s .
  689s ==
  689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart)
  689s --
  689s Traceback (most recent call last):
  689s   File "/usr/lib/python3.12/shutil.py", line 785, in rmtree
  689s _rmtree_safe_fd(fd, path, onexc)
  689s   File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd
  689s onexc(os.unlink, fullname, err)
  689s   File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd
  689s os.unlink(entry.name, dir_fd=topfd)
  689s FileNotFoundError: [Errno 2] No such file or directory: 
'history-time-full-G935_Gaming_Headset.dat.KL0SL2'
  689s
  689s ==
  689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart)
  689s --
  689s Traceback (most recent call last):
  689s   File "/usr/libexec/upower/integration-test.py", line 2558, in 
test_daemon_restart
  689s self.stop_daemon()
  689s   File "/usr/libexec/upower/integration-test.py", line 239, in 
stop_daemon
  689s self.assertEqual(self.daemon.wait(timeout=5.0), 0)
  689s AssertionError: -15 != 0
  689s
  689s ==
  689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart)
  689s --
  689s Traceback (most recent call last):
  689s   File "/usr/libexec/upower/integration-test.py", line 173, in tearDown
  689s self.stop_daemon()
  689s   File "/usr/libexec/upower/integration-test.py", line 239, in 
stop_daemon
  689s self.assertEqual(self.daemon.wait(timeout=5.0), 0)
  689s AssertionError: -15 != 0
  689s
  689s --
  689s Ran 66 tests in 194.378s
  689s
  689s FAILED (failures=2, errors=1)

  full log:

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz

  These test passed in the previous version: 
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz

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


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

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

[Bug Watch Updater]

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

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

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

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

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

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

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

  I have reported the issue to the upstream developers

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

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


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

[Desktop-packages] [Bug 2060555] [NEW] I cant connect my bluetooth keyboard, mouse and jbl headpones

[Niri Centeno]

Public bug reported:

The keyboard and mouse are dell brand and they were able to connect to
my system and now they cannot. My headdpone are JBL ear pods and they
were able to be detected but never connected.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  8 09:42:46 2024
InstallationDate: Installed on 2024-03-31 (7 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: HP HP ProBook x360 435 G7
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2023
dmi.bios.release: 13.0
dmi.bios.vendor: HP
dmi.bios.version: S80 Ver. 01.13.00
dmi.board.name: 8735
dmi.board.vendor: HP
dmi.board.version: KBC Version 09.2D.00
dmi.chassis.asset.tag: 5CG0340N3Z
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 9.45
dmi.modalias: 
dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA:
dmi.product.family: 103C_5336AN HP ProBook x360
dmi.product.name: HP ProBook x360 435 G7
dmi.product.sku: 17G39UT#ABA
dmi.sys.vendor: HP
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 1C:BF:C0:C6:9F:CA  ACL MTU: 1021:6  SCO MTU: 255:12
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:173926 acl:0 sco:0 events:4200 errors:0
TX bytes:58386 acl:0 sco:0 commands:1483 errors:0

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


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

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

Title:
  I cant connect my bluetooth keyboard, mouse and jbl headpones

Status in bluez package in Ubuntu:
  New

Bug description:
  The keyboard and mouse are dell brand and they were able to connect to
  my system and now they cannot. My headdpone are JBL ear pods and they
  were able to be detected but never connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 09:42:46 2024
  InstallationDate: Installed on 2024-03-31 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: HP HP ProBook x360 435 G7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2023
  dmi.bios.release: 13.0
  dmi.bios.vendor: HP
  dmi.bios.version: S80 Ver. 01.13.00
  dmi.board.name: 8735
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.2D.00
  dmi.chassis.asset.tag: 5CG0340N3Z
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.45
  dmi.modalias: 
dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA:
  dmi.product.family: 103C_5336AN HP ProBook x360
  dmi.product.name: HP ProBook x360 435 G7
  dmi.product.sku: 17G39UT#ABA
  dmi.sys.vendor: HP
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 1C:BF:C0:C6:9F:CA  ACL MTU: 1021:6  SCO MTU: 255:12
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:173926 acl:0 sco:0 events:4200 errors:0
TX bytes:58386 acl:0 sco:0 commands:1483 errors:0

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


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

[Desktop-packages] [Bug 2060548] Re: [FFe] Update and seed wsl-pro-service in the WSL images

[Didier Roche-Tolomelli]

** Summary changed:

- Update and seed wsl-pro-service in the WSL images
+ [FFe] Update and seed wsl-pro-service in the WSL images

** Description changed:

  This is a new package for this release. It’s only functional with a
  Windows agent which is not publically released and under beta for now.
  
  As the end of the beta will be after the 24.04 release, we want to get
  as close as possible to the current code level, knowing that current
  code will still certainly grow feature-wise once with the Beta user
  feedback.
  
  However, having it seeded (the MIR is approved and security issues fixed
  but the certificate one, which has been discussed as minor for now) with
  the current code level will be great to diminish the diff when the SRU
  that will be needed then.
  
  The impact is on existing non beta users (and beta users are using a ppa
  with the ppa containing the current code level).
  
  Current diff is large as the development is very active and won’t really
  provide anything more. Note that it contains also a packaging change to
  fix bug #2057651.
+ 
+ It also fixes a vulnerability by depending on latest Go and latest
+ x/net/http.

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

Title:
  [FFe] Update and seed wsl-pro-service in the WSL images

Status in ubuntu-meta package in Ubuntu:
  New
Status in wsl-pro-service package in Ubuntu:
  New

Bug description:
  This is a new package for this release. It’s only functional with a
  Windows agent which is not publically released and under beta for now.

  As the end of the beta will be after the 24.04 release, we want to get
  as close as possible to the current code level, knowing that current
  code will still certainly grow feature-wise once with the Beta user
  feedback.

  However, having it seeded (the MIR is approved and security issues
  fixed but the certificate one, which has been discussed as minor for
  now) with the current code level will be great to diminish the diff
  when the SRU that will be needed then.

  The impact is on existing non beta users (and beta users are using a
  ppa with the ppa containing the current code level).

  Current diff is large as the development is very active and won’t
  really provide anything more. Note that it contains also a packaging
  change to fix bug #2057651.

  It also fixes a vulnerability by depending on latest Go and latest
  x/net/http.

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package pygobject - 3.48.2-1

---
pygobject (3.48.2-1) unstable; urgency=medium

  * New upstream release
- Fix gst-python1.0 build (Closes: #1065547) (LP: #2057836)

 -- Jeremy Bícha   Sat, 06 Apr 2024 06:49:50 -0400

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

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

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

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

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

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

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

  I have reported the issue to the upstream developers

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

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


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

[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-raspi-settings - 24.04.2

---
ubuntu-raspi-settings (24.04.2) noble; urgency=medium

  * Removed etc/netplan/01-use-network-manager.yaml: An equivalent is
now provided under /lib by ubuntu-desktop-settings (LP: #2042866)
  * usr/share/initramfs-tools/hooks/zz-exclude-nvidia: New hook to exclude
nvidia modules from the raspi initramfs (LP: #2060032)
  * usr/bin/update-v3d-config: Add script and corresponding service to update
the X11 configuration for Pi 5 displays (LP: #2044718)
  * etc/X11/xorg.conf.d/99-vc4-primary.conf: Renamed to 99-v3d.conf
  * d/ubuntu-raspi-settings-desktop.lintian-overrides: Remove unknown tags,
add tags for update-v3d-config
  * d/ubuntu-raspi-settings.lintian-overrides: Add override for appstream
metadata
  * ubuntu-raspi-settings: Removed lz4 dependency; we removed the need for
this in 24.04.1 when removing the obsolete initramfs-tools hack
  * Remove meson build dependency; dh_install is sufficient

 -- Dave Jones   Wed, 03 Apr 2024 14:37:51
+0100

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

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

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in SDDM:
  New
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-raspi-settings package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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

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

[Derek Konigsberg]

I'm wondering if the anti-aliasing mode is a bit of a red hearing here, or only 
partially related.
In my case, the app that triggers this is CLion 2023.3.  Except in my case, I 
can reproduce it consistently simply by *changing* the anti-aliasing setting 
between subpixel and grayscale (in *either* direction) and clicking "apply."  
But once I log back in and re-launch the app, the system works fine and doesn't 
crash (regardless of the setting).

Outside of that action, the bug behaves more like a time-bomb.  There
seems to be like a 5% chance that clicking the "debug" icon in the
toolbar will take down my X session.  Most of the time it works fine,
until it doesn't.

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

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

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

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


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

[Desktop-packages] [Bug 2060548] [NEW] Update and seed wsl-pro-service in the WSL images

[Didier Roche-Tolomelli]

Public bug reported:

This is a new package for this release. It’s only functional with a
Windows agent which is not publically released and under beta for now.

As the end of the beta will be after the 24.04 release, we want to get
as close as possible to the current code level, knowing that current
code will still certainly grow feature-wise once with the Beta user
feedback.

However, having it seeded (the MIR is approved and security issues fixed
but the certificate one, which has been discussed as minor for now) with
the current code level will be great to diminish the diff when the SRU
that will be needed then.

The impact is on existing non beta users (and beta users are using a ppa
with the ppa containing the current code level).

Current diff is large as the development is very active and won’t really
provide anything more. Note that it contains also a packaging change to
fix bug #2057651.

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

** Affects: wsl-pro-service (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Update and seed wsl-pro-service in the WSL images

Status in ubuntu-meta package in Ubuntu:
  New
Status in wsl-pro-service package in Ubuntu:
  New

Bug description:
  This is a new package for this release. It’s only functional with a
  Windows agent which is not publically released and under beta for now.

  As the end of the beta will be after the 24.04 release, we want to get
  as close as possible to the current code level, knowing that current
  code will still certainly grow feature-wise once with the Beta user
  feedback.

  However, having it seeded (the MIR is approved and security issues
  fixed but the certificate one, which has been discussed as minor for
  now) with the current code level will be great to diminish the diff
  when the SRU that will be needed then.

  The impact is on existing non beta users (and beta users are using a
  ppa with the ppa containing the current code level).

  Current diff is large as the development is very active and won’t
  really provide anything more. Note that it contains also a packaging
  change to fix bug #2057651.

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


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

[Desktop-packages] [Bug 2060546] [NEW] Update authd to current version

[Didier Roche-Tolomelli]

Public bug reported:

Authd is a new package in noble, in universe.

This package is not shipped by default, we made many improvements and
fixes in the current version. We don’t plan to seed it this release,
despite the MIR being approved.

Update contains a lot of vendoring updates, and code changes (using a C
wrapper to wrap around the Go code in the PAM module to fix some
instability), multiple thousands of line due to the C wrapper in
particular. The diff itself will not be meaningful.

Part of meaningful fixes are the default group being added and ssh
precheck API. Full changelog is available at
https://github.com/ubuntu/authd/pull/237/files.

This is the code level we are testing and relying on.

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

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

Title:
  Update authd to current version

Status in authd package in Ubuntu:
  New

Bug description:
  Authd is a new package in noble, in universe.

  This package is not shipped by default, we made many improvements and
  fixes in the current version. We don’t plan to seed it this release,
  despite the MIR being approved.

  Update contains a lot of vendoring updates, and code changes (using a
  C wrapper to wrap around the Go code in the PAM module to fix some
  instability), multiple thousands of line due to the C wrapper in
  particular. The diff itself will not be meaningful.

  Part of meaningful fixes are the default group being added and ssh
  precheck API. Full changelog is available at
  https://github.com/ubuntu/authd/pull/237/files.

  This is the code level we are testing and relying on.

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


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

[Desktop-packages] [Bug 2050884] Re: Ubuntu Metrics server is not accepting reports

[Tim Andersson]

hi, we're still experiencing this just FYI, I've experienced it in every
noble desktop install I've tested today

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

Title:
  Ubuntu Metrics server is not accepting reports

Status in gnome-initial-setup package in Ubuntu:
  In Progress
Status in ubuntu-report package in Ubuntu:
  Triaged

Bug description:
  gnome-initial-setup now prompts to send a report immediately, and when
  it does, it fails, I'll attach a screenshot in the comments. Even when
  I clicked "Don't send to ubuntu" or however it's phrased, I still
  encountered the error message pop up in the comments.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-initial-setup 46~alpha-2ubuntu1
  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
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 10:38:31 2024
  InstallationDate: Installed on 2024-01-23 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[threadbareobserve]

> sudo add-apt-repository ppa:vanvugt/mutter
> sudo apt update
> sudo apt upgrade

I have done the following above but still having lagging issues.
Although the lag appears to be much better in the terminal window. But
every other window it's quite apparent after a few minutes of using the
OS after a reboot.

My Setup
- 2 monitor driven by NVIDIA (`GA104M [GeForce RTX 3070 Mobile / Max-Q]) 
running driver `server-open::550.54.14`
- 1 laptop screen driven by Intel graphics (`TigerLake-H GT1 [UHD Graphics`)

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

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

[Nathan Bryant]

Everyone's been discussing bug 2007742 as something that causes only log
spam, no other issues. My system is still failing to update the screen
after keypresses in gnome-terminal. So maybe those log messages aren't
relevant, but it looks like this bug 2059847 is not fully & correctly
fixed.

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

[Desktop-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds

[Ghadi Rahme]

** Changed in: ppa-purge (Ubuntu Mantic)
   Status: In Progress => Fix Released

** Changed in: ppa-purge (Ubuntu Mantic)
   Status: Fix Released => Fix Committed

** Changed in: ppa-purge (Ubuntu Noble)
   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/2036761

Title:
  [mantic] ppa-purge no longer purges what add-apt-repository adds

Status in ppa-purge package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Confirmed
Status in ppa-purge source package in Mantic:
  Fix Committed
Status in software-properties source package in Mantic:
  Confirmed
Status in ppa-purge source package in Noble:
  Fix Released
Status in software-properties source package in Noble:
  Confirmed

Bug description:
  Thank you @jbicha for the original bug report!

  [ Impact ]

  Currently ppa-purge fails to purge packages on distribution using the deb822 
source format. Currently mantic and noble make use of this format and are 
affected by this issue.
  When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the 
custom PPA since it cannot disable deb822 sources and leads to apt still 
querying the ppa when running:

  $ apt update

  In older versions of ubuntu, PPAs used the ".list" format which could be 
disabled by simply commenting out the "deb" line with a "#". This was the 
method that ppa-purge used to disable PPAs.
  This new patch allows ppa-purge to detect and disable deb822 source files by 
adding an "Enabled: no" field in each component section of the deb822 file. It 
also removes any line that starts with "Enabled:"
  to make sure the resulting file is clean.

  [ Test Plan ]

  The changes were tested on both mantic and noble in a lxc container using the 
oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) 
as the test PPA.
  The following steps were recorded in a noble lxc container.

   - First make sure that mesa-utils is installed in your environment:
  $ sudo apt update && sudo apt install mesa-utils

   - Add the oibaf PPA to your system using the following command:
  $ sudo add-apt-repository ppa:oibaf/graphics-drivers

   - Make sure that the mesa-utils packages were upgraded after adding the PPA:
  $ sudo apt update && sudo apt upgrade
  $ dpkg - l | grep mesa

   - output should be similar to the following:

  ii  libegl-mesa0:amd64  24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the EGL API -- Mesa vendor library
  ii  libgl1-mesa-dri:amd64   24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the OpenGL API -- DRI modules
  ii  libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the GL API -- shared library
  ii  libglx-mesa0:amd64  24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the OpenGL API -- GLX vendor library
  ii  mesa-utils  9.0.0-2   
  amd64Miscellaneous Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd649.0.0-2   
  amd64Miscellaneous Mesa utilities -- native applications
  ii  mesa-vulkan-drivers:amd64   24.1~git2402280600.41722c~oibaf~n 
  amd64Mesa Vulkan graphics drivers


   - Install and run ppa-purge:
  $ sudo apt install ppa-purge
  $ sudo ppa-purge ppa:oibaf/graphics-drivers

   - ppa-purge will report at the end that none of the oibaf packages
  need to be downgraded/removed:

  
  libglapi-mesa is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  libglapi-mesa set to manually installed.
  libglx-mesa0 is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  libglx-mesa0 set to manually installed.
  mesa-vulkan-drivers is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  mesa-vulkan-drivers set to manually installed.
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-radeon1'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Op

[Desktop-packages] [Bug 2060534] [NEW] Thunderbird disk usage out of control

[luca moscato]

Public bug reported:

Environment: Thunderbird 124.0 64bits installed as SNAP on Ubuntu 22.04 LTS
3 gmail imap account

This (monday) morning Ubuntu notify me that I was running out of disk
space, and while I was checking where the problem was, the disk analyzer
told me the answer

snap/thunderbird/common directory has a size of more than 360GB, pretty strange 
since my gmail account have 15GB and 30GB of quota (half used more or less)
One of them is a shared one we use for notfication with almost 100k emails, 
flow is very high since with my team we receive emails, handle and archive them.

I tryed to compact database, keep on disk only latest 90 days email but
the sistem started to suffer issues due to no disk space so that I tried
to remove that account and instantly more than 250GB of data on disk
disappeared.

Issue found and fixed but:
- Thunderbird should NOT use so much disk space, some cleanup process MUST be 
implemented to keep disk usage under control, as I wrote system usage is 
impaired
- Is this issue index-related? Since I do a lot of quick search on that account
- Is something snap/linux related? Could be found also on Windows/Mac?
- If someone needs logs, I'd be happy to provide them but I need instructions 
about how to retrieve them.

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

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

Title:
  Thunderbird disk usage out of control

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Environment: Thunderbird 124.0 64bits installed as SNAP on Ubuntu 22.04 LTS
  3 gmail imap account

  This (monday) morning Ubuntu notify me that I was running out of disk
  space, and while I was checking where the problem was, the disk
  analyzer told me the answer

  snap/thunderbird/common directory has a size of more than 360GB, pretty 
strange since my gmail account have 15GB and 30GB of quota (half used more or 
less)
  One of them is a shared one we use for notfication with almost 100k emails, 
flow is very high since with my team we receive emails, handle and archive them.

  I tryed to compact database, keep on disk only latest 90 days email
  but the sistem started to suffer issues due to no disk space so that I
  tried to remove that account and instantly more than 250GB of data on
  disk disappeared.

  Issue found and fixed but:
  - Thunderbird should NOT use so much disk space, some cleanup process MUST be 
implemented to keep disk usage under control, as I wrote system usage is 
impaired
  - Is this issue index-related? Since I do a lot of quick search on that 
account
  - Is something snap/linux related? Could be found also on Windows/Mac?
  - If someone needs logs, I'd be happy to provide them but I need instructions 
about how to retrieve them.

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


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

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

[Tim Richardson]

for what it's worth, JetBrains bug reports find that the problem is
triggered by requesting grayscale anti-aliasing.

https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window

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

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

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

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


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

[Desktop-packages] [Bug 2060458] [NEW] ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap

[Talha Can Havadar]

Public bug reported:

Hello,

I see the following messages keeps being logged in /var/log/syslog:
```
Apr  8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:04:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:04:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:05:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:05:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:06:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:06:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:07:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:07:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:08:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:08:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:09:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:09:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:10:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:10:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:11:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:11:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:12:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:12:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:13:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:13:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
Apr  8 10:14:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
Apr  8 10:14:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
```

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7.22.04.4
ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136
Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/mmcblk1p1)
Date: Mon Apr  8 10:15:18 2024
ProcEnviron:
 TERM=vt220
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2023-09-20T10:06:31

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


** Tags: apport-bug arm64 arm64-image jammy third-party-packages uec-images

** Summary changed:

- ARMSOC(0): flip queue failed: Invalid argument
+ ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap

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

Title:
  ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Hello,

  I see the following messages keeps being logged in /var/log/syslog:
  ```
  Apr  8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip 
queue failed: Invalid argument
  Apr  8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] 
DRI2SwapBuffers: driver failed to schedule swap
  

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

[Daniel van Vugt]

And here's the debdiff for mantic.

** Patch added: "mutter_45.2-0ubuntu5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2059847/+attachment/5762119/+files/mutter_45.2-0ubuntu5.debdiff

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

[Desktop-packages] [Bug 2060396] Re: reconnaitre le scanner

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 2060396

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Please note that you didn't even tell us which release of Ubuntu you are
using. Running the 'apport-collect' command will now tell us that.

** Description changed:

  si je lance libreoffice ou gimp par l'icone il ne reconnait pas le
  scanner. si je lance les applications par le terminal Libreoffice et
  gimp reconnaissent le scanners
+ 
+ Google translates as:
+ if I launch libreoffice or gimp using the icon it does not recognize the 
scanner. if I launch the applications through the Libreoffice terminal and gimp 
recognize the scanners

** Summary changed:

- reconnaitre le scanner
+ reconnaitre le scanner (recognize the scanner)

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

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

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

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

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

Title:
  reconnaitre le scanner (recognize the scanner)

Status in gimp package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  si je lance libreoffice ou gimp par l'icone il ne reconnait pas le
  scanner. si je lance les applications par le terminal Libreoffice et
  gimp reconnaissent le scanners

  Google translates as:
  if I launch libreoffice or gimp using the icon it does not recognize the 
scanner. if I launch the applications through the Libreoffice terminal and gimp 
recognize the scanners

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


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

[Desktop-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds

[Ghadi Rahme]

Hello Norbert, thank you for your testing and results.

This issue is caused by the fact that Ubuntu server and Ubuntu desktop use 
different types of awk. Ubuntu server uses gawk (GNU awk) by default while 
Ubuntu desktop ships with mawk which has less features than gawk and does not 
have support for the -i argument hence the error "awk: not an option: -i".
If your workflow depends on ppa-purge I recommend installing gawk (apt install 
gawk) and this will fix the issue temporarily while I get a permanent fix for 
ppa-purge.

side note: I am not sure why there is a difference in the default awk
installed/used between Ubuntu desktop and server maybe it is an
oversight and should be labeled as a bug? or maybe there is another
reason that someone could  clarify? To my knowledge gawk is the default
version of awk on most linux distros and has all the features of mawk.

I will add gawk as a dependency to ppa-purge but I still believe that
someone should look into why different versions of awk are shipped
between server and desktop since this means shell scripts are not
compatible between server and desktop by default.

** Changed in: ppa-purge (Ubuntu Mantic)
   Status: Fix Committed => In Progress

** Changed in: ppa-purge (Ubuntu Noble)
   Status: Fix Released => In Progress

** Tags removed: verification-needed verification-needed-mantic
** Tags added: verification-failed verification-failed-mantic

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

Title:
  [mantic] ppa-purge no longer purges what add-apt-repository adds

Status in ppa-purge package in Ubuntu:
  In Progress
Status in software-properties package in Ubuntu:
  Confirmed
Status in ppa-purge source package in Mantic:
  In Progress
Status in software-properties source package in Mantic:
  Confirmed
Status in ppa-purge source package in Noble:
  In Progress
Status in software-properties source package in Noble:
  Confirmed

Bug description:
  Thank you @jbicha for the original bug report!

  [ Impact ]

  Currently ppa-purge fails to purge packages on distribution using the deb822 
source format. Currently mantic and noble make use of this format and are 
affected by this issue.
  When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the 
custom PPA since it cannot disable deb822 sources and leads to apt still 
querying the ppa when running:

  $ apt update

  In older versions of ubuntu, PPAs used the ".list" format which could be 
disabled by simply commenting out the "deb" line with a "#". This was the 
method that ppa-purge used to disable PPAs.
  This new patch allows ppa-purge to detect and disable deb822 source files by 
adding an "Enabled: no" field in each component section of the deb822 file. It 
also removes any line that starts with "Enabled:"
  to make sure the resulting file is clean.

  [ Test Plan ]

  The changes were tested on both mantic and noble in a lxc container using the 
oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) 
as the test PPA.
  The following steps were recorded in a noble lxc container.

   - First make sure that mesa-utils is installed in your environment:
  $ sudo apt update && sudo apt install mesa-utils

   - Add the oibaf PPA to your system using the following command:
  $ sudo add-apt-repository ppa:oibaf/graphics-drivers

   - Make sure that the mesa-utils packages were upgraded after adding the PPA:
  $ sudo apt update && sudo apt upgrade
  $ dpkg - l | grep mesa

   - output should be similar to the following:

  ii  libegl-mesa0:amd64  24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the EGL API -- Mesa vendor library
  ii  libgl1-mesa-dri:amd64   24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the OpenGL API -- DRI modules
  ii  libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the GL API -- shared library
  ii  libglx-mesa0:amd64  24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the OpenGL API -- GLX vendor library
  ii  mesa-utils  9.0.0-2   
  amd64Miscellaneous Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd649.0.0-2   
  amd64Miscellaneous Mesa utilities -- native applications
  ii  mesa-vulkan-drivers:amd64   24.1~git2402280600.41722c~oibaf~n 
  amd64Mesa Vulkan graphics drivers


   - Install and run ppa-purge:
  $ sudo apt install ppa-purge
  $ sudo ppa-purge ppa:oibaf/graphics-drivers

   - ppa-purge will report at the end that none of the oibaf packages
  need to be downgraded/removed:

  
  libglapi-mesa is already the newest version 
(24.1~git24022

[Desktop-packages] [Bug 2060396] [NEW] reconnaitre le scanner (recognize the scanner)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

si je lance libreoffice ou gimp par l'icone il ne reconnait pas le
scanner. si je lance les applications par le terminal Libreoffice et
gimp reconnaissent le scanners

Google translates as:
if I launch libreoffice or gimp using the icon it does not recognize the 
scanner. if I launch the applications through the Libreoffice terminal and gimp 
recognize the scanners

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


** Tags: bot-comment
-- 
reconnaitre le scanner (recognize the scanner)
https://bugs.launchpad.net/bugs/2060396
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libreoffice in Ubuntu.

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

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

[Daniel van Vugt]

Here's the debdiff for jammy.

** Patch added: "mutter_42.9-0ubuntu8.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2059847/+attachment/5762110/+files/mutter_42.9-0ubuntu8.debdiff

** Description changed:

  [ Impact ]
  
  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.
  
  [ Test Plan ]
  
  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Verify that input never froze for any perceptible period of time.
  4. Run: journalctl -b0 | grep MetaSyncRing
  5. Verify the above command does NOT show messages such as:
  
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling
  
  [ Where problems could occur ]
  
- Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the
- code being modified.
+ Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
+ being modified is only used with that driver.
  
  [ Original Description ]
  
  There is a noticeable delay in input while using the native terminal. I
  belive it was caused by a recent software update, as this issue is
  relatively new.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubs

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

[Daniel van Vugt]

** Changed in: mutter (Ubuntu Jammy)
   Status: Triaged => In Progress

** Changed in: mutter (Ubuntu Mantic)
   Status: Triaged => In Progress

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

[Desktop-packages] [Bug 2060094] Re: Packaging: Provide chromium

[Nathan Teodosio]

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Packaging: Provide chromium

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Debian provides the Chromium browser in the chromium package; we, in
  chromium-browser package.

  A package that depends on 'chromium' was autosynced. So this provides
  for it.

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


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

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

[Tais P. Hansen]

I can also confirm the lag is gone on my 22.04 laptop using X11 with
nvidia-driver-550 when using the PPA packages.

Thanks!

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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