[Bug 1987631] Re: Screencast only records one second
I can confirm that screencast is still broken in Jammy. There's a fix waiting in the 'proposed' repo: https://launchpad.net/ubuntu/+source/pipewire/0.3.48-1ubuntu3 Couldn't it be fast-tracked to the stable one? 22.04 is a LTS version and screencast has been broken for more than a month. -- 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/1987631 Title: Screencast only records one second To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998529] Re: Uninstalling extensions dereferences symlinks, risking data loss
** Changed in: gnome-shell 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/1998529 Title: Uninstalling extensions dereferences symlinks, risking data loss To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1998529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999833] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1999833/+attachment/5635793/+files/ProcEnviron.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/1999833 Title: gnome-shell update should not request a reboot if it is not running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999833] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1999833/+attachment/5635791/+files/GsettingsChanges.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/1999833 Title: gnome-shell update should not request a reboot if it is not running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999833] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1999833/+attachment/5635792/+files/ProcCpuinfoMinimal.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/1999833 Title: gnome-shell update should not request a reboot if it is not running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999833] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1999833/+attachment/5635790/+files/Dependencies.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/1999833 Title: gnome-shell update should not request a reboot if it is not running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999833] [NEW] gnome-shell update should not request a reboot if it is not running
Public bug reported: The gnome-shell package requests a reboot even if no GNOME desktop is running. This reminds me too much of how Microsoft Windows only knows about itself. Windows assumes it is the only OS and overwrites GRUB, and now gnome-shell is assuming it's the only desktop environment (even ignoring the fact that Linux always has TTY too) and requests that everyone reboot even if just its users need to relog. It's also too much like how Windows will tell the user to restart their computer when just a single service needs to be restarted, while gnome-shell is now also telling the user to restart their computer if the just need to relog, possibly with a `killall5`. $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 43.1-0ubuntu1 Candidate: 43.1-0ubuntu1 Version table: *** 43.1-0ubuntu1 500 (phased 80%) 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic-updates/main amd64 Packages 100 /var/lib/dpkg/status 43.0-1ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages # Expected Behavior There should not be a reboot notification in my KDE tray after running apt upgrade. No gnome desktop is logged in. # Actual Behavior There is a needless reboot notification in my KDE tray. `/var/run/reboot-required` exists. $ cat /var/run/reboot-required.pkgs gnome-shell # Analysis In gnome-shell_43.1-0ubuntu1_amd64.deb there is control.tar.zst which has postinst. In that script there is not check for whether a gnome-session is running. Perhaps a `if ps -ef | grep -q gnome-shell; then` could be added. Even Firefox only tells you to restart only running instances. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DisplayManager: DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 PackageArchitecture: amd64 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 ShellJournal: -- No entries -- Tags: third-party-packages kinetic wayland-session Uname: Linux 6.0.12-surface x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-29 (77 days ago) UserGroups: dialout docker kvm lpadmin lxd plugdev sudo systemd-journal video wireshark _MarkForUpload: True ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected kinetic third-party-packages wayland-session ** Tags added: apport-collected kinetic third-party-packages wayland- session ** Description changed: The gnome-shell package requests a reboot even if no GNOME desktop is running. This reminds me too much of how Microsoft Windows only knows about itself. Windows assumes it is the only OS and overwrites GRUB, and now gnome-shell is assuming it's the only desktop environment (even ignoring the fact that Linux always has TTY too) and requests that everyone reboot even if just its users need to relog. It's also too much like how Windows will tell the user to restart their computer when just a single service needs to be restarted, while gnome-shell is now also telling the user to restart their computer if the just need to relog, possibly with a `killall5`. $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 43.1-0ubuntu1 Candidate: 43.1-0ubuntu1 Version table: *** 43.1-0ubuntu1 500 (phased 80%) 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic-updates/main amd64 Packages 100 /var/lib/dpkg/status 43.0-1ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages # Expected Behavior There should not be a reboot notification in my KDE tray after running apt upgrade. No gnome desktop is logged in. # Actual Behavior There is a needless reboot notification in my KDE tray. `/var/run/reboot-required` exists. $ cat /var/run/reboot-required.pkgs gnome-shell # Analysis - In gnome-shell_43.1-0ubuntu1_amd64.deb there is control.tar.zst which - has postinst. In that script there is not check for whether a gnome- - session is running. Perhaps a `if ps -ef | grep -q gnome-shell; then` - could be added. Even Firefox only tells you to restart only running - instances. + In gnome-shell_43.1-0ubuntu1_amd64.deb there is control.tar.zst which has postinst. In that script there is not check for whether a gnome-session is running. Perhaps a `if ps -ef | grep -q gnome-shell; then` could be added. Even Firefox only tells you to restart only running instances. + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: KDE + DisplayManager: + + DistroRelease: Ubuntu 22.10 + Package: gnome-shell 43.1-0ubuntu1 + PackageArc
[Bug 1998296] Re: evolution fails to connect to gmail account ("failed to obtain an access token: timeout was reached")
Yes, that seems to fix it. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1998296
Title:
evolution fails to connect to gmail account ("failed to obtain an
access token: timeout was reached")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1998296/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
** Description changed: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` + 0. open a terminal `journalctl -f` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several times - After 2 or 3 changes the external screen freeze forever. Internal screen is still responsible. Get into journal : + After 2 changes the external screen freeze forever. Internal screen is still responsible. On each `Apply` The journal recorded an kernel error about nvidia_drm and flooded with clutter-frame-clock error. ``` Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 0x5> Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached ``` - one may ignore the KMS update and clutter-frame-clock part since they are always flooding the log. + one may ignore the drmModeAtomicCommit warning, they are always flooding the log (though it may be related issue) + + The clutter warning then flood the log forever till reboot. -- 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/1999830 Title: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
** Summary changed: - external screen freeze during display setting when using wayland + external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* -- 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/1999830 Title: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999830] [NEW] external screen freeze during display setting when using wayland
Public bug reported: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several times After 2 or 3 changes the external screen freeze forever. Internal screen is still responsible. Get into journal : ``` Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 0x5> Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached ``` one may ignore the KMS update and clutter-frame-clock part since they are always flooding the log. ** 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/1999830 Title: external screen freeze during display setting when using wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
maybe related: > [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID > 0x0100] Failed to map NvKmsKapiMemory Failed to map NvKmsKapiMemory > 0x62c80dd4 Mutter 42.5 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
flooded with ` gnome-shell[3217]: (../clutter/clutter/clutter-frame- clock.c:332):clutter_frame_clock_notify_presented: code should not be reached` Then flooded with: > Page flip discarded: drmModeAtomicCommit: Invalid argument > Failed to post KMS update: drmModeAtomicCommit: Invalid argument Then external screen freeze but internal LCD works fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835794] Re: Bookmarks unusable because clicks drag them
** Changed in: nautilus Status: New => Fix Released -- 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/1835794 Title: Bookmarks unusable because clicks drag them To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1835794/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923311] Re: nautilus crash when creating symlink
** Changed in: nautilus Status: New => Fix Released -- 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/1923311 Title: nautilus crash when creating symlink To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1923311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993129] Re: /usr/bin/nautilus:11:g_action_map_lookup_action:nautilus_window_sync_bookmarks:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
** Changed in: nautilus Status: New => Fix Released -- 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/1993129 Title: /usr/bin/nautilus:11:g_action_map_lookup_action:nautilus_window_sync_bookmarks:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1993129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993129] Re: /usr/bin/nautilus:11:g_action_map_lookup_action:nautilus_window_sync_bookmarks:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
It was fixed upstream in https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1020 ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Committed -- 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/1993129 Title: /usr/bin/nautilus:11:g_action_map_lookup_action:nautilus_window_sync_bookmarks:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1993129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
The proposed packages evince and evince-common versions 42.3-0ubuntu3 from jammy-proposed fixes the problem for me on MATE 22.04. Much obliged. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
mozjs102 and gjs packages have been uploaded for jammy, and mozjs102 for kinetic, into the security team PPA here: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+packages Once they are finished building, they can be pocket-copied by an archive admin into the -proposed pocket for more testing. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999802] [NEW] Gimp crash
Public bug reported: ``` GNU Image Manipulation Program version 2.10.30 git-describe: GIMP_2_10_30 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/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 11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --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-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr --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 11.2.0 (Ubuntu 11.2.0-16ubuntu1) # Libraries # using babl version 0.1.92 (compiled against version 0.1.88) using GEGL version 0.4.34 (compiled against version 0.4.34) using GLib version 2.72.4 (compiled against version 2.71.1) using GdkPixbuf version 2.42.8 (compiled against version 2.42.6) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.50.6 (compiled against version 1.50.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Aborted Stack trace: ``` # Stack traces obtained from PID 40144 - Thread 40163 # [New LWP 40147] [New LWP 40148] [New LWP 40149] [New LWP 40150] [New LWP 40151] [New LWP 40152] [New LWP 40153] [New LWP 40154] [New LWP 40155] [New LWP 40156] [New LWP 40157] [New LWP 40158] [New LWP 40159] [New LWP 40160] [New LWP 40161] [New LWP 40162] [New LWP 40163] [New LWP 40164] [New LWP 40165] [New LWP 40185] [New LWP 40186] [New LWP 40209] [New LWP 40235] [New LWP 40252] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Id Target Id Frame * 1Thread 0x7fb32e774300 (LWP 40144) "gimp-2.10" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 2Thread 0x7fb32de8b640 (LWP 40147) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7fb32d68a640 (LWP 40148) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7fb32ce89640 (LWP 40149) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7fb327fff640 (LWP 40150) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7fb31f7fe640 (LWP 40151) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7fb3277fe640 (LWP 40152) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fb326ffd640 (LWP 40153) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7fb3267fc640 (LWP 40154) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 10 Thread 0x7fb325ffb640 (LWP 40155) "worker" __GI___libc_read (nbytes=256, buf=0x7fb325ff8e90, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26 11 Thread 0x7fb3257fa640 (LWP 40156) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7fb324ff9640 (LWP 40157) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7fb31640 (LWP 40158) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 14 Thread 0x7fb31effd640 (LWP 40159) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 15 Thread 0x7fb31e7fc640 (LWP 40160) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 16 Thread 0x7fb31dffb640 (LWP 40161) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 17 Thread 0x7
[Bug 1855711] Re: Add keyboard navigation to desktop icons
This bug was fixed in the package gnome-shell-extension-desktop-icons-ng - 46+really47-1 --- gnome-shell-extension-desktop-icons-ng (46+really47-1) unstable; urgency=medium * New upstream release (LP: #1998084) - Add keyboard navigation to desktop icons (LP: #1855711) - Fix rubberband with margins like top bar or dock (LP: #1971055) * Use debian/watch to mangle the upstream version to lessen version skew if this extension is merged into gnome-shell-extensions later * Drop desktopGrid and metadata patches: applied in new release * Depend on gir1.2-gnomeautoar-0.1 instead of file-roller & xdg-desktop-portal (Closes: #1010810) -- Jeremy Bicha Wed, 14 Dec 2022 16:50:12 -0500 ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1855711 Title: Add keyboard navigation to desktop icons To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1855711/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966795] Re: First boot with fingerprint auth enabled, gdm doesn't prompt to enter password
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1966795 Title: First boot with fingerprint auth enabled, gdm doesn't prompt to enter password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966795/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995682] Re: gnome session freeze when open settings
Thanks your reply, and it seems to be a duplicate of LP#1998950? ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1995682/+attachment/5635707/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1995682 Title: gnome session freeze when open settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1995682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999709] Re: Nautilus as root does not show hidden files even when checked in options.
Thank you for your bug report, starting graphical applications aren't meant to be started as root though so that's not a bug ** 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/1999709 Title: Nautilus as root does not show hidden files even when checked in options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1999709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
