[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Donn Ingle]

@sladyo - Thanks. I hope I manage all that! Should I do this, or wait
for some official 22.04 solution? Don't want to further snafu the whole
thing.

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Steffen]

@donn-ingle Did you enable jammy-proposed first?

See the following posts:

- #92 by vorlon
- #115 by taisph

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Donn Ingle]

@sldayo Can you help? This is what I get:


$ sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy-proposed
[sudo] password for donn: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package gir1.2-mutter-10 is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libmutter-10-0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Release 'jammy-proposed' for 'gir1.2-mutter-10' was not found
E: Release 'jammy-proposed' for 'libmutter-10-0' was not found


Anyone got instructions for dummies for me ? :D

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 513244] Re: "Split in volumes" option is grayed out

[Ken]

Still an issue in 23.04.

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

Title:
  "Split in volumes" option is grayed out

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind

[Bug Watch Updater]

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

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

Title:
  When clicking on some maximized or tiled windows, focus on roughly the
  lower quarter falls to the window behind

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 2065644] Re: Right click Rename file or folder freeze

[Jonathan Smith]

Hi Sebastien,

it freezes

at first i just logout

then i actually open process to kill the process

then i figure if i click on the location bar /home/Documents on the same 
window, it allows me to get back control

but i have to tap a few times which is still annoying and this is just 
to regain back control of the ui

i then went to settings touch-pad and disable the tap to click

i now have to push every time to execute an event in any part of the ui

but at least i don't run into that issue where it just freeze

i install ubuntu on a macbook pro 2012 13'


On 5/14/24 02:38, Sebastien Bacher wrote:
> Thank you for your bug report.So is the issue just the tapping not
> working as expected or is it really freezing, the description is a bit
> confusing
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Undecided => Low
>

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

Title:
  Right click Rename file or folder freeze

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065733] [NEW] Mouse cursor does not stay visible.

[Rich Perry]

Public bug reported:

# System Details Report
---

## Report details
- **Date generated:**  2024-05-14 16:11:26

## Hardware Information:
- **Hardware Model:**  ASUS TUF GAMING X570-PRO 
_WI-FI_
- **Memory:**  32.0 GiB
- **Processor:**   AMD Ryzen™ 9 5900X × 24
- **Graphics:**AMD Radeon™ RX 6900 XT
- **Disk Capacity:**   6.0 TB

## Software Information:
- **Firmware Version:**4408
- **OS Name:** Ubuntu 24.04 LTS
- **OS Build:**(null)
- **OS Type:** 64-bit
- **GNOME Version:**   46
- **Windowing System:**X11
- **Kernel Version:**  Linux 6.8.0-31-generic

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-session-bin 46.0-1ubuntu4
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Tue May 14 16:09:49 2024
InstallationDate: Installed on 2024-04-29 (15 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

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

Title:
  Mouse cursor does not stay visible.

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065726] [NEW] gimp crash

[Karel Hůlka]

Public bug reported:


```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Neoprávněný přístup do paměti (SIGSEGV)

Stack trace:
```

