[Bug 130811] Re: use "close" animation when sending to the notification area
I have also facing the same issue on my website... Please check this site: https://www.gogoanimeapkk.com/gogoanime-mod-apk -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/130811 Title: use "close" animation when sending to the notification area To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/130811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060077] Re: Unable to load the feed
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: rhythmbox (Ubuntu) Importance: Undecided => Low ** Changed in: rhythmbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2060077 Title: Unable to load the feed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2060077/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal conn
If you've got similar issue where ubuntu-dock disappeared, try running: killall -HUP gnome-shell to reload GNOME Shell. -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051383] Re: gnome-shell high CPU utilization when moving a high frequency mouse
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/2051383 Title: gnome-shell high CPU utilization when moving a high frequency mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051383] Re: gnome-shell high CPU utilization when moving a high frequency mouse
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons-ng (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/2051383 Title: gnome-shell high CPU utilization when moving a high frequency mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I've fetched some older versions (again, I am running 22.04.4) of packages gir1.2-mutter-10 libmutter-10-0 and mutter-common and made them into hold status. After a very ugly and dangerous move, namely editing /var/lib/dpkg/status by hand (to comply the dependencies of gnome-shell which was broken by forcing older versions of packages ... maybe I should have simply installed also older version of gnome-shell, hmm ...), now everything works perfectly again. -- 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 in native terminal on Nvidia desktops with X11 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 2060122] [NEW] minimise animations fly everywhere
Public bug reported: Problem: When maximising/minimising/restoring a window by clicking on the item in the launcher, sometimes (often) the animation - which makes the window shrink and 'fly' to or from the dock, will fly in the wrong direction. Steps to reproduce: * Have multiple monitors (I think, I don't recall seeing this in a single monitor usage) * Launch a number of applications * Click icons in the dock to trigger animation as applications grow and shrink from the launcher up to the workspace. What should happen: * Window appears near the dock, and grows to the final location on screen and * Window shrinks back down to the dock What happens: * Sometimes windows fly up to the top left of the display, *and* to the dock at the bottom. Animation frames flicker all over the place, but mostly both towards the top left and towards the bottom. It *looks* like alternate frames of animation are flying up and down. Here is a video of it happening. https://www.youtube.com/watch?v=b2vgEurkHk8 I am currently running Ubuntu 23.10, but I am sure I have seen this on multiple releases. I am using multiple displays. Arranged like this: ( 1 )( 2 ) ( 3 ) 1 - external display 2 - external display 3 - Laptop (primary) The launcher is on the bottom of the primary monitor. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 87ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 3 13:31:22 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (607 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to mantic on 2023-10-15 (171 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2060122 Title: minimise animations fly everywhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2060122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
Based on mikabytes's answer, I've found another solution that not will not leave apt in a temporary broken state. For Ubuntu 22.04.4: Download the packages: $ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/gir1.2-mutter-10_42.9-0ubuntu5_amd64.deb $ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/libmutter-10-0_42.9-0ubuntu5_amd64.deb $ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/mutter-common_42.9-0ubuntu5_all.deb Install the packages: $ sudo dpkg -i *mutter*.deb Mark as hold: $ sudo apt-mark hold gir1.2-mutter-10 $ sudo apt-mark hold libmutter-10-0 $ sudo apt-mark hold mutter-common -- 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 in native terminal on Nvidia desktops with X11 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 2060137] [NEW] Gnome freezes on login with X11 and nvidia
Public bug reported: Recently i updated muttter-common(42.9-0ubuntu7) and libmutter(42.9-0ubuntu7), gir1.2-mutter(42.9-0ubuntu7) on Ubuntu 22.04 LTS after which when I try to login the following issue happens but only when I use the nvidia driver and X11 this does not happen when using Wayland or Nouveau driver. The problem is when I try to log in, tested on nvidia drivers 535 and 545. in most cases: Desktop freezes for ~15s, then ~4s black screen, then ~20s grey screen, then works as expected. In some cases: Gnome locks up and needs a hard reset (mouse cursor does not freeze) In rare cases: Works as expected, except high CPU usage There are new error messages in the syslog file that weren't there before: gnome-shell[...]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? gnome-shell[...]: Window manager warning: MetaSyncRing: Too many reboots -- disabling ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060137 Title: Gnome freezes on login with X11 and nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1944464] Re: gnome-screensaver locked screen leaks text to underlying windows
This update is to report that my daughter (now 8 years old) "consistently" (e.g. a couple of times out of hundreds of random sessions in front of a locked screen) triggers this bug and leaks down to the underlying terminal. Again, I had to switch user to unlock the screen and again I found my password in the terminal. My Ubuntu is now 22.04.4 and gnome-screensaver is at version 3.6.1-13ubuntu1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1944464 Title: gnome-screensaver locked screen leaks text to underlying windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1944464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)
** Changed in: mutter Status: New => Fix Released -- 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/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1835521/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
@ Daniel van Vugt, The faulty change has a timestamp of 22 Feb, and the package began to arrive at users probably on 29 Mar. That's a difference of 5 weeks. I'm not familiar with Ubuntu's internal procedures, I don't know how things work, which component (e.g. building packages, QA, somewhat wider testing in -proposed etc.) took how long, but overall 5 weeks is pretty long. As I understand from comments in upstream mutter#3384, it's not immediately obvious to you guys what and why exactly goes wrong and how to properly fix all this. It needs investigation first. This means that my rough guess is that, if everything goes well, it could take maybe 1-2 weeks to develop a fix and another 5 weeks for the regular release prodecure? Do you have any wild estimate on how many people were affected by the old bug that this update fixed, and how many are affected by the new one? The old one seems to be about software rendering, i.e. when running inside a virtual machine. The new one seems to affect people using an NVidia video card with its proprietary driver. Sounds to me that the new issue probably affects way more people. I'm wondering: Is there some guideline, best practice, runbook rule etc. describing how to handle such a situation? If so, what does it say? Wouldn't the right thing be to release new updated packages that revert this change ASAP (like, in a day or two at most, skipping QA and -proposed etc.), and then start to work on the proper fix that fixes both issues at the same 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 in native terminal on Nvidia desktops with X11 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 2060154] [NEW] Sort by "Modified" uses lexicographic ordering
Public bug reported: I have opened a folder where the subfolder dates go back a few years. Expect 16 Feb 2024 < 9 Feb 2024 Actual 9 Feb 2024 < 16 Feb 2024 It seems that the folders are sorted lexicographically by their date string, not chronologically. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2024-04-03 11-58-15.png" https://bugs.launchpad.net/bugs/2060154/+attachment/5761500/+files/Screenshot%20from%202024-04-03%2011-58-15.png -- 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/2060154 Title: Sort by "Modified" uses lexicographic ordering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060154] Re: Sort by "Modified" uses lexicographic ordering
nautilus --version GNOME nautilus 45.rc -- 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/2060154 Title: Sort by "Modified" uses lexicographic ordering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060155] [NEW] gdm3 coredumps when starting (maybe related to snapd apparmor)
Public bug reported: Ubuntu Noble after apt dist-upgrade: gdm3 does not start anymore 2024-04-03T20:50:44.437550+02:00 huahine kernel: audit: type=1400 audit(1712170244.433:170): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=3205 comm="snap-confine" capability=12 capname="net_admin" 2024-04-03T20:50:44.437561+02:00 huahine kernel: audit: type=1400 audit(1712170244.433:171): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=3205 comm="snap-confine" capability=38 capname="perfmon" 2024-04-03T20:50:44.441534+02:00 huahine kernel: audit: type=1400 audit(1712170244.437:172): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.snapd-desktop-integration" name="/proc/3260/maps" pid=3260 comm="5" requested_mask="r" denied_mask="r" fsuid=120 ouid=0 2024-04-03T20:50:44.445081+02:00 huahine snapd-desktop-integration.snapd-desktop-integration[3205]: Sorry, home directories outside of /home needs configuration. 2024-04-03T20:50:44.445123+02:00 huahine snapd-desktop-integration.snapd-desktop-integration[3205]: See https://forum.snapcraft.io/t/11209 for details. 2024-04-03T20:50:44.445759+02:00 huahine systemd[3191]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Main process exited, code=exited, status=1/FAILURE 2024-04-03T20:50:44.445831+02:00 huahine systemd[3191]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 2024-04-03T20:50:44.487215+02:00 huahine systemd[1]: gdm.service: Main process exited, code=dumped, status=5/TRAP 2024-04-03T20:50:44.487368+02:00 huahine systemd[1]: gdm.service: Failed with result 'core-dump'. 2024-04-03T20:50:44.487791+02:00 huahine systemd[1]: gdm.service: Triggering OnFailure= dependencies. 2024-04-03T20:50:44.490976+02:00 huahine systemd[1]: Starting plymouth-quit.service - Terminate Plymouth Boot Screen... 2024-04-03T20:50:44.508150+02:00 huahine systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen. 2024-04-03T20:50:45.527533+02:00 huahine systemd[1]: gdm.service: Scheduled restart job, restart counter is at 1. 2024-04-03T20:50:45.527669+02:00 huahine systemd[1]: plymouth-quit.service: Deactivated successfully. 2024-04-03T20:50:45.527894+02:00 huahine systemd[1]: Stopped plymouth-quit.service - Terminate Plymouth Boot Screen. 2024-04-03T20:50:45.550213+02:00 huahine systemd[1]: Starting gdm.service - GNOME Display Manager... 2024-04-03T20:50:45.612812+02:00 huahine systemd[1]: Started gdm.service - GNOME Display Manager. 2024-04-03T20:50:45.641041+02:00 huahine snapd-desktop-i[2853]: Detected new session c7 at /org/freedesktop/login1/session/c7 2024-04-03T20:50:45.666028+02:00 huahine systemd[1]: Started session-c7.scope - Session c7 of User gdm. 2024-04-03T20:50:45.667383+02:00 huahine gdm3: Gdm: GdmSession: no session desktop files installed, aborting... 2024-04-03T20:50:45.669555+02:00 huahine kernel: traps: gdm3[3276] trap int3 ip:72f305e29681 sp:7ffccb379de0 error:0 in libglib-2.0.so.0.7903.0[72f305de5000+a] 2024-04-03T20:50:45.759719+02:00 huahine systemd[1]: gdm.service: Main process exited, code=dumped, status=5/TRAP 2024-04-03T20:50:45.759800+02:00 huahine systemd[1]: gdm.service: Failed with result 'core-dump'. 2024-04-03T20:50:45.759829+02:00 huahine systemd[1]: gdm.service: Triggering OnFailure= dependencies. 2024-04-03T20:50:45.778560+02:00 huahine systemd[1]: Starting plymouth-quit.service - Terminate Plymouth Boot Screen... 2024-04-03T20:50:45.790694+02:00 huahine systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen. Package: gdm3 Status: install ok installed Priority: optional Section: gnome Installed-Size: 2016 Maintainer: Ubuntu Developers Architecture: amd64 Version: 46~rc-1ubuntu2 Provides: x-display-manager Depends: accountsservice (>= 0.6.35), adduser, bash (>= 4.3), dconf-cli (>= 0.20), dconf-gsettings-backend (>= 0.20), dbus-bin | systemd-sysv, dbus-daemon, default-dbus-system-bus | dbus-system-bus, default-logind | logind, gir1.2-gdm-1.0 (= 46~rc-1ubuntu2), ubuntu-session | gnome-session | x-session-manager | x-window-manager | x-terminal-emulator, gnome-session-bin (>= 3.37.0), gnome-session-common (>= 3.37.0-2~), gnome-settings-daemon (>= 3.37.0), gnome-shell (>= 3.37.90), gsettings-desktop-schemas, libgdm1 (= 46~rc-1ubuntu2), libglib2.0-bin (>= 2.35.0), libpam-modules (>= 0.72-1), libpam-runtime (>= 0.76-13.1), librsvg2-common, polkitd, procps, ucf, x11-common (>= 1:7.6+11), x11-xserver-utils, debconf (>= 0.5) | debconf-2.0, libaccountsservice0 (>= 0.6.55), libaudit1 (>= 1:2.2.1), libc6 (>= 2.38), libcanberra-gtk3-0t64 (>= 0.25), libcanberra0t64 (>= 0.2), libgdk-pixbuf-2.0-0 (>= 2.22.0), libglib2.0-0t64 (>= 2.79.0), libgtk-3-0t64 (>= 3.0.0), libgudev-1.0-0 (>= 232), libjson-glib-1.0-0 (>= 1.5.2), libkeyutils1 (>= 1.5.9), libpam0g (>= 0.99.7.1), libselinux1 (>= 3.1~), libsystemd0 (>
[Bug 2060155] Re: gdm3 coredumps when starting (maybe related to snapd apparmor)
** Attachment added: "coredump" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060155/+attachment/5761501/+files/core._usr_sbin_gdm3.0.c10bb790-5cb1-49f9-8a10-2cb23c7e6652.3726.162130 ** Description changed: - Ubuntu Noble after apt dist-upgrade gdm3 does not start anymore + Ubuntu Noble after apt dist-upgrade: gdm3 does not start anymore 2024-04-03T20:50:44.437550+02:00 huahine kernel: audit: type=1400 audit(1712170244.433:170): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=3205 comm="snap-confine" capability=12 capname="net_admin" 2024-04-03T20:50:44.437561+02:00 huahine kernel: audit: type=1400 audit(1712170244.433:171): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=3205 comm="snap-confine" capability=38 capname="perfmon" 2024-04-03T20:50:44.441534+02:00 huahine kernel: audit: type=1400 audit(1712170244.437:172): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.snapd-desktop-integration" name="/proc/3260/maps" pid=3260 comm="5" requested_mask="r" denied_mask="r" fsuid=120 ouid=0 2024-04-03T20:50:44.445081+02:00 huahine snapd-desktop-integration.snapd-desktop-integration[3205]: Sorry, home directories outside of /home needs configuration. 2024-04-03T20:50:44.445123+02:00 huahine snapd-desktop-integration.snapd-desktop-integration[3205]: See https://forum.snapcraft.io/t/11209 for details. 2024-04-03T20:50:44.445759+02:00 huahine systemd[3191]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Main process exited, code=exited, status=1/FAILURE 2024-04-03T20:50:44.445831+02:00 huahine systemd[3191]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 2024-04-03T20:50:44.487215+02:00 huahine systemd[1]: gdm.service: Main process exited, code=dumped, status=5/TRAP 2024-04-03T20:50:44.487368+02:00 huahine systemd[1]: gdm.service: Failed with result 'core-dump'. 2024-04-03T20:50:44.487791+02:00 huahine systemd[1]: gdm.service: Triggering OnFailure= dependencies. 2024-04-03T20:50:44.490976+02:00 huahine systemd[1]: Starting plymouth-quit.service - Terminate Plymouth Boot Screen... 2024-04-03T20:50:44.508150+02:00 huahine systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen. 2024-04-03T20:50:45.527533+02:00 huahine systemd[1]: gdm.service: Scheduled restart job, restart counter is at 1. 2024-04-03T20:50:45.527669+02:00 huahine systemd[1]: plymouth-quit.service: Deactivated successfully. 2024-04-03T20:50:45.527894+02:00 huahine systemd[1]: Stopped plymouth-quit.service - Terminate Plymouth Boot Screen. 2024-04-03T20:50:45.550213+02:00 huahine systemd[1]: Starting gdm.service - GNOME Display Manager... 2024-04-03T20:50:45.612812+02:00 huahine systemd[1]: Started gdm.service - GNOME Display Manager. 2024-04-03T20:50:45.641041+02:00 huahine snapd-desktop-i[2853]: Detected new session c7 at /org/freedesktop/login1/session/c7 2024-04-03T20:50:45.666028+02:00 huahine systemd[1]: Started session-c7.scope - Session c7 of User gdm. 2024-04-03T20:50:45.667383+02:00 huahine gdm3: Gdm: GdmSession: no session desktop files installed, aborting... 2024-04-03T20:50:45.669555+02:00 huahine kernel: traps: gdm3[3276] trap int3 ip:72f305e29681 sp:7ffccb379de0 error:0 in libglib-2.0.so.0.7903.0[72f305de5000+a] 2024-04-03T20:50:45.759719+02:00 huahine systemd[1]: gdm.service: Main process exited, code=dumped, status=5/TRAP 2024-04-03T20:50:45.759800+02:00 huahine systemd[1]: gdm.service: Failed with result 'core-dump'. 2024-04-03T20:50:45.759829+02:00 huahine systemd[1]: gdm.service: Triggering OnFailure= dependencies. 2024-04-03T20:50:45.778560+02:00 huahine systemd[1]: Starting plymouth-quit.service - Terminate Plymouth Boot Screen... 2024-04-03T20:50:45.790694+02:00 huahine systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen. - Package: gdm3 Status: install ok installed Priority: optional Section: gnome Installed-Size: 2016 Maintainer: Ubuntu Developers Architecture: amd64 Version: 46~rc-1ubuntu2 Provides: x-display-manager Depends: accountsservice (>= 0.6.35), adduser, bash (>= 4.3), dconf-cli (>= 0.20), dconf-gsettings-backend (>= 0.20), dbus-bin | systemd-sysv, dbus-daemon, default-dbus-system-bus | dbus-system-bus, default-logind | logind, gir1.2-gdm-1.0 (= 46~rc-1ubuntu2), ubuntu-session | gnome-session | x-session-manager | x-window-manager | x-terminal-emulator, gnome-session-bin (>= 3.37.0), gnome-session-common (>= 3.37.0-2~), gnome-settings-daemon (>= 3.37.0), gnome-shell (>= 3.37.90), gsettings-desktop-schemas, libgdm1 (= 46~rc-1ubuntu2), libglib2.0-bin (>= 2.35.0), libpam-modules (>= 0.72-1), libpam-runtime (>= 0.76-13.1), librsvg2-common, polkitd, procps, ucf, x11-common (>= 1:7.6+11), x11-xserver-utils, debconf (>= 0.5) | debconf-2.0, libaccountsservice0 (>
[Bug 2060154] Re: Sort by "Modified" uses lexicographic ordering
** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/2060154 Title: Sort by "Modified" uses lexicographic ordering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060155] Re: gdm3 coredumps when starting
** Summary changed: - gdm3 coredumps when starting (maybe related to snapd apparmor) + gdm3 coredumps when starting ** Attachment added: "crash file" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060155/+attachment/5761518/+files/_usr_sbin_gdm3.0.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2060155 Title: gdm3 coredumps when starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060155/+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
Hi - ok - very long thread so not quite sure how best to resolve.
I note bubblewrap is marked as confirmed but no resolution.
For budgie-control-center - backgrounds - Add Picture I found that the
gnome-desktop library libgnome-desktop-3-20 is calling bwrap and that
this was failing due to permissions.
I worked around this via
```
cat /etc/apparmor.d/bwrap
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"
abi ,
include
profile bwrap /usr/bin/bwrap flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
```
Can this be added to apparmor please?
--
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
I believe bwrap was ignored intentionally, as the point of the apparmor change was to prevent arbitrary apps from making unprivileged user namespaces with capabilities. Allowing Bubblewrap to do so would provide a loophole. Same reason `unshare` isn't allowed to make unprivileged namespaces with capabilities. Perhaps something about libgnome-desktop is incorrectly assuming it needs capabilities that it doesn't actually need? Or is the ability to make unprivileged user namespaces with no capabilities failing somehow? -- 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 2060165] [NEW] gnome-system-tools fail to build on armhf due to implicit function declaration
Public bug reported: See https://launchpadlibrarian.net/722978646/buildlog_ubuntu-noble- armhf.gnome-system-tools_3.0.0-9.1ubuntu3_BUILDING.txt.gz ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-system-tools (Debian) Importance: Unknown Status: Unknown ** Tags: time-t ** Bug watch added: Debian Bug tracker #1066239 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066239 ** Also affects: gnome-system-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066239 Importance: Unknown Status: Unknown ** Tags added: time-t -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/2060165 Title: gnome-system-tools fail to build on armhf due to implicit function declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/2060165/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060165] Re: gnome-system-tools fail to build on armhf due to implicit function declaration
** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/gnome-system-tools/+git/gnome-system-tools/+merge/463640 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/2060165 Title: gnome-system-tools fail to build on armhf due to implicit function declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/2060165/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060165] Re: gnome-system-tools fail to build on armhf due to implicit function declaration
** Changed in: gnome-system-tools (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/2060165 Title: gnome-system-tools fail to build on armhf due to implicit function declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/2060165/+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
@arraybolt3 is correct. Both unshare and bwrap will not get a unconfined profile, as that allows for an arbitrary by-pass of the restriction. There is a potential solution in the works that will allow for bwrap and unshare to function as long as the child task does not require permissions but at this point there are still some issues with it that are being debugged. -- 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
@arraybolt3: Answer to your question. bwrap requires capabilities within the user namespace. unshare is a little more forgiving in that what it requires depends on the options passed but most of the options also require capabilities within the user namespace. The potential solution I mention is comment #91 is to define a profile for bwrap that allows it capabilities within the namespace but does not allow its children capabilities within the namespace, so that bwrap and unshare can not just launch an application to by-pass the restriction. This seems to work well for unshare but there are cases where bwrap is failing in unexpected ways (which is still being debugged). At this late stage the plan is to try to get a fix for bwrap in but if necessary to file an SRU if necessary for the bwrap fix. So yes this is being worked on and even if the fix isn't present on day one we do plan to get it fixed. -- 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 2060155] Re: gdm3 coredumps when starting
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please: 1. Run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2060155 Title: gdm3 coredumps when starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060155/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
The old issue could possibly affect more people because it was for a large commercial partner. Maybe, maybe not... But we don't need to pick and choose which is more important when we can fix everyone's bugs without reverting anything. I proposed two fixes for this bug yesterday: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3685 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3684 and I intend to make a PPA available with this fix in the next day or so. That way nobody is waiting for the slow process of getting an official update released. -- 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 in native terminal on Nvidia desktops with X11 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 2060137] Re: Gnome freezes on login with X11 and nvidia
*** This bug is a duplicate of bug 2059847 *** https://bugs.launchpad.net/bugs/2059847 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2059847, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: nvidia ** Tags added: jammy ** This bug has been marked a duplicate of bug 2059847 Input lag in native terminal on Nvidia desktops with X11 -- 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/2060137 Title: Gnome freezes on login with X11 and nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969140] Re: Window minimize animation flickers and appears in the wrong place
It looks like this affects both Xorg sessions, and Xwayland apps in Wayland sessions? ** Summary changed: - Window minimize animation flickers and appears in the wrong place in Xorg sessions + Window minimize animation flickers and appears in the wrong place ** Tags added: 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/1969140 Title: Window minimize animation flickers and appears in the wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1969140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060137] Re: Gnome freezes on login with X11 and nvidia
*** This bug is a duplicate of bug 2059847 *** https://bugs.launchpad.net/bugs/2059847 I'm sorry if I'm wrong, I've now read the problems mentioned but I'm not having any problems related to input delay, when I try to log into the session it freezes and or black screens. -- 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/2060137 Title: Gnome freezes on login with X11 and nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag on Nvidia desktops with X11
** Changed in: mutter (Ubuntu) Milestone: None => ubuntu-24.04-beta ** Also affects: mutter (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Noble) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Mantic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => High ** Changed in: mutter (Ubuntu Mantic) Importance: Undecided => High ** Changed in: mutter (Ubuntu Jammy) Status: New => Triaged ** Changed in: mutter (Ubuntu Mantic) Status: New => Triaged ** Description changed: + [ Impact ] + + Input or the entire screen may freeze at times on systems using the + Nvidia Xorg driver with GNOME. + + [ Test Plan ] + + 0. Set up a desktop with Nvidia driver 545 or 550. + 1. Log into Ubuntu, ensuring it's a Xorg session. + 2. Open a Terminal, resize it vigorously, and type several lines of text. + 3. Verify that input never froze for any perceptible period of time. + 4. Run: journalctl -b0 | grep MetaSyncRing + 5. Verify the above command does NOT show messages such as: + + Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? + Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? + Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? + Window manager warning: MetaSyncRing: Too many reboots -- disabling + + [ Where problems could occur ] + + Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the + code being modified. + + [ Original Description ] + There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag on Nvidia desktops with X11 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 on Nvidia desktops with X11
** Summary changed: - Input lag in native terminal on Nvidia desktops with X11 + Input lag on Nvidia desktops with X11 -- 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 on Nvidia desktops with X11 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 2060137] Re: Gnome freezes on login with X11 and nvidia
*** This bug is a duplicate of bug 2059847 *** https://bugs.launchpad.net/bugs/2059847 See the upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/3384#note_2070247 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3384 https://gitlab.gnome.org/GNOME/mutter/-/issues/3384 -- 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/2060137 Title: Gnome freezes on login with X11 and nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
