Dear Maintainer,

I had to make a laptop for many users with autologin, and wanted to use
Cinnamon. I have used Debian 9 RC2 and the latest updates available on
2017-3-27.

I have seen many times that Cinnamon used 100% CPU after the displaymananger
did the autologin. I've tested with Lightdm and with GDM3. Sometimes Cinnamon
started after some time, sometimes it did not (or my patience was not big
enough).

I have also tested some other desktops with Debian 9 RC2, I did not see this
problems with Mate. Not sure the problem is only there with autologin.

I have also seen other computers and laptops without this problem. I have
tested with 3 different laptops, but all of the type Lenovo Thinkpad X220 with
SSD. It is not really difficult to reproduce, but it's not always there. Maybe
it's a timing-problem.

With regards,
Paul van der Vlis

Hi,

I've seen this problem as well, particularly on intel graphics hardware
but I don't have enough data to be sure if that's the cause.

Anyway, what seems to have helped is disabling the accessibility
settings applet.  It would be helpful if you could try this out and
report whether this helps for you:

gsettings set org.cinnamon.settings-daemon.plugins.a11y-settings active
false

This will disable the plugin.  After that, you would need to logout and
back in enough times to verify that it actually helped.  Could you do
that?

Thanks!

Hello Marga and others,

Op 22-04-17 om 12:54 schreef Margarita Manterola:

I've made a new installation, on a Lenovo Thinkpad X220 with SSD and the
same amount of memory (2x2GB). But I cannot reproduce the problem
anymore. I've tested with the same type of hardware, but not the same
device. The SSD is the same make, but another modell.

What I still hear is a processor-fan what makes noice after logging in,
so the processor is busy. But after a few seconds it's gone. After
giving the gesettings-command I don't see changings in this.

I will do a bit more tests. I did tests with Cinnamon version 3.2.7-2.

With regards,
Paul van der Vlis

I saw the problem today often, and ik lookslike the gsettings command
helped.

But I still have problems reproducing the problem, after a "gsettings
set org.cinnamon.settings-daemon.plugins.a11y-settings active false"
I did not saw the problem anymore.


Paul

Hi Paul,

sorry for the very long delay in answering.

This report is against cinnamon 3.0.4 (jessie-backports) and 3.2.7
(stretch), both long unsupported, and the problem was never reproduced
reliably nor diagnosed: there is no indication of which process was
spinning, and no backtrace.

The most likely trigger back then was the accessibility stack started at
login (which matches Margarita's workaround of disabling the
a11y-settings plugin): at that time the cinnamon package still pulled in
caribou, a known source of CPU spinning together with at-spi2. That
dependency was dropped in cinnamon 6.6.7-1, and the rest of the desktop
has changed considerably since 3.x.

I'm therefore closing this bug. If you still see it on trixie or sid,
please reopen it with the output of top showing the process at 100% CPU
and, if possible, a backtrace of it.

Thanks for the report,
Fabio