# Stack traces obtained from PID 10410 - Thread 10410 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 10581]
[New LWP 10555]
[New LWP 10540]
[New LWP 10532]
[New LWP 10516]
[New LWP 10495]
[New LWP 10494]
[New LWP 10493]
[New LWP 10423]
[New LWP 10422]
[New LWP 10421]
[New LWP 10420]
[New LWP 10419]
[New LWP 10418]
[New LWP 10417]
[New LWP 10416]
[New LWP 10415]
[New LWP 10414]
[New LWP 10413]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7644e8f1ba9a in __GI___libc_read (nbytes=256, buf=0x7fffb18ae330, fd=19) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x7644e84c3640 (LWP 10410) "gimp-2.10"  0x7644e8f1ba9a in 
__GI___libc_read (nbytes=256, buf=0x7fffb18ae330, fd=19) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7644a2a006c0 (LWP 10581) "swap writer"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7644a16006c0 (LWP 10555) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7644a0c006c0 (LWP 10540) "gimp-2.10"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7644a20006c0 (LWP 10532) "gimp-2.10"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7644a34006c0 (LWP 10516) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7644bb4006c0 (LWP 10495) "gdbus"  0x7644e8f1b4cd in 
__GI___poll (fds=0x7644900035e0, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7644baa006c0 (LWP 10494) "gmain"  0x7644e8f1b4cd in 
__GI___poll (fds=0x5a23de11cff0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x7644ba0006c0 (LWP 10493) "pool-spawner"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7644dcc006c0 (LWP 10423) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7644dd6006c0 (LWP 10422) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7644de0006c0 (LWP 10421) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7644dea006c0 (L

[Bug 2042844] Re: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
58-1build1

---
gnome-shell-extension-appindicator (58-1build1) oracular; urgency=medium

  * Rebuild for oracular

gnome-shell-extension-appindicator (58-1) unstable; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release to fully support GNOME 46
  * appIndicator: Try to introspect the application for Activate method support.
(LP: #2042844)
  * dbusMenu: Handle missing AboutToShow gracefully (LP: #2042844).
  * debian/patches: Drop applied upstream

  [ Peter Dave Hello ]
  * Add zh_TW Traditional Chinese locale

  [ Jing Wang ]
  * Fix first click being treated as both a single and double click
(LP: #2059819)

  [ Sergio Costas Rodriguez ]
  * Replace add_actor and remove_actor (LP: #2059818).

  [ Yevhen Popok ]
  * Add Ukrainian translation

  [ BlankParticle ]
  * Reset DBusItem Properties before applying new changes

 -- Jeremy Bícha   Tue, 14 May 2024 16:45:44 +0200

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  JS ERROR: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in
  AboutToShow

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
58-1build1

---
gnome-shell-extension-appindicator (58-1build1) oracular; urgency=medium

  * Rebuild for oracular

gnome-shell-extension-appindicator (58-1) unstable; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release to fully support GNOME 46
  * appIndicator: Try to introspect the application for Activate method support.
(LP: #2042844)
  * dbusMenu: Handle missing AboutToShow gracefully (LP: #2042844).
  * debian/patches: Drop applied upstream

  [ Peter Dave Hello ]
  * Add zh_TW Traditional Chinese locale

  [ Jing Wang ]
  * Fix first click being treated as both a single and double click
(LP: #2059819)

  [ Sergio Costas Rodriguez ]
  * Replace add_actor and remove_actor (LP: #2059818).

  [ Yevhen Popok ]
  * Add Ukrainian translation

  [ BlankParticle ]
  * Reset DBusItem Properties before applying new changes

 -- Jeremy Bícha   Tue, 14 May 2024 16:45:44 +0200

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: In Progress => Fix Released

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
58-1build1

---
gnome-shell-extension-appindicator (58-1build1) oracular; urgency=medium

  * Rebuild for oracular

gnome-shell-extension-appindicator (58-1) unstable; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release to fully support GNOME 46
  * appIndicator: Try to introspect the application for Activate method support.
(LP: #2042844)
  * dbusMenu: Handle missing AboutToShow gracefully (LP: #2042844).
  * debian/patches: Drop applied upstream

  [ Peter Dave Hello ]
  * Add zh_TW Traditional Chinese locale

  [ Jing Wang ]
  * Fix first click being treated as both a single and double click
(LP: #2059819)

  [ Sergio Costas Rodriguez ]
  * Replace add_actor and remove_actor (LP: #2059818).

  [ Yevhen Popok ]
  * Add Ukrainian translation

  [ BlankParticle ]
  * Reset DBusItem Properties before applying new changes

 -- Jeremy Bícha   Tue, 14 May 2024 16:45:44 +0200

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: New => Fix Released

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064736] Re: gnome crashes

[Brett Holman]

Will do once I return.

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

Title:
  gnome crashes

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1961508] Re: Dock displaying over window after resuming from blank screen

[popov895]

> I submitted a patch to mutter that should fix this problem:
> https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3601

Interesting, if this patch really fixes this issue, can it be backported
to Ubuntu 22.04?

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

Title:
  Dock displaying over window after resuming from blank screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065382] Re: Screen flashing when hoovering over menus

[Daniel van Vugt]

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

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

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

Title:
  Screen flashing when hoovering over menus

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065432] Re: Unable to authenticate with smartcard: gnome-shell throws on unhandled promise rejection

[Daniel van Vugt]

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

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

Title:
  Unable to authenticate with smartcard: gnome-shell throws on unhandled
  promise rejection

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)

[Daniel van Vugt]

24.04 will get the fix automatically as part of the mutter 46.1 update.

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

Title:
  GNOME Wayland session crashes with
  
libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
  assertion failed: (logical_monitor)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065398] Re: Syslog filled with many "Window manager warning: Property WM_NAME on window 0xXXXXXXX contained invalid UTF-8"

[Daniel van Vugt]

** Tags added: logspam

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

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

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

Title:
  Syslog filled with many "Window manager warning: Property WM_NAME on
  window 0xXXX contained invalid UTF-8"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065695] Re: GNOME Shell crashed with signal 11 on drag and drop panel

[Julian Briggs]

root@ssfdt0:/var/crash# ll _usr_bin_gnome-shell.1000*
-rw-r- 1 ph1jb whoopsie 57293630 May 14 14:37 
_usr_bin_gnome-shell.1000.crash
-rw-r--r-- 1 ph1jb whoopsie 0 May 14 14:37 _usr_bin_gnome-shell.1000.upload
-rw--- 1 whoopsie whoopsie 37 May 14 14:37 
_usr_bin_gnome-shell.1000.uploaded
root@ssfdt0:/var/crash# cat _usr_bin_gnome-shell.1000.uploaded
1daf1616-11f7-11ef-9df5-fa163ec44ecd
root@ssfdt0:/var/crash#

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

Title:
  GNOME Shell crashed with signal 11 on drag and drop panel

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065489] Re: Gnome terminal slow problem returns after update to latest mutter

[Daniel van Vugt]

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

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


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

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

Title:
  Gnome terminal slow problem returns after update to latest mutter

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)

[Dalyn Dalton]

Hoping this gets backported to 24.04 LTS as well, affecting several of
our members on a daily basis

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

Title:
  GNOME Wayland session crashes with
  
libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
  assertion failed: (logical_monitor)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'

[Daniel van Vugt]

Note to self: Check if bug 2065587 is related.

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

Title:
  gnome-shell crashed with signal 5:  Settings schema
  'org.gnome.mutter.wayland' does not contain a key named 'xwayland-
  allow-byte-swapped-clients'

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065695] Re: GNOME Shell crashed with signal 11 on drag and drop panel

[Daniel van Vugt]

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

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

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

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

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

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

Title:
  GNOME Shell crashed with signal 11 on drag and drop panel

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065524] Re: DMAR: DRHD error with black screen while wake from sleep mode

[Daniel van Vugt]

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

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

Title:
  DMAR: DRHD error with black screen while wake from sleep mode

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Antoine L]

Ok, thanks for the thorough answer @egmont-gmail.
I fixed the issue for now as stated in my last comment though, so I'm gonna 
stay on 22.04 if it stays fixed.

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065695] [NEW] GNOME Shell crashed with signal 11 on drag and drop panel

[Julian Briggs]

Public bug reported:

GNOME Shell crashed with signal 11

I use Eclipse IDE
gnome-shell crashes
1. when I drag and drop a panel
2. when I click a link in a pop-up

May 12 09:05:49 ssfdt0 gnome-shell[2628]: Window manager warning: Ping serial 
11101399 was reused for window 0x22000f4, previous use was for window 0x22000ac.
May 12 10:08:44 ssfdt0 gnome-shell[2628]: GNOME Shell crashed with signal 11
May 12 10:08:44 ssfdt0 gnome-shell[2628]: == Stack trace for context 
0x5f09d93378c0 ==
May 12 10:08:44 ssfdt0 gnome-shell[2628]: #0   5f09d9403208 i   
resource:///org/gnome/shell/ui/init.js:21 (247195570bf0 @ 48)
May 12 10:10:06 ssfdt0 gnome-shell[3409]: (EE) failed to read Wayland events: 
Broken pipe

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

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

Title:
  GNOME Shell crashed with signal 11 on drag and drop panel

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064696] Re: gnome-shell crash

[Daniel van Vugt]

Julian, please open a new bug for that.

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

Title:
  gnome-shell crash

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065582] Re: there is no way to disable the onscreen keyboard

[Daniel van Vugt]

** Tags added: osk

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

Title:
  there is no way to disable the onscreen keyboard

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]

