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

[caio tor]

Public bug reported:

Summary:
1- Snap grid bug 2- file manager always shows "1" 
Steps to Reproduce:
1. Log in to the Ubuntu desktop.
2. click on the title bar/window of an app

Expected Result:
The snap grid / snapping thing should only be triggered when really required 
and  when dragged to the end of the scree right or extreme left etc

Actual Result:
GNOME Shell has 2 issues: 1 the Nautilus icon on the pinned dock is always with 
the (1) number. and 2 whenever i click on a window, Gnome shell wants to resize 
it or use the snap grid tool. even when i don't want to 

Additional Information:
- Ubuntu version: 24.04 LTS
- GNOME Shell version: 46
- I am using the default Ubuntu login

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 01:07:51 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-04-27 (17 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=
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 wayland-session

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/2065646/+attachment/5778143/+files/syslog

-- 
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/+bug/2065646/+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"

[caio tor]

Here is how the file manager always shows (1) green colored, bug

** Attachment added: "Screenshot from 2024-05-14 01-14-03.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2065646/+attachment/5778149/+files/Screenshot%20from%202024-05-14%2001-14-03.png

-- 
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/+bug/2065646/+subscriptions


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

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

[Jonathan Smith]

It appears when you right click and the context menu appears, you can
not tap on the Rename item, you need to do a hard click, meaning, if you
have a system with touch-pad, like a laptop, and you are use to tapping
and not clicking on the touch-pad, it is actually 2 different functions
on the Ubuntu OS, or at least Ubuntu treats it that way since i was able
to `click` on the context menu item Rename and make it work versus the
first time when i was just tapping on the context item menu
Rename...this really sucks since you are used to tapping everywhere on
the ui but all of the sudden you start finding out that tapping does not
work everywhere.

-- 
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 2065645] [NEW] I can't open setting, and my gnome-control-center can't use.

[Xuefei Han]

Public bug reported:

When I use gnome-control-center, the terminal showed the bug is:
(gnome-control-center:16511): Clutter-WARNING **: 10:59:12.603: Whoever 
translated default:LTR did so wrongly.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 14 10:57:48 2024
InstallationDate: Installed on 2022-02-18 (815 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  I can't open setting, and my gnome-control-center can't use.

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


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

[Bug 2065644] [NEW] Right click Rename file or folder freeze

[Jonathan Smith]

Public bug reported:

Ubuntu 24.04
All Updates as of 2024-05-13
Open Files
Right click on a file
Select Rename from context menu
Does not popup or allow to rename file
Same with folder
F2 key does works though
but I want to use Right click if that is an option

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 13 22:48:45 2024
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2024-05-12 (1 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: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   44.1-1
 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

-- 
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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[John Johansen]

The AppArmor profile covers the packaged version and the standard
privileged install location. You are correct that it does not cover
running firefox from an unprivileged user writable location like $HOME.

For unprivileged user writable locations like $HOME/bin/ the user has to
deliberately make a privileged action like installing a profile for the
location of the application. This applies to the appimage version run
out of the users $HOME as well.

-- 
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 2065632] Re: gnome-shell crashes when attaching external monitors with assertion 'logical_monitor != NULL' failed

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell 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/ubuntu/+source/gnome-shell/+bug/2065632/+subscriptions


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

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

[Dalyn Dalton]

Public bug reported:

Attaching and then detaching a workstation from an external thunderbolt
dock causes the shell to crash.  The bug here is appears to be related
to the detachment, rather than the attachment.

This appears to be fixed upstream with
https://gitlab.gnome.org/GNOME/mutter/-/issues/3402, however the current
Ubuntu 24.04 does not contain the fix.

Release: Ubuntu 24.04 LTS
gnome-shell: 46.0-0ubuntu5.1

Expected: Machine maintains shell session between docking and un-docking
of external monitors

Reality: gnome-shell session crashes upon re-docking the workstation.

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

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/2065632/+attachment/5778069/+files/journal.txt

-- 
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/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/ubuntu/+source/gnome-shell/+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

[Dalyn Dalton]

It appears that this has been fixed in the upstream
https://gitlab.gnome.org/GNOME/mutter/-/issues/3402#note_2070469


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

-- 
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 2065624] Re: GIMP crashes when exiting

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

