I don't know you guys are looking for the issues opened on Github (https://github.com/lxde/menu-cache/issues/) - currently there are 5 reported there, but I'd like to report specifically for the menu-cached process using 100% of CPU (we also have an issue opened on Github for this with lots of comments: https://github.com/lxde/menu-cache/issues/7).
I'm using a brand new installation of Lubuntu 16.10 in my laptop.
I noticed the machine temperature was too hot (96 degrees!!!) so I took a look on top and the menu-cached was the guilty. I killed it and everything was as usual again.
I just don't know if it was because I returned from the suspended mode or if it's because I tried to run a custom command with "Open With". I did both in sequence/same session.
$ dpkg -l |grep -iP "menu.*?cache"
ii libmenu-cache-bin 1.0.1-1build1 amd64
ii libmenu-cache3:amd64 1.0.1-1build1 amd64
Hey all,
I don't know you guys are looking for the issues opened on Github (https:/ /github. com/lxde/ menu-cache/ issues/) - currently there are 5 reported there, but I'd like to report specifically for the menu-cached process using 100% of CPU (we also have an issue opened on Github for this with lots of comments: https:/ /github. com/lxde/ menu-cache/ issues/ 7).
I'm using a brand new installation of Lubuntu 16.10 in my laptop.
I noticed the machine temperature was too hot (96 degrees!!!) so I took a look on top and the menu-cached was the guilty. I killed it and everything was as usual again.
I just don't know if it was because I returned from the suspended mode or if it's because I tried to run a custom command with "Open With". I did both in sequence/same session.
$ dpkg -l |grep -iP "menu.*?cache" cache3: amd64 1.0.1-1build1 amd64
ii libmenu-cache-bin 1.0.1-1build1 amd64
ii libmenu-
Thanks