<html>Hi ! Thanks for your quick followup<br /><br />> Control: tags -1 + moreinfo<br />><br />> On Fri, 10 May 2024 at 12:08:27 +0200, Julien Negros wrote:<br />> > In Bookworm last gnome-shell upgrade 43.9-0+deb12u1 -> 43.9-0+deb12u2<br />> > closes current logged session. Same issue with Bullseye<br />> > (3.38.6-1~deb11u1 -> 3.38.6-1~deb11u2). Doesn't look like an actual<br />> > crash in logs : [...] But rather a GDM restart.<br />><br />> I did not experience this when upgrading several bookworm GNOME machines,<br />> and one bullseye virtual machine. My GNOME session continued to run until<br />> I rebooted the machine manually.<br />><br />> In general I would recommend rebooting the system anyway after installing<br />> security updates in core library packages like libglib2.0-0, otherwise<br />> running programs and sessions will remain vulnerable.<br /><br />I agree but the issue here is having the session closed when doing a simple apt upgrade...<br /><br />> Are you sure you were not using some tool like checkrestart or needrestart<br />> that detected gdm3 as a service that was affected by the security-fixed<br />> versions of libglib2.0-0, and offered to restart it for you?<br />><br />> In needrestart's default configuration, it will default to not<br />> restarting gdm3 and other known display managers (this is set up in<br />> $nrconf{override_rc}, in /etc/needrestart/needrestart.conf), but if they<br />> are explicitly selected to be restarted, it will assume you are aware of<br />> the consequences and do as you ask.<br /><br />needrestart and debian-goodies are not installed in our workstations, but we use needrestart on our servers so I'm familiar with the use of this tool. That could have been a lead though.<br /><br />> I don't know whether checkrestart has similar mechanisms.<br />><br />> If you *do* restart gdm3, then it is probably expected that active GUI<br />> sessions managed by gdm3 will be terminated - that's why needrestart avoids<br />> doing this by default.<br />><br />> smcv<br /><br />If you are not affected by this there must be something specific with out setup (we do all kind of tweaks to our Debian installations), that would also explain why I can't find any complain online since Monday... But I have no clue what it could be. If you or anyone has any idea where to look that would be great :)<br /><br />--<br />Julien Negros<img src="https://u23627639.ct.sendgrid.net/wf/open?upn=u001.LNwQNwtlYkE35OrPhNTjdZDmx3YlHNf6kWHmkf8yGbGkNbFaxrrI1-2BWrzfQPsymilOco1NPgsgTbFOlQxD-2BuYfY3ZGcM3PC1gv66m1UWkpFaxZQbTUUBzIIeuLfO0CdjkoS6Sq8bPSP2siL800pPEFs-2F8wJYp7ADJf1za7-2ByN8xKH5-2BVsJvnfeKPwc8Xt6MlLERI9kb-2BBqKgTtE-2FQnlE5bzb68hmYZVZh3oD1bmiMxs-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/></html>