[Daniel van Vugt]

HDR might be relevant but I'm not sure what the status of HDR support
is.

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4
  [drmModeAtomicCommit: Invalid argument]

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)

[Joe Auge]

By activating the proposed repository I did not get any updates for
gimp. So i installed it via

sudo apt install gimp/noble-proposed

And I can confirm, that the patch works. No more crashes while closing
Gimp. Before I had them all the time.

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

Title:
  GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Egmont Koblinger]

> @egmont-gmail For users on 22.04, would you suggest upgrading to 24.04 as 
> well ?
> Is this something you would recommend or are there some important pitfalls to 
> know about beforehand ?

@toniopelo I cannot make a generic recommendation. It depends on your
circumstances, priorities, short-term goals, long-term goals, etc.

If, apart from this very issue, you're super happy with 22.04 and don't
plan to upgrade for many-many years, potentially jumping straight to
26.04 or 28.04, then I'd recommend to stay on 22.04, find a workaround
or wait patiently until the fix is properly released.

If you'd upgrade to 24.04 anyway, maybe in the following months, then
upgrading right now (and getting rid of this issue once and for all)
might not be a bad idea.

> I guess the right upgrade path would be to upgrade to 23.10 first and
then to 24.04.

As far as I know, it's either through all the releases (22.04 -> 22.10
-> 23.04 -> 23.10 -> 24.04) which is no longer possible as 22.10 and
23.04 have already EOL'ed; or from LTS to LTS, i.e. 22.04 -> 24.04. I
don't think other types of dist-upgrades are supported. I might be
wrong, though.

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064696] Re: gnome-shell crash

