[Desktop-packages] [Bug 1631851] Re: Chromium taking 150% cpu after page load

2016-10-11 Thread lemonsqueeze
Moved to bugs.chromium.org, can close this one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1631851 Title: Chromium taking 150% cpu after page load Status in chromium-bro

[Desktop-packages] [Bug 1631851] Re: Chromium taking 150% cpu after page load

2016-10-10 Thread lemonsqueeze
Can replicate in regular Ubuntu 16.04.1 LiveCD if Unity is not running: Boot LiveCD, kill Unity and switch to minimal desktop as in: http://askubuntu.com/questions/833868/way-to-run-ubuntu-livecd-without-unity/833962#833962 Start Chromium from there and open facebook page, takes 150% cpu after pa

[Desktop-packages] [Bug 1631851] Re: Chromium taking 150% cpu after page load

2016-10-10 Thread lemonsqueeze
Xubuntu 16.04 is affected as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1631851 Title: Chromium taking 150% cpu after page load Status in chromium-browser package

[Desktop-packages] [Bug 1631851] [NEW] Chromium taking 150% cpu after page load

2016-10-09 Thread lemonsqueeze
Public bug reported: - Open https://www.facebook.com/U2 - Chromium continues to take 150% cpu after page finishes loading. Running Ubuntu 14.04 Mate desktop here. This happens with latest Chromium 53.0.2785 package and earlier versions as well. I can replicate the issue in Ubuntu Mate 14.04 and

[Desktop-packages] [Bug 580437] Re: wvdial returns with Huawei E160E error NO CARRIER

2013-01-03 Thread lemonsqueeze
I was having a similar issue with a Huawei E1762. It seems the modem was getting confused when wvdial starts talking to it before it's finished registering. -> using a script to wait until the device is registered before running wvdial solved it ! details here: http://superuser.com/questions/52