This bug was fixed in the package gnome-do - 0.8.4-0ubuntu1
---
gnome-do (0.8.4-0ubuntu1) natty; urgency=low
* The Race Against FF upload. Merge from unreleased Debian git.
Remaining Ubuntu changes:
+ debian/patches/05_disable_resize_grips.patch.diff:
Disable resize h
I can confirm the issue. Ubuntu 10.10 x64. I detected the problem
because my cpu starts to overheat and gnome-do is ussing 700% in system
monitor funny
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
This should be fixed in 0.8.4.
I'll do a little cleaning up in do-plugins, cut another do-plugins
release, and then update the Debian & Ubuntu packages.
** Changed in: do
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can only confirm what has been said in the last comment. I find
exactly the same behavior with Gnome-Do 0.8.3.1 in Ubuntu 10.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/450852
Title:
GNOME-D
I have the same issue as well, 32 bit Maverick & 0.8.3.1+dfsg-2ubuntu1
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
The same trouble here under Maverick (was also the case when I was running
Lucid) with Gnome-Do 0.8.3.1.
Everything runs smoothly, then after a while (could be either minutes or hours,
it depends), Gnome-Do reaches and holds 100% cpu and has to be killed.
--
GNOME-Do uses 200% (two cores) of CP
I have this issue as well - 32 bit Maverick. Freezes on resume from
suspend, going to 200% CPU usage on my Core 2.
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
same here (only on resume).
Chris, any chance to get at least a PPA release soon? There are other fixed
bugs waiting for a long time for a release, too (e.g. bug #531568)...
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification becau
Same here on maverick, 64bit. After resuming from suspend, gnome-do
takes up nearly 800% CPU-Time on my core i7.
After "killall gnome-do" and restarting gnome-do, everything is back to
normal ...
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this b
Possibly related? https://bugs.launchpad.net/ubuntu/+source/gnome-
do/+bug/626308
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
I will just add that I rarely experience this bug except for when I
logout and then log back in (not restart), if I do that it almost always
starts happening (using 0.8.3.1 on Lucid).
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notificati
I'm fairly sure that this has been fixed in trunk. I want to land some
more merge requests, fix a couple more bugs, and then do a new release.
** Changed in: do
Status: Incomplete => Fix Committed
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You receiv
I see this bug and it appears minutes or hours after activating the
banshee plugin. Not having the plugin enabled I don't see the problem,
so in my case it's definately the banshee plugin. (on x64 lucid, but I
had the same problem on x86 karmic with ubuntu-provided versions).
--
GNOME-Do uses 200
gnome-do 0.8.3.1+dfsg-1 on Lucid, when resuming from suspend
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
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.
Same problem, 400% CPU on quad core with gnome-do 0.8.3.1+dfsg-1 on
Lucid. I cannot work out what is triggering the issue; sometimes a
command causes it, but usually it's fine.
** Changed in: gnome-do (Ubuntu)
Importance: Undecided => Medium
--
GNOME-Do uses 200% (two cores) of CPU.
https://b
ppa version fixes this for me. Thanks
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
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
https://list
opps...sry about the status change..
** Changed in: do
Status: Incomplete => Confirmed
** Changed in: do
Status: Confirmed => Incomplete
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of
I also have the same issue, but I am not using Docky.
All I needed to do is install Gnome-do on a fresh Karmik, make it
runnable at startup and reboot two times (the first time it will work
ok).
I confirm what Daniel Tiecher said: "If I open Do after my computer has
fully started this bug does no
try out the ppa: (gnome-do 8.3.1) https://launchpad.net/~do-
core/+archive/ppa
i believe this bug is a duplicate of
https://bugs.launchpad.net/do/+bug/395190, if the ppa fixes your
problems it shurely is
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You receive
I have the same issue. I did a trace on the mono process running gnome-
do and found out that it hangs while trying to read battery info even
though I don't have the battery widget thingie enabled...
I was able to reproduce it 100% by following these steps:
- start gnome-do with docky and without
I have this too on Karmic 64bit, also if I launch manually, and at
random points.
BTW, regarding the remark from comment #1, "the dock will also stall for
some amount of seconds at arbitrary occurrences": This seems to be down
to the battery docklet. At least it has stopped since I deactivated it.
+1
Anything I can help to debug this as its rather annoying. It also
happens on resume from suspend.
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Just want to add that once the CPU spinning begins I have to kill the
process. Then I have to restart it twice; once, kill, then a second
time. The it runs again and seems not to have the CPU problem again.
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You rec
I have this too, and it indeed happens relatively random with full CPU
(and also when I start it manually, so different from #395190). I just
noticed this snippet of stdout:
[Debug 20:56:02.138] NameOwnerChanged: org.bansheeproject.CollectionIndexer, ''
=> ':1.853'
[Debug 20:56:02.138] NameOwnerC
This does NOT affect Xorg! If 1 process eats all of the cpu then other
processes will be starved, there is nothing other processes can do about
it!
** Changed in: xorg-server
Status: New => Invalid
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You recei
** Also affects: xorg-server
Importance: Undecided
Status: New
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
In mi computer with Ubuntu 9.04 64 bits , GnomeDo causes the Xorg
process will block.
output in top:
3299 root 20 0 202m 78m 15m R 100 4.5 10:48.43 Xorg
logically, the graphical session will block.
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
Yo
The hottest bug in our list: bug 395190
GNOME do 0.8.2 use 90% CPU when my computer startup
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@robert: what bug would it be then because looking through the bug list
I could not find anything similar to what I'm experiencing.
Thanks!
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs,
On Sat, 2009-10-17 at 18:14 +, Robert Dyer wrote:
> Please dont change our bug status. We do not yet have all the
> information we need to mark it confirmed. I believe this might be a
> duplicate bug, but your bug description hints that it isnt.
>
> @dj: does this only happen at startup?
>
Sorry about that, I seem to have misunderstood the status system. Won't
happen again.
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
Please dont change our bug status. We do not yet have all the
information we need to mark it confirmed. I believe this might be a
duplicate bug, but your bug description hints that it isnt.
@dj: does this only happen at startup?
@Daniel: that is another bug, not this bug.
** Changed in: do
I'm experiencing this issue on Ubuntu 9.04as well as in 9.10 beta. I've
noticed that it only happens when if choose to start Do on Gnome's
session start. If I open Do after my computer has fully started this bug
does not happen.
i really don't know what kind of debugging information you'll need to
** Changed in: do
Status: Incomplete => Confirmed
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
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.ubun
I do not have the Microblogging plugin enabled.
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
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
ht
** Changed in: do
Status: New => Incomplete
** Changed in: do
Importance: Undecided => Medium
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Also affects: do
Importance: Undecided
Status: New
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
This happens for me, I don't use docky.
** Changed in: gnome-do (Ubuntu)
Status: New => Confirmed
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This has happened since the Upgrade to Karmic Beta. The dock will also
stall for some amount of seconds at arbitrary occurrences, too.
--
GNOME-Do uses 200% (two cores) of CPU.
https://bugs.launchpad.net/bugs/450852
You received this bug notification because you are a member of Ubuntu
Bugs, which
39 matches
Mail list logo