[Julian Briggs]

root@ssfdt0:/var/crash# ll _usr_bin_gnome-shell.1000*
-rw-r- 1 ph1jbwhoopsie 57293630 May 14 14:37 
_usr_bin_gnome-shell.1000.crash
-rw-r--r-- 1 ph1jbwhoopsie0 May 14 14:37 
_usr_bin_gnome-shell.1000.upload
-rw--- 1 whoopsie whoopsie   37 May 14 14:37 
_usr_bin_gnome-shell.1000.uploaded
root@ssfdt0:/var/crash# cat _usr_bin_gnome-shell.1000.uploaded
1daf1616-11f7-11ef-9df5-fa163ec44ecd
root@ssfdt0:/var/crash#

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

Title:
  gnome-shell crash

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 2064696] Re: gnome-shell crash

[Julian Briggs]

Hi Daniel,

root@ssfdt0:/var/crash# ll _usr_bin_gnome-shell.1000*
-rw-r- 1 ph1jb    whoopsie 57293630 May 14 14:37 
_usr_bin_gnome-shell.1000.crash
-rw-r--r-- 1 ph1jb    whoopsie    0 May 14 14:37 
_usr_bin_gnome-shell.1000.upload
-rw--- 1 whoopsie whoopsie   37 May 14 14:37 
_usr_bin_gnome-shell.1000.uploaded
root@ssfdt0:/var/crash# cat _usr_bin_gnome-shell.1000.uploaded
1daf1616-11f7-11ef-9df5-fa163ec44ecd
root@ssfdt0:/var/crash#

Kind Regards
Julian


On 14/05/2024 13:35, Daniel van Vugt wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It sounds like some part of the system has crashed. To
> help us find the cause of the crash please follow these steps:
>
> 1. Run these commands:
>  journalctl -b0 > journal.txt
>  journalctl -b-1 > prevjournal.txt
> and attach the resulting text files here.
>
> 2. Look in /var/crash for crash files and if found run:
>  ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
>
> ** Changed in: gnome-shell (Ubuntu)
> Status: Confirmed => Incomplete
>
-- 
Julian Briggs

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

Title:
  gnome-shell crash

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]

[Ge-org Brohammer]

It's a vanilla install, I haven't setup any custom colour profiles or
even enabled night light. I will keep using the setting thank you. Was
just hoping to help improve hardware support for new installs.  Both
screens are 4k HDR capable though.  Not sure if that plays a part.

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4
  [drmModeAtomicCommit: Invalid argument]

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065587] Re: Add explicit dependency on glib 2.80 to ease upgrades 22.04 → 24.04

[Daniel van Vugt]

Can we have more details about this bug? Is it related to bug 2054761?

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

Title:
  Add explicit dependency on glib 2.80 to ease upgrades 22.04 → 24.04

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065632] Re: gnome-shell crashes when attaching external monitors with assertion 'logical_monitor != NULL' failed