Title:
  GIMP crashes when exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2065624/+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

[Paulo Narciso]

Me also.

-- 
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 2065624] [NEW] GIMP crashes when exiting

[Chris Hermansen]

Public bug reported:

Closing GIMP after editing and overwriting a screen shot (PNG) results
in GIMP crashing and this:




```
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: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 12950 - Thread 12950 #


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 13044]
[New LWP 13028]
[New LWP 12992]
[New LWP 12976]
[New LWP 12973]
[New LWP 12970]
[New LWP 12969]
[New LWP 12968]
[New LWP 12967]
[New LWP 12966]
[New LWP 12965]
[New LWP 12964]
[New LWP 12963]
[New LWP 12962]
[New LWP 12961]
[New LWP 12960]
[New LWP 12959]
[New LWP 12958]
[New LWP 12957]
[New LWP 12956]
[New LWP 12955]
[New LWP 12954]
[New LWP 12953]
[New LWP 12952]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x75562f91ba9a in __GI___libc_read (nbytes=256, buf=0x7ffe943a8530, fd=18) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x75562ed3e640 (LWP 12950) "gimp-2.10"  0x75562f91ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffe943a8530, fd=18) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7555f9a006c0 (LWP 13044) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7555fae006c0 (LWP 13028) "paint"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x755604a006c0 (LWP 12992) "swap writer"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7555fa4006c0 (LWP 12976) "gimp-2.10"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7555fbe006c0 (LWP 12973) "gimp-2.10"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7556054006c0 (LWP 12970) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7556120006c0 (LWP 12969) "gdbus"  0x75562f91b4cd in 
__GI___poll (fds=0x7555cb90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x755612a006c0 (LWP 12968) "gmain"  0x75562f91b4cd in 
__GI___poll (fds=0x59a95e333b80, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  10   Thread 0x7556134006c0 (LWP 12967) "pool-spawner"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x75561cc006c0 (LWP 12966) "worker" syscall () at 

[Bug 2064682] Re: Gnome control center crash on launch with "undefined symbol: GST_CAT_DEFAULT"

[Daniel Elbirt]

Output below:
```
$ debsums libgstreamer1.0-0
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcoreelements.so OK
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcoretracers.so  OK
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner   OK
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-ptp-helper   OK
/usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0.2003.0  OK
/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2003.0 OK
/usr/lib/x86_64-linux-gnu/libgstcontroller-1.0.so.0.2003.0OK
/usr/lib/x86_64-linux-gnu/libgstnet-1.0.so.0.2003.0   OK
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2003.0OK
/usr/share/doc/libgstreamer1.0-0/changelog.Debian.gz  OK
/usr/share/doc/libgstreamer1.0-0/copyrightOK
```

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

Title:
  Gnome control center crash on launch with "undefined symbol:
  GST_CAT_DEFAULT"

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


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

[Bug 2065621] Re: always happens, when I turn if off.

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

Title:
  always happens, when I turn if off.

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


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

[Bug 2065621] [NEW] always happens, when I turn if off.

[Bo]

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

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: Segmentfejl

Stack trace:
```

