[Bug 2065352] Re: when getting file properties of an audio file twice, file-manager freezes
*** This bug is a duplicate of bug 2056772 *** https://bugs.launchpad.net/bugs/2056772 Thank you for your bug report, the issue was already reported as bug #2056772 ** This bug has been marked a duplicate of bug 2056772 Properties of Audio Files Causes Lock Ups -- 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/2065352 Title: when getting file properties of an audio file twice, file-manager freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065352/+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?"
OMG, what an incredibly stupid move by the ubuntu maintainers. I have the same problem as anyone else who has been forcefully downgraded and I tried to solve it by reverting to Daniel's version. However, this "downgrade" would uninstall a lot of GNOME related packages (including `gnome-shell`): ``` Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libnvidia-cfg1-525 libnvidia-common-525 libnvidia-compute-525 libnvidia-compute-525:i386 libnvidia-decode-525 libnvidia-decode-525:i386 libnvidia-egl-wayland1 libnvidia-encode-525 libnvidia-encode-525:i386 libnvidia-extra-525 libnvidia-fbc1-525 libnvidia-fbc1-525:i386 libnvidia-gl-525 libnvidia-gl-525:i386 nvidia-compute-utils-525 nvidia-dkms-525 nvidia-driver-525 nvidia-firmware-535-535.161.07 nvidia-utils-525 xserver-xorg-video-nvidia-525 Use 'apt autoremove' to remove them. The following additional packages will be installed: notification-daemon policykit-1-gnome python3-update-manager update-manager update-manager-core The following packages will be REMOVED: chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator gnome-shell-extension-desktop-icons-ng gnome-shell-extension-prefs gnome-shell-extension-ubuntu-dock gnome-shell-extensions libmutter-10-0 ubuntu-desktop ubuntu-desktop-minimal ubuntu-session The following NEW packages will be installed: notification-daemon policykit-1-gnome The following packages will be upgraded: python3-update-manager update-manager update-manager-core The following packages will be DOWNGRADED: mutter-common 3 upgraded, 2 newly installed, 1 downgraded, 15 to remove and 13 not upgraded. Need to get 1.246 kB of archives. After this operation, 15,0 MB disk space will be freed. Do you want to continue? [Y/n] ``` Seems like we're stuck and have to wait for a proper fix ... again! I've been using Ubuntu for about 20 years and have never been so close to switching to a different distribution. The way they handle this bug is absolutely ridiculous. -- 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 2065352] [NEW] when getting file properties of an audio file twice, file-manager freezes
Public bug reported: If I want to get the properties (alt+enter) of an audio file (e.g. mp3) the second time (even if it is a file with the same name in other directory), the file-manager freezes. It does not happen with other file types. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 10 03:34:36 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-05-02 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: If I want the to get the properties (alt+enter) of an audio file (e.g. - mp3) the second time the file with the same name (even in other - directory) the filemanager freezes. It does not happen with other file - types. + mp3) the second time I want the properties of a file with the same name + (even in other directory) the file-manager freezes. It does not happen + with other file types. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 10 03:34:36 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-05-02 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Description changed: - If I want the to get the properties (alt+enter) of an audio file (e.g. - mp3) the second time I want the properties of a file with the same name - (even in other directory) the file-manager freezes. It does not happen - with other file types. + If I want to get the properties (alt+enter) of an audio file (e.g. mp3) + the second time (even if it is a file with the same name in other + directory), the file-manager freezes. It does not happen with other file + types. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 10 03:34:36 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-05-02 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Summary changed: - when getting file properties of an audio file twice, filemanger freezes + when getting file properties of an audio file twice, file-manger freezes ** Summary changed: - when getting file properties of an audio file twice, file-manger freezes + when getting file properties of an audio file twice, file-manager freezes -- 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/2065352 Title: when getting file properties of an audio file twice, file-manager freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065352/+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
@jorge-lavila: technically possible yes. I want to be careful with what I promise here, as the user experience is not my area. With that said we are currently looking at using aa-notify as a bridge to improve the user experience. We would install it with a filter to only fire a notification for the user namespace denial/transition. That notification will show in your desktops notification area with a button/click action that will launch a user prompt. There will have to be an SRU to add some of the new functionality, but we can make it available before the SRU via a ppa for those who want to test. I will make sure to update this bug when we have this ready for testing. -- 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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Thanks for the detailed reply @jjohansen, Do you think it would be feasible to spawn a pop-up that says something like "This application uses namespaces which is considered vulnerable to exploits, are you sure you want to continue?" and ask for the password to allow the application to run. This would resolve the issue while still allowing portable applications to run properly. This could be achieved for example providing a tool to ask apparmor for permissions. From my side I can just detect if apparmor is used and ask apparmor to grant access to namespaces, in term, apparmor would spawn a pop-up for the user saying that my application is requesting this permission. -- 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 2064638] Re: Gimp crashed when exporting to .jpg
*** 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/2064638 Title: Gimp crashed when exporting to .jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2064638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065177] Re: Gimp crashed when exporting to .png
*** 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/2065177 Title: Gimp crashed when exporting to .png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2065177/+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?"
Same for me. -- 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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@zgraft: I have added a tor item, a profile will land in an update. -- 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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@jorge-lavila, Its not a theoretical case, they have been used by multiple exploits every year (including this one) since landing in the kernel. Ubuntu is not the only ones looking at restricting them. SELinux has also picked up the ability but they haven't really rolled it out in policy, there are also discussions in other security forms (eg. the OSS security list) about how to disable them better than the giant sysctl that turns them off for everything. The apparmor solution allows doing it on a per application basis. Yes it deliberately requires a privileged operation, otherwise the restriction could be trivially by-passed by exploit code. We know the experience is not user friendly atm, and are working on improving it. Improving both the flexibility on what is mediated on how the user can by-pass/disable the restriction. On the GUI side the end goal is something similar to what you get on MacOS where the user gets notified, and has to go to the security center to enable running an untrusted application. There is in fact a profile coming for bwrap, and unshare, but not the unconfined profile that is being generically used to disable the restriction. The profile will restrict certain modes of operation, and prevent applications launch by it from having privilege within the user namespace. It will open the ubuntu shipped versions up for regular users again for many of its use cases. Unfortunately untrusted code, which is the case of code downloaded into the home dir, will require a privileged operation to be able to use user namespaces. That could be the use of sudo when using the application, or creating a profile for the application, which then allows the user to subsequently use the application without a privileged operation. ** Also affects: tor (Ubuntu) Importance: Undecided Status: New -- 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
Re: [Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
Hi! Just now I made a screencast: https://drive.google.com/file/d/1PaonPodD_v27OCFeE5m6t7PO7OM1ial0/view?usp=drive_link Operating System: Ubuntu Studio 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-31-lowlatency (64-bit) Graphics Platform: X11 On Thu, May 9, 2024 at 6:15 PM wgroiss <2055...@bugs.launchpad.net> wrote: > I have now gimp package 2.10.36-3build3 > > and i have done this 4 steps: > > + 1. Install GIMP on Ubuntu 24.04. > + 2. Create a blank image and draw a black squiggly line in it. > + 3. Export it as a PNG. > + 4. Close GIMP, and click "Discard" when prompted if you want to save > your changes. > > Gimp does not crash anymore. It closes without failure. Thanks! > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2064962). > https://bugs.launchpad.net/bugs/2055044 > > Title: > GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) > > Status in The Gimp: > Fix Released > Status in gimp package in Ubuntu: > Fix Committed > Status in gimp source package in Noble: > Fix Committed > Status in gimp source package in Oracular: > Fix Committed > > Bug description: > [ Impact ] > > GIMP is crashing when closed on Ubuntu 24.04 only. This seems to > happen if an unsaved image is present, popping up the dialog asking if > you want to save your changes. If you click "Discard", GIMP crashes. > This isn't too critical for data safety, but it is a serious papercut > and can result in data loss in certain edge cases according to the > upstream bug report in GIMP. > > There is already a one-line patch available that solves the problem: > > https://gitlab.gnome.org/GNOME/gimp/-/merge_requests/1442/diffs?commit_id=d7228727d7a4b11909001cf8fd8977d68bd29720 > This has been merged upstream. > > [ Test Plan ] > > 1. Install GIMP on Ubuntu 24.04. > 2. Create a blank image and draw a black squiggly line in it. > 3. Export it as a PNG. > 4. Close GIMP, and click "Discard" when prompted if you want to save > your changes. > 5. Observe crash. > 6. Install a patched GIMP that has the previously linked patch applied. > 7. Repeat steps 1-4 and ensure that GIMP does not crash and that the > image is saved properly. > > [ Where problems could occur ] > > The patch changes the behavior of signal handlers, meaning that a > difference between upstream GIMP and Ubuntu's GIMP could potentially > result in the patch being incompatible and causing similar or worse > crashing issues. The above test plan will likely catch such issues. > > -- > > Original bug report: > > Hello. > > I report a bug or supposed to be a bug concerning GIMP. I had worked > with GIMP without pb. > > When closing the GIMP session, I got a crash (Refer to reported info > below). > > My configuration is Kubuntu 24.04 (Dev) Noble updated daily. > > I remain available to provide further information. > Thanks to you for your support. Regards. Xavier > > > > ``` > 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-7ubuntu1' --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-bootstrap --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes > --with-default-libstdcxx-abi=new --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-p2aSDx/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-p2aSDx/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 > --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 >Thread model: posix >Supported LTO compression algorithms: zlib zstd >gcc version 13.2.0 (Ubuntu 13.2.0-7ubuntu1) > > # Libraries # > using babl version 0.1.108 (compiled against version 0.1.106) > using GEGL ve
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
Yep, same issue for me. I have not applied this update yet: From "apt changelog mutter-common" run just seconds ago: mutter (42.9-0ubuntu7.1) jammy-security; urgency=medium * No-change rebuild in the -security pocket. -- Marc Deslauriers Tue, 07 May 2024 17:12:45 -0400 From "apt-cache policy mutter-common " mutter-common: Installed: 42.9-0ubuntu7vv1 Candidate: 42.9-0ubuntu7.1 Version table: 42.9-0ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages *** 42.9-0ubuntu7vv1 500 500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main amd64 Packages 500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages Since there was "No Change" in the official version, can Daniel quickly bump the version of his TEMP fix to "42.9-0ubuntu7.1vv1" (or equiv) so it becomes the latest again and we can wait for the next 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/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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Thanks for the reply! My use case is this one 'shipped as a .tar.gz that people unpack into their home dir and then use'. To me it seems counter-intuitive to force applications to run un-sanboxed for added security; both the solutions proposed (with the application profile and to turn off the user namespace restrictions) would require root privileges, which I currently do not require users to have to be able to run my application. Does Ubuntu have plans for an alternative to bubblewrap sandboxing? Blocking kernel features because they might be exploited seems really extreme. -- 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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Also note that even the system's build of Bubblewrap is not granted the ability to bypass user namespace restrictions as that would allow the restrictions to be bypassed by any application. Doing this to your own build of Bubblewrap will pose the same security issue. If you can avoid doing things the way you're doing, that would be best, otherwise just turning off the restriction or granting your build of Bubblewrap an exception at install time is probably the best you can do. -- 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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Unless your app and Bubblewrap can both work without any capabilities in an unprivileged user namespace, things will probably go south. You should probably be installing an AppArmor profile for your app that allows you to use unprivileged user namespaces normally again, as described in Comment 5 (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/comments/5). You can look at `/etc/apparmor.d/chrome` as an example profile, and make your profile similar. This will require that your build of Bubblewrap be installed into a static location on the filesystem - if you're depending on Bubblewrap working no matter where the binary is on the filesystem (for instance, if your app is portable and is shipped as a .tar.gz that people unpack into their home dir and then use), you'll need to turn off the user namespace restrictions entirely during the install process, as described in the Ubuntu 24.04 release notes (https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release- notes/39890): * Disable this restriction using a persistent setting by adding a new file (/etc/sysctl.d/60-apparmor-namespace.conf) with the following contents: kernel.apparmor_restrict_unprivileged_userns=0 Reboot. This is similar to the previous behaviour, but it does not mitigate against kernel exploits that abuse the unprivileged user namespaces feature. Try to avoid using the "disable unprivileged user namespace restriction" solution if at all possible. -- 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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
In Ubuntu 22.04, I just got an update for mutter (42.9-0ubuntu7.1), replacing the one from @Daniel's PPA (42.9-0ubuntu7vv1). However, the bug resurfaced with this new version. Regrettably, it seems this update didn't include Daniel van Vugt's proposed fix. -- 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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Hello, Pardon my ignorance, but I ship applications with my own build of bubblewrap to run in a sandboxed manner. bwrap's pivot_root allows my application to work across several distros without worrying about issues with missing or incompatible libraries; it also makes possible to run the same binary on both musl and glibc systems. Does this mean that this will never work on ubuntu again even after the proposed fix (since I do not use the system provided /usr/bin/bwrap binary)? -- 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 2038761] Re: gnome-disk-utility does not give size of nvme disk
Sorry: on a different PC with both Ubuntu 24.04 Noble and 24.10 Oracular the bug is still here. Next week i will have again the PC where the problem was disappeared to do some more test. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/2038761 Title: gnome-disk-utility does not give size of nvme disk To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2038761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065331] Re: package shared-mime-info 2.1-2 failed to install/upgrade: 已安装 shared-mime-info 软件包 post-installation 脚本 子进程返回错误状态 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: shared-mime-info (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/2065331 Title: package shared-mime-info 2.1-2 failed to install/upgrade: 已安装 shared- mime-info 软件包 post-installation 脚本 子进程返回错误状态 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2065331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065331] [NEW] package shared-mime-info 2.1-2 failed to install/upgrade: 已安装 shared-mime-info 软件包 post-installation 脚本 子进程返回错误状态 1
Public bug reported: audacity installation failed with these message ProblemType: Package DistroRelease: Ubuntu 22.04 Package: shared-mime-info 2.1-2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri May 10 00:36:50 2024 ErrorMessage: 已安装 shared-mime-info 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2024-04-05 (34 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: shared-mime-info Title: package shared-mime-info 2.1-2 failed to install/upgrade: 已安装 shared-mime-info 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/2065331 Title: package shared-mime-info 2.1-2 failed to install/upgrade: 已安装 shared- mime-info 软件包 post-installation 脚本 子进程返回错误状态 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2065331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2038761] Re: gnome-disk-utility does not give size of nvme disk
Problem reappeared in Ubuntu 24.10 Oracular installed today from Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240509.1) And also in 24.04 Noble from Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) was disappeared in 24.04 Noble from a previous ISO with many updates -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/2038761 Title: gnome-disk-utility does not give size of nvme disk To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2038761/+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)
I have now gimp package 2.10.36-3build3 and i have done this 4 steps: + 1. Install GIMP on Ubuntu 24.04. + 2. Create a blank image and draw a black squiggly line in it. + 3. Export it as a PNG. + 4. Close GIMP, and click "Discard" when prompted if you want to save your changes. Gimp does not crash anymore. It closes without failure. Thanks! -- 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 2065296] Re: gnome-keyring missing login.keyring until first user login in seahorse and Chrome on ubuntu 24.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2065296 Title: gnome-keyring missing login.keyring until first user login in seahorse and Chrome on ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2065296/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065296] Re: gnome-keyring missing login.keyring until first user login in seahorse and Chrome on ubuntu 24.04
** Description changed: I have ubuntu 24.04 and gnome-keyring apt policy gnome-keyring gnome-keyring: - Installed: 46.1-2build1 - Candidate: 46.1-2build1 - Version table: - *** 46.1-2build1 500 - 500 http://ua.archive.ubuntu.com/ubuntu noble/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 46.1-2build1 + Candidate: 46.1-2build1 + Version table: + *** 46.1-2build1 500 + 500 http://ua.archive.ubuntu.com/ubuntu noble/main amd64 Packages + 100 /var/lib/dpkg/status When freshly created user logs in first time the login keyring created but it is not visible in seahorse. In user's home files exist myt@test-VirtualBox:~/.local/share/keyrings$ ll total 16 drwx-- 2 myt myt 4096 May 9 15:36 ./ drwx-- 11 myt myt 4096 May 9 15:36 ../ -rw--- 1 myt myt 105 May 9 15:36 login.keyring -rw--- 1 myt myt 207 May 9 15:36 user.keystore - I try to install Google Chrome browser from official website which uses - keyring and it does not start in logs I see prompt which does not appear - in screen. When user logs out and then logs in problem disappeared: - Seahorse displays login keyring and Chrome starts successfully. + I try to check via terminal is keyring is locked on first login and it + gives me busctl --user get-property org.freedesktop.secrets + /org/freedesktop/secrets/collection/login + org.freedesktop.Secret.Collection Locked: + + Failed to get property Locked on interface + org.freedesktop.Secret.Collection: Object does not exist at path + “/org/freedesktop/secrets/collection/login” + + After I log out and then log in it gives: + myt@test-VirtualBox:~$ busctl --user get-property org.freedesktop.secrets /org/freedesktop/secrets/collection/login org.freedesktop.Secret.Collection Locked + b false + + + I try to install Google Chrome browser from official website which uses keyring and it does not start in logs I see prompt which does not appear in screen. When user logs out and then logs in problem disappeared: Seahorse displays login keyring and Chrome starts successfully. Logs: May 09 15:37:19 test-VirtualBox dbus-daemon[533]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.1146' (uid=1003 pid=29505 comm="/opt/google/chrome/chrome" label="chrome (unconfined)") May 09 15:37:19 test-VirtualBox systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth). May 09 15:37:19 test-VirtualBox dbus-daemon[27983]: [session uid=1003 pid=27983] Activating service name='org.gnome.keyring.SystemPrompter' requested by ':1.4' (uid=1003 pid=27984 comm="/usr/bin/gnome-keyring-daemon --foreground --compo" label="unconfined") May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: bus acquired: org.gnome.keyring.SystemPrompter May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: registering prompter May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: bus acquired: org.gnome.keyring.PrivatePrompter May 09 15:37:19 test-VirtualBox dbus-daemon[27983]: [session uid=1003 pid=27983] Successfully activated service 'org.gnome.keyring.SystemPrompter' May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: acquired name: org.gnome.keyring.SystemPrompter May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p3@:1.4 May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p3@:1.4 May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: creating new GcrPromptDialog prompt May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: automatically selecting secret exchange protocol May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: generating public key May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: beginning the secret exchange: [sx-aes-1]\npublic=tOaQ3JOvQBNxL9ZgXnjLvXTkDduutPcB8BHaLAEPHjTrF+FCrKZbF+gJtzsUQL8LjaK6qQmzKUEhqmXgKFrHY64BijXpml3pUrWYADcfYTo8AzixXVVAcgyp2I7r5+gKNsNdu5tgZm1pMd/vY6xNcUqu4CrAFl4kSTHJkYupf77dZRY8WmoGRrEUHQHuMgCVNeE9xOLq4T36qej0gBmlDXUvPgVdZaORRZfKXoGz9SkPnhqd7+iFNO+FL2fsIJUQ\n May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p3@:1.4 May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: acquired name: org.gnome.keyring.PrivatePrompter May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p3@:1.4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2065296 Title: gnome-keyring missing login.keyring until first user login in seahorse and Chrome on ubuntu 24.04 To manage notifications about
[Bug 2065296] [NEW] gnome-keyring missing login.keyring until first user login in seahorse and Chrome on ubuntu 24.04
Public bug reported: I have ubuntu 24.04 and gnome-keyring apt policy gnome-keyring gnome-keyring: Installed: 46.1-2build1 Candidate: 46.1-2build1 Version table: *** 46.1-2build1 500 500 http://ua.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status When freshly created user logs in first time the login keyring created but it is not visible in seahorse. In user's home files exist myt@test-VirtualBox:~/.local/share/keyrings$ ll total 16 drwx-- 2 myt myt 4096 May 9 15:36 ./ drwx-- 11 myt myt 4096 May 9 15:36 ../ -rw--- 1 myt myt 105 May 9 15:36 login.keyring -rw--- 1 myt myt 207 May 9 15:36 user.keystore I try to install Google Chrome browser from official website which uses keyring and it does not start in logs I see prompt which does not appear in screen. When user logs out and then logs in problem disappeared: Seahorse displays login keyring and Chrome starts successfully. Logs: May 09 15:37:19 test-VirtualBox dbus-daemon[533]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.1146' (uid=1003 pid=29505 comm="/opt/google/chrome/chrome" label="chrome (unconfined)") May 09 15:37:19 test-VirtualBox systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth). May 09 15:37:19 test-VirtualBox dbus-daemon[27983]: [session uid=1003 pid=27983] Activating service name='org.gnome.keyring.SystemPrompter' requested by ':1.4' (uid=1003 pid=27984 comm="/usr/bin/gnome-keyring-daemon --foreground --compo" label="unconfined") May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: bus acquired: org.gnome.keyring.SystemPrompter May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: registering prompter May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: bus acquired: org.gnome.keyring.PrivatePrompter May 09 15:37:19 test-VirtualBox dbus-daemon[27983]: [session uid=1003 pid=27983] Successfully activated service 'org.gnome.keyring.SystemPrompter' May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: acquired name: org.gnome.keyring.SystemPrompter May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p3@:1.4 May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p3@:1.4 May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: creating new GcrPromptDialog prompt May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: automatically selecting secret exchange protocol May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: generating public key May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: beginning the secret exchange: [sx-aes-1]\npublic=tOaQ3JOvQBNxL9ZgXnjLvXTkDduutPcB8BHaLAEPHjTrF+FCrKZbF+gJtzsUQL8LjaK6qQmzKUEhqmXgKFrHY64BijXpml3pUrWYADcfYTo8AzixXVVAcgyp2I7r5+gKNsNdu5tgZm1pMd/vY6xNcUqu4CrAFl4kSTHJkYupf77dZRY8WmoGRrEUHQHuMgCVNeE9xOLq4T36qej0gBmlDXUvPgVdZaORRZfKXoGz9SkPnhqd7+iFNO+FL2fsIJUQ\n May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p3@:1.4 May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: acquired name: org.gnome.keyring.PrivatePrompter May 09 15:37:19 test-VirtualBox gcr-prompter[29566]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p3@:1.4 ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2065296 Title: gnome-keyring missing login.keyring until first user login in seahorse and Chrome on ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2065296/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065294] [NEW] Diagnostics settings flips to Never without any user action
Public bug reported: steps to reproduce. 1. Open Gnome Settings 2. Go to Privacy -> Diagnostics 3. You should see `Send error reports to Canonical` set to Manual by default. 4. Stay on the settings page for some time (maybe <2 mins), the setting will slip to Never. You could also try to change the settings to Automatic and stay on the page, it will also flip to Never within a couple of minutes. I noticed this on Jammy, Mantic, and Noble. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Description changed: steps to reproduce. 1. Open Gnome Settings 2. Go to Privacy -> Diagnostics 3. You should see `Send error reports to Canonical` set to Manual by default. 4. Stay on the settings page for some time (maybe <2 mins), the setting will slip to Never. You could also try to change the settings to Automatic and stay on the page, it will also flip to Never within a couple of minutes. + + I noticed this on Jammy, Mantic, and Noble. -- 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/2065294 Title: Diagnostics settings flips to Never without any user action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2065294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065161] Re: On the second opening, app folder will not close on click outside
Found the bug report in gitlab https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7541 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7541 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7541 -- 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/2065161 Title: On the second opening, app folder will not close on click outside To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2065161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