[Daniel van Vugt]

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

The 'logical_monitor != NULL' assertions precede the crash, but bug
2050865 shows that's not the crashing assertion. Let's treat this as a
duplicate of bug 2050865.

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

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

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

** This bug has been marked a duplicate of bug 2050865
   GNOME Wayland session crashes with 
libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
 assertion failed: (logical_monitor)

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

Title:
  gnome-shell crashes when attaching external monitors with assertion
  'logical_monitor != NULL' failed

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754687] Re: gnome-shell crashes with meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed

[Daniel van Vugt]

Since this bug was fixed a few years ago, let's keep the new issue in
bug 2065632.

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

Title:
  gnome-shell crashes with
  meta_monitor_manager_get_logical_monitor_from_number: assertion
  '(unsigned int) number < g_list_length (manager->logical_monitors)'
  failed

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[John Johansen]

Yes for the appimages that are affected they should be reported
upstream. There are some things that upstream can do to make appimages
work under the restriction, ideally they would do it dynamically based
on whether the user namespace is available than just based on distro
which is the quick fix some have done.

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065646] Re: 1- Snap grid bug 2- file manager always shows "1"

[Daniel van Vugt]

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

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

Title:
  1- Snap grid bug 2- file manager always shows "1"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065681] Re: my x11 working slowly, so slow and bugged

[Daniel van Vugt]

If you run 'top' then what process is using the most CPU time?

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

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

Title:
  my x11 working slowly, so slow and bugged

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Antoine L]

@sldayo OMG, you got it right!
Finally this is fixed on my machine, thanks, A LOT.

Apparently it was upgrading mutter to the jammy-proposed version explicitly 
that caused the dependency removing mess, so your command works fine and only 
upgrade the necessary packages.
I can confirm, after a reboot everything is fine and no results from `sudo 
journalctl -b0 | grep MetaSyncRing`

So the right command to install the jammy-proposed fix is this one from
@sldayo (comment #127) :

`sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy-
proposed`

Then reboot and it works fine :).

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065024] Re: gnome-shell random error

[Daniel van Vugt]

Thanks for the bug report. Please try disabling all of these extensions:

'dim-on-batt...@nailfarmer.nailfarmer.com',
'paneln...@gittymac.github.io',
'unbl...@sun.wxg@gmail.com',
'bluetooth-battery-me...@maniacx.github.com'

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

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

Title:
  gnome-shell random error

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064977] Re: new gnome-terminal instances launched from nautilus fail to receive automatic focus

[Daniel van Vugt]

** Tags added: fcosu

** Tags removed: fcosu
** Tags added: focus

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

Title:
  new gnome-terminal instances launched from nautilus fail to receive
  automatic focus

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064709] Re: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

[Daniel van Vugt]

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

I've reopened bug 1871262 to track this.

** Summary changed:

- Error every time Nautilus is launched
+ meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 
0' failed

** This bug has been marked a duplicate of bug 1871262
   meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 
0' failed

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

Title:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064736] Re: gnome crashes

[Daniel van Vugt]

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

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

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

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

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


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

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

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

Title:
  gnome crashes

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1871262] Re: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Status: Won't Fix => Confirmed

** Tags added: noble

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

Title:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064698] Re: Several errors in gnome-shell and extesions

[Daniel van Vugt]

Please choose one error message for this bug to be about.

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

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

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

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

Title:
  Several errors in gnome-shell and extesions

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[GTBS, LLC]

I do not want to reinstall Ubuntu 22.04.4 just 3 months before I install
Ubuntu 24.04.1  Too much work.

OK. I bit the bullet (and it turned out to be not-that-painful).  From
the Jammy Proposed PPA, I installed:

 sudo apt install libmutter-10-0=42.9-0ubuntu8  
 sudo apt install gir1.2-mutter-10=42.9-0ubuntu8

and autoremoved everything it proposed.

I then rebooted normally, and was presented with a console terminal
screen (autoremove had removed gnome-shell, gdm, and a bunch of other
things).  How 1980s!

I then installed

 sudo apt install ubuntu-desktop

and  rebooted normally.

Everything seems to have returned AND no results from sudo journalctl
-b0 | grep MetaSyncRing

Hope this helps others.  :-)  Thanks Daniel for taking this seriously.

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064696] Re: gnome-shell crash

