Bug 868 - GUI Progress bar sits at 0% until done when using GUI's with none server
Summary: GUI Progress bar sits at 0% until done when using GUI's with none server
Status: RESOLVED FIXED
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: image creator (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.1
Assignee: Joshua Lock - Disabled
QA Contact:
URL:
Whiteboard: Fixed in josh/hob
Depends on:
Blocks:
 
Reported: 2011-03-14 18:44 UTC by Gary Thomas
Modified: 2011-07-01 16:16 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Thomas 2011-03-14 18:44:58 UTC
Running 'bitbake -u hob' hangs with no apparent results when Python < 2.7

Tried this on Fedora 14 (Python 2.7), it starts up
Identical setup on Fedora 13 (Python 2.6.4), just sits there...
Comment 1 Joshua Lock - Disabled 2011-03-15 05:37:45 UTC
I'm going to have to set up a machine to test this.

I have Python 2.7.0 (Fedora 14) and Python 2.6.6 (Ubuntu 10.10) available here and am unable to reproduce.
Comment 2 Gary Thomas 2011-03-15 05:50:47 UTC
bitbake -u gogggle <target> does the same thing with this version of Python
Comment 3 Joshua Lock - Disabled 2011-03-15 08:52:47 UTC
Hmm, I can't repro this exactly. On Fedora 13 with Python 2.6.4 the UI launches but the progress bar sits at 0% until all data is loaded.

This is something to do with the none server as I see the same on Python 2.7.0 on Fedora 14.

Which desktop environment? Do you have pygtk2 installed? We may need to error out with a useful message if people don't have that module available.
Comment 4 Richard Purdie 2011-03-15 08:54:44 UTC
I tested on python 2.6.5 and it works. Do you have all the pygtk+ pieces installed? I'm wondering if there is some issue in that area?
Comment 5 Gary Thomas 2011-03-15 09:11:48 UTC
Looks like I was just impatient.  On a fast machine, it took more than 3 minutes before anything started happening.  With no feedback in the "processing recipes" bar, it seemed to be hung up.
Comment 6 Joshua Lock - Disabled 2011-03-15 09:22:13 UTC
(In reply to comment #5)
> Looks like I was just impatient.  On a fast machine, it took more than 3
> minutes before anything started happening.  With no feedback in the "processing
> recipes" bar, it seemed to be hung up.

Yeah, we (I) definitely need to speed it up.

I'm changing this bug to track the lack of feedback in the progress bar when using the none server.
Comment 7 Joshua Lock - Disabled 2011-04-14 15:14:20 UTC
Not sure if the none server is even relevant for 1.1 but either way this bug should be closed in the next development cycle.
Comment 8 Joshua Lock - Disabled 2011-06-12 16:12:18 UTC
It turns out the hob UI was calling a spurious method which made the mainloop interact badly with Python's threading. It resulted in a few bugs most notably this and another. A patch is in the image-creator development tree to fix this issue pending a merge to master.