This bug was fixed in the package checkbox - 0.9.2
---
checkbox (0.9.2) lucid-proposed; urgency=low
New upstream release (LP: #567568):
* Added referer when sending submissions to Launchpad (LP: #550973)
* Added suggests to checkbox package in debian/control file (LP: #352740)
Verified fix from checkbox 0.9.2 on Lucid
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553328
Title:
Backend does not get
Hello Marc, or anyone else affected,
Accepted checkbox into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Branch linked: lp:ubuntu/lucid-proposed/checkbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553328
Title:
Backend does not get terminated
To manage notifications about this bug go to:
This bug is awaiting verification that the checkbox version in lucid-
proposed solves the problem. Please test checkbox and update this bug
with the results. If the problem is solved, change the tag
'verification-needed' to 'verification-done'.
See https://wiki.ubuntu.com/Testing/EnableProposed
Hello, the following information should complete this bug as a valid SRU
report, to hopefully upload this fix to Lucid.
Solution:
Checkbox revision 796 addresses this by Closing fifo descriptors so that
backend can get terminated.
TEST CASE:
1- Perform a fresh installation of 10.04 and do a
** Branch linked: lp:~roadmr/ubuntu/lucid/checkbox/0.9.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553328
Title:
Backend does not get terminated
To manage notifications about this bug go to:
Clean new Ubuntu 10.04.2 latest updates. still exists
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553328
Title:
Backend does not get terminated
--
ubuntu-bugs mailing list
** Changed in: checkbox (Ubuntu)
Assignee: Marc Tardif (cr3) = Vistavnoy Roman Valentinovich (rvystavnoy)
** Changed in: checkbox (Ubuntu)
Assignee: Vistavnoy Roman Valentinovich (rvystavnoy) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Still happening on Ubuntu 10.04 LTS 2.6.32-29-generic-pae #58-Ubuntu. I
started the System Testing program, checked what tests it would perform
and then closed it without performing any tests. I did not notice any
system slowdowns but noticed when I started system monitor that I had
one core @
** Changed in: checkbox (Ubuntu Lucid)
Status: In Progress = Fix Committed
** Changed in: checkbox (Ubuntu Lucid)
Status: Fix Committed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Silviu
As a workaround, please see #34 to get an update from the checkbox-
developers PPA with the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553328
Title:
Backend does not get terminated
Installed Ubuntu 10.04.2 LTS GNU/Linux x86_64 2.6.32-28-server #55-Ubuntu SMP
Mon Jan 10 23:57:16 UTC 2011.
Went through System Testing and exited after completing the test. Found after 5
minutes the fan was running continuous, and top showed one backend
processes consuming 100% cpu. Manually
I'm having this problem as of late. It's taking up 101%... I have 400%
available. I have one core being continuously taxed by Ubuntu One.
The one piece of non-free software I have on my computer and it is
hogging up processor.Canonical, fix your shit. This is rediculous.
One problem
I've found this backend process running at almost 100% in my Linux roger-eeepc
2.6.32-27-generic #49-Ubuntu SMP Wed Dec 1 23:52:12 UTC 2010 i686 GNU/Linux
I only became aware of this because the computer was too slow.
Is there a way to set an alert when this 100% cpu usage happens?
I'm not quite
Would changing the importance of this bug from undecided to high help
make it more visible to the lucid packagers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553328
Title:
Backend does not get
A fix was apparently committed in June of last year. Lucid still has the
problem. What happened to the `pending review' that was supposed to
happen in August. Does somebody need a gentle reminder - a.k.a. - kick
in the pants.
This is a pretty serious problem potentially shortening the life of
I don't know when the fix will get to the Lucid repositories. However, in the
meantime, I've uploaded a package to checkbox-developers PPA:
https://launchpad.net/~checkbox-dev/+archive/ppa
The package contains the latest version of the code so it has not only
the fix you are looking for, but
Thanks for that Javier. I appreciate your effort. The checkbox
developers have done all that can be expected of them by fixing the bug
promptly. It is the Lucid package maintainers who seem to have dropped
the ball.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I just ran in this problem. Same problem: 100% of one of the CPUs used.
I could just kill the process and got everything back to normal.
--
Backend does not get terminated
https://bugs.launchpad.net/bugs/553328
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Me too, me too, and after a while the fan starts to blow because I guess the
CPU is overheating.
But here is the real weird thing - when all this is happening, it is the only
time my hsf modem connects properly.
--
Backend does not get terminated
https://bugs.launchpad.net/bugs/553328
You
Same issue, system up to date as of today. Started in core1 then core 2
and stayed in core 3 until I killed it. I was looking for system
monitor and started system testing by mistake.
--
Backend does not get terminated
https://bugs.launchpad.net/bugs/553328
You received this bug notification
unsubscribing ubuntu-sponsors. Please resubscribe the team once Mathias'
concerns are addressed.
** Changed in: checkbox (Ubuntu Lucid)
Assignee: (unassigned) = Benjamin Drung (bdrung)
** Changed in: checkbox (Ubuntu Lucid)
Assignee: Benjamin Drung (bdrung) = (unassigned)
** Changed
Bug is still extant in 10.04 with latest updates, incl. ubuntu-proposed.
--
Backend does not get terminated
https://bugs.launchpad.net/bugs/553328
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Guys, read the statuses abroad and the comments
* bug is fixed in upstream
* fixed in developer branch
* not yet merged in lucid due to a pending review:
** https://code.launchpad.net/~cr3/ubuntu/lucid/checkbox/0.9.2/+merge/28341
* you can use the ppa:cr3/ppa repository if you can't wait for the
Just fresh installed 10.04 LTS today...same as Nixloz. Went into System
Testing twice, Networking only, to see what my wireless card was on my
X31, and exited out without completing the test. Found after 5 minutes
the fan was running continuous, and top showed two backend processes
consuming
I only opened the system testing app, but never really started it.
the backend continued after closing the app though, causing one of the 2 cores
to be at 100% all of the time (occasionally switching core).
--
Backend does not get terminated
https://bugs.launchpad.net/bugs/553328
You received
I've verified that 0.9.2 fixes the 100 CPU issue. (for those who can't
wait the merge into lucid, use the ppa:cr3/ppa repository)
But I wonder if the fix isn't just a workaround of a gksu problem.
Because ggksu doesn't seem to handle signals properly. I.e. killing the
gksu process doesn't kill
Problem still remains (started when upgraded 10.04). :(
Sudo killing the process still leaves the system monitor applet with at least
60% cpu usage, though the processes shown in htop (or top) dont stack up to
this percentage... No reboots fix the issue either.
$ ps -eo pcpu,args|sort -rn|head
I can confirm the same bug on my Lucid 10.04 install.
One additional detail, if I click through to see the tests that are
about to run, but choose not to run the tests by clicking the Next
button and instead close the System Tests at that point (after it has
gathered system information, but
Fresh install of Lucid on desktop PC here, same issue, killing backend.
Frustrating! I thought Ubuntu was ready for the mainstream by now.
--
Backend does not get terminated
https://bugs.launchpad.net/bugs/553328
You received this bug notification because you are a member of Ubuntu
Bugs, which
$ ps -e -F w -T | grep backend
root 6567 6567 1 92 2044 4460 3 14:54 ?Rs 108:00
/usr/bin/python /usr/share/checkbox/backend /tmp/checkboxAAgvr7/input
/tmp/checkboxAAgvr7/output
1000 7389 7389 7358 0 835 932 1 16:51 pts/1S+ 0:00 grep
--color=auto
Same problem after test, backend 99%. After sudo kill it back to normal.
--
Backend does not get terminated
https://bugs.launchpad.net/bugs/553328
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: checkbox (Ubuntu)
Importance: Undecided
Status: New
** Also affects: checkbox (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: checkbox (Ubuntu)
Status: New = Fix Released
** Changed in: checkbox (Ubuntu Lucid)
Status: New = In
** Description changed:
+ The impact of this bug is that when checkbox finished, the backend keeps
+ running forever while consuming processing power the whole time. This
+ fix simply makes sure that the backend finishes when the frontend
+ finishes too.
+
When Checkbox is stopped, the
35 matches
Mail list logo
