** Description changed: [ Impact ] - * An explanation of the effects of the bug on users and justification - for backporting the fix to the stable release. + * End users are reporting that extended usage of the desktop can lead to + a variety of very undesirable issues. + 1. CPU maxing out at 100% leading to excessive battery usage. + 2. Often after a suspend and resume, polkit dialogs where seeking to + elevate permissions no longer appear + 3. Screen blanking for an extended amount of time can lead to memory + exhaustion with the systemd OOM kicking in to kill vital processes + such as budgie-panel. - * In addition, it is helpful, but not required, to include an - explanation of how the upload fixes this bug. + * This has been traced to a single budgie process called budgie-polkit-dialog + that spins to 100%. Underlying this is its usage of multiple wayland + client calls that interact with each other causing deadlocks. + + * The upstream resolution is to force repeated calls to obtain wayland based + info to be serialised thus avoiding the possibility of multiple wayland + calls causing deadlocks. [ Test Plan ] - * detailed instructions how to reproduce the bug + * Use any application that requests elevated permissions to continue. + For example, gnome-disks writing to an ISO or sddm-customize to change + the login screen. - * these should allow someone who is not familiar with the affected - package to reproduce the bug and verify that the updated package - fixes the problem. + * Repeatedly use these apps will often result in the polkit dialog + not appearing - once it doesnt appear the only way to make it reappear + is to logout and login. - * if other testing is appropriate to perform before landing this - update, this should also be described here. + * alternative routes to invoke this issue is to suspend the desktop + and resume after - say - half an hour and try to use an app that + invokes a polkit dialog + + * Install the budgie-desktop package from proposed + sudo apt install -t resolute-proposed budgie-desktop budgie-core libbudgie-raven-plugin0 libbudgie-appindexer0 libbudgie-plugin0 libbudgietheme0 libbudgie-private0 libbudgie-windowing0 libraven0 + + reboot and repeat the test plan. [ Where problems could occur ] - * Think about what the upload changes in the software. Imagine the - change is wrong or breaks something else: how would this show up? + * The change is specific to budgie-desktop - no other desktop environment + use this process (budgie-polkit-dialog) - * It is assumed that any SRU candidate patch is well-tested before - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the event - of a regression. + * The patch has been through extensive testing via a PPA through our + discourse forum. The patch has been evaluated and successfully + upstreamed. These details are in the dep3 header of the patch. - * This must never be "None" or "Low", or entirely an argument as to why - your upload is low risk. + * In terms of regression risks, the area of invoking polkit dialogs + could possibly regress further than it already occurs. The experience + of users who require elevated permissions would regress. - * This both shows the SRU team that the risks have been considered, - and provides guidance to testers in regression-testing the SRU. + * if regressions in this area occurs then command line alternatives + (sudo) could be used if the end user understands how to use the + terminal. + + * Given the propensity for this issue to occur and the serious issues observed + (processes being killed, battery issues, unable to run apps or capabilities + requiring elevated permissions, the ubuntu budgie team consider this patch + a necessity for LTS users. [ Other Info ] - * Anything else you think is useful to include - - * Make sure to explain any deviation from the norm, to save the SRU - reviewer from having to infer your reasoning, possibly incorrectly. - This should also help reduce review iterations, particularly when the - reason for the deviation is not obvious. - - * Anticipate questions from users, SRU, +1 maintenance, security teams - and the Technical Board and address these questions in advance - + * N/A ----- Several related reports via our discourse forum https://discourse.ubuntubudgie.org/t/the-logout-shutdown-restart- buttons-on-the-graphical-interface-sometimes-dont-work-ubuntu- budgie-26-04-wayland/8728 https://discourse.ubuntubudgie.org/t/crystal-dock-budgie-panel-the- bottom-panel-will-disappear-and-userspace-out-of-memory-oom-killer- socket-ubuntu-budgie-26-04/8759 https://discourse.ubuntubudgie.org/t/on-ubuntu-budgie-26-04-with- wayland-the-sleep-wake-panel-disappears-and-the-system-freezes/8757 All have been found to be due to a key budgie specific process budgie- polkit-dialog that runs at 100%, using memory during this run and causing the systemd OOM to kick in when memory is exhausted. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: budgie-desktop 10.10.2-1ubuntu4 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: Budgie Date: Mon Jun 22 21:06:40 2026 InstallationDate: Installed on 2026-04-05 (78 days ago) InstallationMedia: Ubuntu-Budgie 26.04 "Resolute Raccoon" - Daily amd64 (20260402) PackageArchitecture: all SourcePackage: budgie-desktop UpgradeStatus: No upgrade log present (probably fresh install)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2157920 Title: [SRU] budgie-desktop fails to display polkit based dialogs and causes the desktop to freeze/run out of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2157920/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