[Daniel van Vugt]

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

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

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

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

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


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

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

Title:
  gnome-shell crash

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Daniel van Vugt]

For 24.04, please see bug 2026194 and bug 2063831.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064540] Re: Very laggy after latest update/upgrade

[Daniel van Vugt]

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

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


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

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

Title:
  Very laggy after latest update/upgrade

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064559] Re: Screen clicks not working when app page maximised

[Daniel van Vugt]

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

I think this would be better tracked in the newer bug 2026194 (or bug
2063831)

** Tags added: noble

** This bug is no longer a duplicate of bug 1181666
   gnome-shell randomly blocks mouse clicks from working in app windows

** This bug has been marked a duplicate of bug 2026194
   When clicking on some maximized or tiled windows, focus on roughly the lower 
quarter falls to the window behind

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

Title:
  Screen clicks not working when app page maximised

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Pirouette Cacahuète]

Yep, this is fine. I just wanted to make it clear for others, because
one of the comment above might be misleading and even though I know the
area of the code impacted by userns, I was actually thinking you got a
fix landed on AppArmor side to avoid the need for a dedicated profile.

AppImage being impacted might also be good to report to those upstream?

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065681] [NEW] my x11 working slowly, so slow and bugged

[Morgan]

Public bug reported:

i feel like im in 2000 computer, i have good specs but i feel so weird
when x11 is not optimized

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May 14 13:53:34 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-05-14 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=pl_PL.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

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

Title:
  my x11 working slowly, so slow and bugged

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]

[Daniel van Vugt]

Thanks. For each "KMS update failed: drmModeAtomicCommit: Invalid
argument", the only unusual things I can see are:

KMS: [atomic] Setting CRTC (83, /dev/dri/card1) gamma, size: 4096
KMS: [atomic] Setting CRTC 83 (/dev/dri/card1) property 'GAMMA_LUT' (28) to 161

which means either Night Light or a custom colour profile is enabled on
the AMD GPU.

This is a problem I've seen before in bug 1968040 but the same "Invalid
argument" can have multiple causes and "gamma" is just one that I've
seen.

Since we can't reproduce the issue in development at the moment, and
therefore can't debug it, I suggest sticking to the workaround:

  MUTTER_DEBUG_FORCE_KMS_MODE=simple

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4
  [drmModeAtomicCommit: Invalid argument]

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065524] ProcCpuinfoMinimal.txt

[shun wang]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2065524/+attachment/5778287/+files/ProcCpuinfoMinimal.txt

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

Title:
  DMAR: DRHD error with black screen while wake from sleep mode

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065524] Re: DMAR: DRHD error with black screen while wake from sleep mode

[shun wang]

apport information

** Tags added: apport-collected noble wayland-session

** Description changed:

  It happens all the time on my Alienware x14 laptop, every time while
  wake form sleep mode the screen always goes black and all the keys don't
  work. I could only solve it by force shutting down and restarting with
  the power button. I've tried
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040  solutions
  but none of them worked, so I suspect this is a different problem. I
  have attached the relevant logs, the approximate time is around
  20:44-20:45.
  
  ```
  Alienware Alienware x14
  Ubuntu 24.04 LTS
  12th Gen Intel® Core™ i7-12700H × 20
  Intel® Graphics (ADL GT2)
  NV177 NVIDIA Graphics
  Wayland
  ```
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.28.1-0ubuntu3
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 24.04
+ InstallationDate: Installed on 2024-04-27 (17 days ago)
+ InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
+ Package: mutter 46.0-1ubuntu9
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANG=zh_CN.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+ ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
+ Tags: noble wayland-session
+ Uname: Linux 6.8.0-31-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sudo users
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2065524/+attachment/5778286/+files/Dependencies.txt

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

Title:
  DMAR: DRHD error with black screen while wake from sleep mode

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Steffen]

@toniopelo I don't know about others but I'm inclined toward waiting for
Ubuntu 24.04.1 because of my personal experience. I was eager to upgrade
to Ubuntu 24.04 for unrelated reasons but reverted to Ubuntu 22.04.4 due
to experiencing display/GPU issues that I didn't have before.

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs

[David]

I don't use autologin.

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

Title:
  Window borders and shadows missing from GTK3 dialogs

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Antoine L]

