@ichudov:
I have the line
*/2 * * * * /usr/bin/killall -q gwibber-service
in my crontab to kill it every 2mins.
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug notification because you are a member of
I'm working on this today since kenvandine is out.
It has been discovered that accessing gnomekeyring from a thread is
causing these CPU problems.
What I am going to do is move the calls to gnomekeyring to before
gwibber-service starts threads and store that data in mlock()'d
memory. Then,
** Branch linked: lp:~nafai/gwibber/gnomekeyring-fix
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I have the same problem, which ruins my battery life. While this is
being worked on, how can I disable this gwibber-service?
thanks
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug notification because
I can also confirm this problem. I'm running Ubuntu 10.04, x86_64 AMD,
kernel 2.6.32-19, gnome 2.30.0
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm running also Ubuntu 10.04 on Linux fuckup 2.6.32-19-generic
#28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux on a Asus
EEEPC and can confirm the problem
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You
Same experience here with gwibber-service. I have only one identi.ca
account set up, gwibber-service will use 100% CPU as soon as it is
running. Can I provide you with useful information somehow or has the
problem already been identified?
--
accessing keyring from python threads sometimes causes
Same here with latest Lucid Gnome Desktop. Only 1 Twitter account added.
Timeline wont update also!
gwibber-service is eating up 100% CPU.
This starts automatically after some time or when i try to reload the Twitter
timeline manually in gwibber.
Please let me know how to help.
--
accessing
@apo - I think dobey tracked the problem down to some thread locking in
gwibber-service, and that @kenvandine is re-working the code. Any help
testing when they are available and providing bug reports and telemetry
if there are any regressions would be really appreciated.
** Changed in: gwibber
I am also having this problem. I am using Ubuntu Lucid Lynx AMD64.
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
confirmed
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42888697/Dependencies.txt
** Changed in: libgnome-keyring (Ubuntu)
Importance: Undecided = High
** Changed in: libgnome-keyring (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
**
** Also affects: gwibber (Ubuntu)
Importance: Undecided
Status: New
** Also affects: desktopcouch (Ubuntu)
Importance: Undecided
Status: New
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received
** Branch linked: lp:~dobey/gwibber/gwibber-keyring-unthreaded
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: gwibber (Ubuntu Lucid)
Importance: Undecided = High
** Changed in: desktopcouch (Ubuntu Lucid)
Importance: Undecided = High
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug
I was going to comment in bug #551326, which is a dupe of bug #530605,
but as Brendan_P comments in the first bug, this doesn't seem related to
samba or gvfs. This report seems to more accurately match my
experience. Here's what I did to cause 100% CPU utilisation on Lucid:
Click the envelope
16 matches
Mail list logo