# Stack traces obtained from PID 3735 - Thread 3735 #


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 3784]
[New LWP 3756]
[New LWP 3753]
[New LWP 3750]
[New LWP 3749]
[New LWP 3748]
[New LWP 3747]
[New LWP 3746]
[New LWP 3745]
[New LWP 3744]
[New LWP 3743]
[New LWP 3742]
[New LWP 3741]
[New LWP 3740]
[New LWP 3739]
[New LWP 3738]
[New LWP 3737]
[New LWP 3736]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7db99a11ba9a in __GI___libc_read (nbytes=256, buf=0x7ffdbcfb4f70, fd=18) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7db999881640 (LWP 3735) "gimp-2.10"0x7db99a11ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffdbcfb4f70, fd=18) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7db97cc006c0 (LWP 3784) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7db977e006c0 (LWP 3756) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7db97d6006c0 (LWP 3753) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7db984e006c0 (LWP 3750) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7db987e006c0 (LWP 3749) "gdbus"0x7db99a11b4cd in 
__GI___poll (fds=0x7db938008da0, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7db98d0006c0 (LWP 3748) "gmain"0x7db99a11b4cd in 
__GI___poll (fds=0x616ca1001120, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7db98da006c0 (LWP 3747) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7db98ea006c0 (LWP 3746) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7db98f4006c0 (LWP 3745) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7db98fe006c0 (LWP 3744) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7db9952006c0 (LWP 3743) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7db995c006c0 (LWP 3742) 

[Bug 2065617] [NEW] GIMP crash at startup

[Pieterjan Wintjes]

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: Segmentatiefout

Stack trace:
```

# Stack traces obtained from PID 2465 - Thread 2465 #


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 3195]
[New LWP 2580]
[New LWP 2479]
[New LWP 2476]
[New LWP 2474]
[New LWP 2472]
[New LWP 2471]
[New LWP 2470]
[New LWP 2469]
[New LWP 2468]
[New LWP 2467]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7af508f1ba9a in __GI___libc_read (nbytes=256, buf=0x7ffd34ef33f0, fd=15) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id Frame 
* 1Thread 0x7af5083da640 (LWP 2465) "gimp-2.10"  0x7af508f1ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffd34ef33f0, fd=15) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7af4b7e006c0 (LWP 3195) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7af4f24006c0 (LWP 2580) "swap writer"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7af4e7e006c0 (LWP 2479) "gimp-2.10"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7af4f1a006c0 (LWP 2476) "gimp-2.10"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7af4f2e006c0 (LWP 2474) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7af4ffe006c0 (LWP 2472) "gdbus"  0x7af508f1b4cd in 
__GI___poll (fds=0x7af4eb90, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7af504c006c0 (LWP 2471) "gmain"  0x7af508f1b4cd in 
__GI___poll (fds=0x64f0bbd79920, nfds=2, timeout=6488) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x7af505c006c0 (LWP 2470) "pool-spawner"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7af5066006c0 (LWP 2469) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7af5070006c0 (LWP 2468) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7af507a006c0 (LWP 2467) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 12 (Thread 0x7af507a006c0 (LWP 2467) "worker"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7af50937740d in g_cond_wait () from 

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

[florin]

If it helps, I also have 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?"

[Sandy Patterson]

This appears to fix the issue for me on mantic (23.10) using the mantic-
proposed repo.

45.2-0ubuntu5 - for: gir1.2-mutter-13 libmutter-13-0 mutter-common
mutter

I did have to purge the ppa to get get to install. Maybe I did something
to get those vv version pinned.

I confirmed that I don't get the strange delay (the display persisted up
to 1-2s after I would hit a key sometimes).

I also confirmed that I don't see MetaSyncRing messages on this boot.
Oh, and I rebooted after installing the packages.

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

-- 
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?"

[Tanmoy Dasgupta]

Here is a temporary solution that I am using in a few Ubuntu 22.04
installations that I currently manage.

1) Open a TTY (Ctrl + Alt + F3)

2) Remove mutter-common: sudo apt remove mutter-common gir1.2-mutter-10
libmutter-10-0

This will remove a lot of other important packages. So basically you
will end up with a non-functional desktop. But TTY will thankfully still
work.

3) Add the test-fix ppa (if you haven't already): sudo add-apt-
repository ppa:vanvugt/mutter

4) Install specific versions of the affected packages: 
sudo apt install --allow-downgrades gir1.2-mutter-10=42.9-0ubuntu7vv1 
mutter-common=42.9-0ubuntu7vv1 libmutter-10-0=42.9-0ubuntu7vv1

5) Pin these packages:
sudo apt-mark hold mutter gir1.2-mutter-10 libmutter-10-0 libmutter-10-dev 
libmutter-test-10 mutter-10-tests mutter-common

6) Then install all the packages that went missing: 
sudo apt install ubuntu-desktop^

7) Update packages and then reboot:
sudo apt update && sudo apt upgrade

Let me know if this works. Thanks!

-- 
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?"

[GTBS, LLC]

Antoine (@toniopelo), it is the same as for me.  I do not have Wayland
installed (mutter) - only X11 - and an upgrade of just mutter-common and
libmutter-10-0 from the Jammy Proposed PPA does NOT fix the issue.  As
soon as I try to install mutter (which I don't need or want), apt
proposes making massive deletions/changes to my install.  This is NOT an
option either.

Whatever Daniel van Vugt (vanvugt) created for dependencies on his
"temp" PPA worked and did not require the massive install changes and
fixed the problem.  The Jammy Proposed PPA has different dependencies
and makes it a non-option.

I add my request to please fix this, OR, create another temp PPA with
the same dependencies and a version that gets ahead in priority of the
current (not proposed) jammy PPA.

-- 
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]

I'm just running glxgears all the time :(

-- 
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?"

[Antoine L]

Nobody seems to care but as I stated several times in this thread, for
some people (including me) upgrading these packages will remove some
other packages that apparently need the former ones. This is not an
option.

See the output of `sudo apt-get install mutter/jammy-proposed
libmutter-10-0/jammy-proposed -s` on my computer in one of my previous
comments (#100) for details.

I would really appreciate somebody to give me a hand here, I don't have
that much xp with apt specifics so it might be obvious to some of you.

I use ubuntu as my main and only driver for my everyday dev work and it
is barely usable since one or two months now. I will have to change
distro if I don't find a quick solution as it is impacting vscode
intelliJ, terminal, browser responsivness and more.

-- 
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?"

[threadbareobserve]

I've been fighting with this bug for about 2 months now. 
I've tried the new mutter fixes but nothing seemed to work.

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.
2. After ubuntu install first thing you do is put a hold the mutter packages
   ```
   sudo dpkg -i *mutter*.deb
   echo libmutter-$package hold | sudo dpkg --set-selections
   ```
3. Upgrade NVIDIA to `nvidia-driver-535` proprietary.

-- 
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 1966635] Re: can't move file/directory by drag and drop by using touch monitor

[Zorro Zhang]

Confirmed it's workable under Ubuntu 24.04 GA release on XPS 13, Wayland
mode.

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

Title:
  can't move file/directory by drag and drop by using touch monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1966635/+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

[Jeremy Bícha]

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

** Also affects: gnome-shell (Ubuntu Noble)
   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/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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Tais P. Hansen]

@mark You need to enable the proposed archive to get the packages I
mentioned. See https://wiki.ubuntu.com/Testing/EnableProposed. I highly
recommend using the "selective" approach.

-- 
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?"

[Mark Erbaugh]

Ubuntu LTS 22.04.4

I ran Deku's script, from message 102 above:

sudo apt install -y --allow-downgrades \
gir1.2-mutter-10=42.9-0ubuntu7vv1 \
mutter-common=42.9-0ubuntu7vv1 \
libmutter-10-0=42.9-0ubuntu7vv1;

That cleared things up, no lag / MetaSyncRing errors, but Ubuntu now
wants to re-upgrade the packages back to 42.9-0ubuntu7.1

I tried installing the 0ubuntu8 packages from Tais in message 111, but
apt couldn't find them

-- 
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 2065587] [NEW] Add explicit dependency on glib 2.80 to ease upgrades 22.04 → 24.04

[Jeremy Bícha]

Public bug reported:

Impact
--
It was detected that something could cause GNOME Shell to crash during the 
upgrade from Ubuntu 22.04 LTS to 24.04 LTS. GNOME Shell then was unable to 
start because it wasn't able to locate the gio 2.0 gir files.

Therefore, we are bumping the minimum version of the gir1.2-glib-2.0
dependency to 2.80 so that gnome-shell is not upgraded before the gir
file it depends on.

Test Case
-

What Could Go Wrong
---

Other Info
--
There was a major reorganization in glib 2.80 compared to glib 2.78. The gir 
file is now built by the glib2.0 source package instead of from 
gobject-introspection which bumped the package version from 1.78 to 2.78.

** Affects: gnome-shell (Ubuntu)
 Importance: High
 Status: In Progress


** Tags: noble

** Description changed:

  Impact
  --
  It was detected that something could cause GNOME Shell to crash during the 
upgrade from Ubuntu 22.04 LTS to 24.04 LTS. GNOME Shell then was unable to 
start because it wasn't able to locate the gio 2.0 gir files.
  
  Therefore, we are bumping the minimum version of the gir1.2-glib-2.0
  dependency to 2.80 so that gnome-shell is not upgraded before the gir
  file it depends on.
  
  Test Case
  -
  
  What Could Go Wrong
  ---
  
  Other Info
  --
- There was a major reorganization in glib 2.80 compared to glib 2.78.
+ There was a major reorganization in glib 2.80 compared to glib 2.78. The gir 
file is now built by the glib2.0 source package instead of from 
gobject-introspection which bumped the package version from 1.78 to 2.78.

-- 
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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Roland65]

Using these packages seems to work:
https://bugs.launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8

-- 
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 2065582] [NEW] there is no way to disable the onscreen keyboard

[Susan Cragin]

Public bug reported:

I have an XPS13 and am running Ubuntu in xorg because that is required for my 
Plover stenotype program. The program uses an external keyboard.
I need the onscreen keyboard disabled, because I am using the plover keyboard 
to input information, but I cannot do it, either through Settings / 
Accessibility / Typing or trying various terminal entries suggested by chatgpt. 
(It suggests disabling onboard, but the program was not installed, and 
installing it and then disabling it did nothing.)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-40.40-generic 6.5.13
Uname: Linux 6.5.0-40-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 13 06:37:23 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-04-08 (35 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45.2-0ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2024-04-08 (35 days ago)

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


** Tags: amd64 apport-bug mantic

-- 
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 2065575] Re: GIMP crashed

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

Title:
  GIMP crashed

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


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

[Bug 1840996] Re: Working with Samba

[Sebastien Bacher]

Upstream believes it's fixed in the current version, could you verify if
that's still an issue for you on Ubuntu Noble?

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

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

Title:
  Working with Samba

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


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

[Bug 2065575] [NEW] GIMP crashed

[zzarko]

Public bug reported:

GIMP crashed on closing, and asket to send this. So, here it is...

```
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: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 118814 - Thread 118814 #


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 118959]
[New LWP 118874]
[New LWP 118840]
[New LWP 118836]
[New LWP 118834]
[New LWP 118833]
[New LWP 118832]
[New LWP 118831]
[New LWP 118830]
[New LWP 118829]
[New LWP 118828]
[New LWP 118827]
[New LWP 118826]
[New LWP 118825]
[New LWP 118824]
[New LWP 118823]
[New LWP 118822]
[New LWP 118821]
[New LWP 118820]
[New LWP 118819]
[New LWP 118818]
[New LWP 118817]
[New LWP 118816]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x75db62aa9c00 in malloc_consolidate (av=av@entry=0x75db62c03ac0 
) at ./malloc/malloc.c:4878
  Id   Target Id Frame 
* 1Thread 0x75db62289640 (LWP 118814) "gimp" 0x75db62aa9c00 in 
malloc_consolidate (av=av@entry=0x75db62c03ac0 ) at 
./malloc/malloc.c:4878
  2Thread 0x75db37e006c0 (LWP 118959) "pool-gimp"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x75db350006c0 (LWP 118874) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x75db35a006c0 (LWP 118840) "gimp" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x75db374006c0 (LWP 118836) "gimp" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x75db40c006c0 (LWP 118834) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x75db4d6006c0 (LWP 118833) "gdbus"0x75db62b1b4cd in 
__GI___poll (fds=0x75daf00024a0, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x75db4e0006c0 (LWP 118832) "gmain"0x75db62b1b4cd in 
__GI___poll (fds=0x5c4342cd7c00, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x75db4ea006c0 (LWP 118831) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x75db4fe006c0 (LWP 118830) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x75db54c006c0 (LWP 118829) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x75db556006c0 (LWP 118828) "worker"   syscall () at 

[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]

This is awful. 22.04 is back to being treacle again. Halp!

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

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of 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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Tais P. Hansen]

Installing the packages below seems to work for me (on Ubuntu 22.04.4,
X11, nvidia-550.78). No terminal lag is observed.

mutter=42.9-0ubuntu8
mutter-common=42.9-0ubuntu8
libmutter-10-0=42.9-0ubuntu8
gir1.2-mutter-10=42.9-0ubuntu8

-- 
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?"

[Tais P. Hansen]

I had to downgrade the mutter packages on Ubuntu 22.04.4 today as the
lag returned after the latest update. Did almost the same as Deku King
although opted to deprioritize the 42.9-0ubuntu7.1 packages instead of
locking the older ones.

Package: gir1.2-mutter-10
Pin: version 42.9-0ubuntu7.1
Pin-Priority: 1

Package: libmutter-10-0
Pin: version 42.9-0ubuntu7.1
Pin-Priority: 1

Package: mutter
Pin: version 42.9-0ubuntu7.1
Pin-Priority: 1

Package: mutter-common
Pin: version 42.9-0ubuntu7.1
Pin-Priority: 1

I have not tested proposed yet but will do that shortly.

-- 
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 2064682] Re: Gnome control center crash on launch with "undefined symbol: GST_CAT_DEFAULT"

[Sebastien Bacher]

Thanks, I don't see anything weird in the log and the packages version
seem correct ... what's the output of

$ debsums libgstreamer1.0-0

?

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

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

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

Title:
  Gnome control center crash on launch with "undefined symbol:
  GST_CAT_DEFAULT"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064682/+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

[rue]

HI I tested this also as I was not having the issues described at the time.
Working with lotuspsychje I set my login to 'Autologin' rebooted and then I had 
the resize bug.
 
Applications affected don't support CLD and some are Electron apps.
Gimp, Hexchat, Spotify, Discord, Teams 

One thing I noticed was when these apps were behaving correctly, they had a 
slight drop shadow around them.
On reboot and autologin enabled that drop shadow was do longer there and I 
could not resize the windows. 

Is this also related to the Compositor? Maybe something is not starting
when Autologin is enabled.

-- 
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 2065564] [NEW] crashing