@egmont-gmail For users on 22.04, would you suggest upgrading to 24.04 as well ?
I guess the right upgrade path would be to upgrade to 23.10 first and then to 
24.04.
Is this something you would recommend or are there some important pitfalls to 
know about beforehand ?

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Steffen]

In order to avoid removing vital packages when installing the proposed
package(s) on Ubuntu 22.04, I installed the following packages together:

sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy-
proposed

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064192] Re: Unable to resize windows

[David]

I don't use Autologin and have the same problem

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

Title:
  Unable to resize windows

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065670] Re: Everytime I close GIMP, I get a crash report

[Paul White]

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

** This bug has been marked a duplicate of bug 2055044
   GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)

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

Title:
  Everytime I close GIMP, I get a crash report

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Donn Ingle]

I don't understand how to re-fix this on 22.04 after the original PPA
fix — any instructions?

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065674] [NEW] GIMP crashed with a fatal error: fatal error: Minnesegmentsfeil

[Alexander Vinbæk Strand]

Public bug reported:




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Minnesegmentsfeil

Stack trace:
```

# Stack traces obtained from PID 14282 - Thread 14282 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 14468]
[New LWP 14310]
[New LWP 14307]
[New LWP 14303]
[New LWP 14302]
[New LWP 14301]
[New LWP 14300]
[New LWP 14299]
[New LWP 14298]
[New LWP 14297]
[New LWP 14296]
[New LWP 14295]
[New LWP 14294]
[New LWP 14293]
[New LWP 14292]
[New LWP 14291]
[New LWP 14290]
[New LWP 14289]
[New LWP 14288]
[New LWP 14287]
[New LWP 14286]
[New LWP 14285]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7241b291ba9a in __GI___libc_read (nbytes=256, buf=0x7fff70cffcb0, fd=18) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7241b2082640 (LWP 14282) "gimp-2.10"0x7241b291ba9a in 
__GI___libc_read (nbytes=256, buf=0x7fff70cffcb0, fd=18) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x724197e006c0 (LWP 14468) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7241896006c0 (LWP 14310) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x72418aa006c0 (LWP 14307) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x72419cc006c0 (LWP 14303) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x72419d6006c0 (LWP 14302) "gdbus"0x7241b291b4cd in 
__GI___poll (fds=0x72413c000b90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x72419e0006c0 (LWP 14301) "gmain"0x7241b291b4cd in 
__GI___poll (fds=0x5d3b68d0cdc0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x72419ea006c0 (LWP 14300) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x72419f4006c0 (LWP 14299) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x72419fe006c0 (LWP 14298) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7241a50006c0 (LWP 14297) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7241a5a006c0 (LWP 14296) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7241a64006c0 

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Egmont Koblinger]

> The only thing that has worked for me is listed below
> 1. Reinstall Ubuntu LTS 22.04.4 without any upgrade or just don't connect it 
> to the internet.

To anyone who considers reinstalling the OS due to this issue (because
you messed up your system beyond repair, or whatever): Why not go for
24.04? This very issue is fixed there properly, and you save yourself
from a future upgrade. (Yes I know for LTS guys it's usually recommended
to wait for the .1 subrelease, but given the severity of this issue,
dist-upgrading right now might be a viable option to consider.)

To anyone on 23.10 which will EOL in 2 months anyway: Why not dist-
upgrade now?

Just my 2 cents. (I'm not trying to defend Ubuntu in this badly messed
up situation; I'm just trying to bring yet another possible solution to
its users' attention.)

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Daniel van Vugt]

You're talking about bug 2059847, not this one.

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

Title:
  Incomplete screen redraws in virtual machines running Xorg

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Daniel van Vugt]

In progress: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind

[Daniel van Vugt]

In progress:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3720

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

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

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

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

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

Title:
  When clicking on some maximized or tiled windows, focus on roughly the
  lower quarter falls to the window behind

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2063831] Re: Clicking on bottom half of applications switches to background application

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 2026194
   When clicking on some maximized or tiled windows, focus on roughly the lower 
quarter falls to the window behind

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

Title:
  Clicking on bottom half of applications switches to background
  application

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2065670] [NEW] Everytime I close GIMP, I get a crash report

[Joe Auge]

Public bug reported:

To me it does not seem to crash. It just closes as expected. But then I get 
this CHras Report. Every single time. 
:~$ apt info gimp
Package: gimp
Version: 2.10.36-3build3 ← this is the version I am reporting here. 

:~$ snap list gimp
Name  Version  Revision  TrackingHerausgeberHinweise
gimp  2.99.18  433   preview/stable  snapcrafters✪  deaktiviert





```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Speicherzugriffsfehler

