On Sun, Nov 07, 2021 at 12:28:12PM +0100, Fabio Fantoni wrote: > Il 05/11/2021 17:40, Alex Andreotti ha scritto: > > On Sun, Oct 31, 2021 at 12:28:03PM +0100, Fabio Fantoni wrote: > > > Il 31/10/2021 10:02, Alex Andreotti ha scritto: > > > Sorry if I don't replied before, I'm unable to reproduce the issue on my > > > Sid > > > environment, unfortunately recently I am also very busy and I am used the > > > little time to the tests instead on the big muffin rebase they are doing > > > upstream for cinnamon 5.2. > > > > > > As soon as I have time in these days I will try to prepare the new build > > > with latest upstream bugfixes to upload and doing more tests. > > > > > > About your environments you had some applet,extension, desklet added (not > > > installed by default) and enabled? if yes can you try to disable them, and > > > after reboot the shutdown still have the same issue? without being able to > > > reproduce the problem unfortunately I can not try to debug to try to see > > > what it cause freeze/hang the cinnamon process on shutdown. > > > > > Sorry for the late reply too, my gmail occasionally flags Debian > > emails as spam ... I just happened to see it today. > > > > I don't have custom applets, I just added a couple of auto starts, I > > tried to disable them but nothing changes. > > > > It's not a big deal, I don't reboot often, it's just a little annoying > > because when I do it's because I need it. > > > > It would be useful to have a more precise message, I can try to take a > > look, if you have suggestions where to look are welcome. > > > > Thanks for the work you do. > > Thanks for reply, yesterday I did other tests on Sid testing new bugfix > builds for future upload but I'm still unable to reproduce it. From a fast > search on upstream issues I don't found a similar reports.
I noticed by chance (this is the second time this has happened to me) that the problem does not appear if I have just performed `apt upgrade` and then reboot in the usual way (from the Cinnamon menu). > @Joshua: Have you reproduced it or saw others users report of it with more > informations that can help to reproduce it or found the cause?