[Muhammad Fasial]

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: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 25950 - Thread 25950 #


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 26298]
[New LWP 26035]
[New LWP 25965]
[New LWP 25962]
[New LWP 25960]
[New LWP 25958]
[New LWP 25957]
[New LWP 25956]
[New LWP 25955]
[New LWP 25954]
[New LWP 25953]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f39dbd1ba9a in __GI___libc_read (nbytes=256, buf=0x7ffeccc05bf0, fd=19) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7f39db2fb640 (LWP 25950) "gimp-2.10"0x7f39dbd1ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffeccc05bf0, fd=19) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f39a2a006c0 (LWP 26298) "paint"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f39c52006c0 (LWP 26035) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f39baa006c0 (LWP 25965) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f39bbe006c0 (LWP 25962) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f39c5c006c0 (LWP 25960) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f39d2e006c0 (LWP 25958) "gdbus"0x7f39dbd1b4cd in 
__GI___poll (fds=0x7f39b4009c80, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7f39d38006c0 (LWP 25957) "gmain"0x7f39dbd1b4cd in 
__GI___poll (fds=0x60ad23945150, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x7f39d8a006c0 (LWP 25956) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f39d94006c0 (LWP 25955) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f39d9e006c0 (LWP 25954) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7f39da8006c0 (LWP 25953) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 12 (Thread 0x7f39da8006c0 (LWP 25953) "worker"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f39dc01340d in g_cond_wait () from 

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

[Pirouette Cacahuète]

I have just upgraded to 24.04 from 23.10 and I'd like to emphasize that
for the Firefox case, the comments on that thread mentions "AppArmor
should fix it with beta3" is inaccurate and incomplete: it only
partially fixes the issue since it only covers packaged versions.

Anybody relying on the tarball should have something similar (assuming you 
install in $HOME/bin/firefox)
> $ cat /etc/apparmor.d/firefox-bin
> # This profile allows everything and only exists to give the
> # application a name instead of having the label "unconfined"
> 
> abi ,
> include 
>
> profile firefox /home/XXX/bin/firefox/firefox flags=(unconfined) {
>   userns,
> 
>   # Site-specific additions and overrides. See local/README for details.
>   include if exists 
> }

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