Stack trace:
```

# Stack traces obtained from PID 100534 - Thread 100534 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 100634]
[New LWP 100590]
[New LWP 100583]
[New LWP 100560]
[New LWP 100552]
[New LWP 100551]
[New LWP 100550]
[New LWP 100542]
[New LWP 100541]
[New LWP 100540]
[New LWP 100539]
[New LWP 100538]
[New LWP 100537]
[New LWP 100536]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7c1f17b1ba9a in __GI___libc_read (nbytes=256, buf=0x7ffe120e8f30, fd=19) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id Frame 
* 1Thread 0x7c1f17172640 (LWP 100534) "gimp-2.10"0x7c1f17b1ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffe120e8f30, fd=19) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7c1ee2a006c0 (LWP 100634) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7c1e9fe006c0 (LWP 100590) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7c1ee16006c0 (LWP 100583) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7c1ee34006c0 (LWP 100560) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7c1efb4006c0 (LWP 100552) "gdbus"0x7c1f17b1b4cd in 
__GI___poll (fds=0x7c1ed8009470, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7c1efaa006c0 (LWP 100551) "gmain"0x7c1f17b1b4cd in 
__GI___poll (fds=0x5fff3a339060, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7c1efa0006c0 (LWP 100550) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7c1f0e0006c0 (LWP 100542) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7c1f0ea006c0 (LWP 100541) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/sy

[Bug 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)

[Daniel van Vugt]

This bug is closed, but please see bug 2063869 instead.

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

Title:
  GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white
  square (missing adwaita-icon-theme-full)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"

[Daniel van Vugt]

** Tags added: noble

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

Title:
  Nvidia Wayland sessions sometimes flood the log with
  "clutter_frame_clock_notify_presented: code should not be reached"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Daniel van Vugt]

Sorry for the delay and confusion. I was away for most of the last two
weeks.

It looks like a few things happened:

1. The security team inserted an update which took precedence over the
PPA. This is normal and correct. Just unlucky timing that I was away at
the same time AND the debdiff in comment #42 didn't get attention for a
month (also because much of the team are travelling).

2. Some people had packages automatically removed. I'm not sure what
caused this, it might have been the PPA or more likely might have been
all the manual hacking that's gone on here. And rightfully so -- it was
a bit of an emergency bug. But I've just tested upgrades to
42.9-0ubuntu8 in a fresh VM and cannot reproduce any upgrade issues. It
might be a good idea if everyone just purges the PPA and manually
installs the 42.9-0ubuntu8 packages...

3. People mistakenly install/upgrade 'mutter'/'mutter-common' alone when
really it's 'libmutter-10-0' that provides the fix. E.g. comment #96.

Overall it looks like the fix is sound and jammy has been verified by
comments #98 and #99.




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

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2064696] Re: gnome-shell crash

[Julian Briggs]

I use Eclipse IDE
gnome-shell crashes
1. when I drag and drop a panel
2. when I click a link in a pop-up 

May 12 09:05:49 ssfdt0 gnome-shell[2628]: Window manager warning: Ping serial 
11101399 was reused for window 0x22000f4, previous use was for window 0x22000ac.
May 12 10:08:44 ssfdt0 gnome-shell[2628]: GNOME Shell crashed with signal 11
May 12 10:08:44 ssfdt0 gnome-shell[2628]: == Stack trace for context 
0x5f09d93378c0 ==
May 12 10:08:44 ssfdt0 gnome-shell[2628]: #0   5f09d9403208 i   
resource:///org/gnome/shell/ui/init.js:21 (247195570bf0 @ 48)
May 12 10:10:06 ssfdt0 gnome-shell[3409]: (EE) failed to read Wayland events: 
Broken pipe
May 12 10:10:37 ssfdt0 gnome-shell[22862]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).

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

Title:
  gnome-shell crash

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'

[Daniel van Vugt]

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

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

Title:
  gnome-shell crashed with signal 5:  Settings schema
  'org.gnome.mutter.wayland' does not contain a key named 'xwayland-
  allow-byte-swapped-clients'

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs