[Bug 717348] Re: Caused X to crash and kept using 100% after relogging in

2011-02-22 Thread Sebastien Bacher
If you get the issue again it would be interesting to use dbus-monitor to see if one of the indicator is generating traffic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717348 Title: Caused X to cr

[Bug 717348] Re: Caused X to crash and kept using 100% after relogging in

2011-02-22 Thread Sebastien Bacher
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future. ** Changed in: indicator-applicat

Re: [Bug 717348] Re: Caused X to crash and kept using 100% after relogging in

2011-02-18 Thread Vadim Peretokin
Just happened once and out of the blue. Not sure how to reproduce it, besides possibly using the virtualbox indicator and the cpufreq one, because the virtualbox one with time will steal cpufreq's icon and use it as its own. -- You received this bug notification because you are a member of Ubuntu

[Bug 717348] Re: Caused X to crash and kept using 100% after relogging in

2011-02-18 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: indicator-applic

[Bug 717348] Re: Caused X to crash and kept using 100% after relogging in

2011-02-11 Thread Vadim Peretokin
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/bugs/717348/+attachment/1843765/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717348 Title: Caused X to crash and k