[Bug 1913672] Re: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width
Thanks for the info, that's good to know. And btw, is there a place to report or discuss about the phased-updater, like there is for Ubuntu packages ? -- 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/1913672 Title: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913672] Re: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width
Maybe old bug reports are incorrectly attached to newer packages. Focal, Bionic and others also have "zombie updates" : update-notifier on Focal, gnome-calculator and nautilus on Bionic. Those last two have been zombified more than one year ago (moreover at the same time it seems). Have a look here : https://people.canonical.com/~ubuntu-archive/phased- updates.html Considering all those first go through proposed, the phasing system is an ultimate security system in case something slipped through, which should happen rarely. -- 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/1913672 Title: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913672] Re: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width
I wonder if it could be a bug related to the crash reporting software instead. What looks strange (but maybe I'm not reading it correctly) is that the publishing history indicates it was brought back to 0% even before it was put at 10% : https://launchpad.net/ubuntu/groovy/amd64 /gnome-shell It seems to me it should at least collect some data before phasing out, so maybe the bug is somewhere else or it has been blocked manually... The qemu package looks affected too, maybe it's not a coincidence that it has been published only a few days before : https://launchpad.net/ubuntu/groovy/amd64/qemu -- 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/1913672 Title: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
Command line apt users may not notice, but the fix has been phased out
the day it was released on updates, and the percentile has been
remaining at 0% since then.
As a consequence, update-manager users won't get the update. Is it
wanted behaviour (i.e. a manual, explicit phase-out), or is there
anything wrong with this fix ?
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
s/crypsetup-initramfs/cryptsetup-initramfs -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Interesting. Just my two (Euro) cents, could that be related to the Nvidia drivers being loaded early in the boot process, and being in the initramfs ? Imho, the only things that should reside in the initramfs are the tools needed for the kernel to get access to the root filesystem, period. No need for fancy graphics before that, and I'm sure even people encrypting their root fs could be happy with an "ugly" password prompt. I mean, fancy graphics are nice, but that's worth nothing if the system is unbootable, and playing with the early boot process shouldn't be done lightly. I too had problems with my system being unbootable after upgrade (related to the Nvidia driver too), and among other things I removed everything that was setting the FRAMEBUFFER initramfs option, because that's what brings the Nvidia driver in the initramfs. I wasn't sure that solved my problem though, but now that I read that removing the splash option from the kernel command line solves a similar problem, I'm thinking about it again... On my laptop, two files were setting the FRAMEBUFFER option : /etc /initramfs-tools/conf.d/splash that was created upon installing the MATE desktop environment, and a configuration hook script that was installed by the crypsetup-initramfs package. I removed the first file and purged the crypsetup-initramfs package, and got no more Nvidia GPU driver in the initramfs ! -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 111939] Re: Not possible to alt-tab during a drag-and-drop operation
** Bug watch added: Xfce Bugzilla #5578 http://bugzilla.xfce.org/show_bug.cgi?id=5578 ** Also affects: xfwm4 via http://bugzilla.xfce.org/show_bug.cgi?id=5578 Importance: Unknown Status: Unknown -- Not possible to alt-tab during a drag-and-drop operation https://bugs.launchpad.net/bugs/111939 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
