selected branch fails to download

[Brian Dunnette]

Binary package hint: groundcontrol

Ubuntu 10.04
Ground Control 1.6.5-1

Expected Behavior:
Click "Fetch Branch", select branch & local name; branch content downloads to project folder

Actual Behavior:
Click "Fetch Project", select project -- project folder is created
Browse to project folder
Click "Fetch Branch", select branch & local name; "Retrieving Data" dialog appears, but no data is downloaded

[Martin Owens (doctormo)]

Does this problem appear in 1.6.6 which is available in Debian and the ppa?

https://edge.launchpad.net/~doctormo/+archive/groundcontrol

[Brian Dunnette (bdunnette)]

Yes -- the same behavior occurs after upgrading to 1.6.6 via the PPA.

[Martin Owens (doctormo)]

OK so it's reproducible and your using the latest, I will need to get you to run from the command line and give me a log here so I can understand what is going on. Right now your instructions work on my machine.

touch ~/groundcontrol.log
nautilus --quit; nautilus --no-desktop

Then reproduce your error, you may have to try it more than once to get the result in the log.

[Brian Dunnette (bdunnette)]

Hmm... from the log, it appears that it's failing when looking for a Python module named "winrandom"?

Full log is attached, including two failed attempts to download branches...

[Luke Faraone (lfaraone)]

On 09/02/2010 06:48 PM, Brian Dunnette wrote:
> Hmm... from the log, it appears that it's failing when looking for a
> Python module named "winrandom"?
>
> Full log is attached, including two failed attempts to download
> branches...
>
> ** Attachment added: "groundcontrol.log"
> https://bugs.launchpad.net/groundcontrol/+bug/627172/+attachment/1538199/+files/groundcontrol.log
>
From the log, it looks like the issue is that the Crypto module is
importing winrandom, which is a Windows-only library. Normally, this
import would fail and the module would go onto an alternative.

I think hg tries to speed up its runtime by delaying Python imports
until the imported code is used. This breaks the behavior of some
modules, because they depend on imports of non-extant modules to fail
during import, not usage.

--
╒═════════════════════════════════════════════════════════════════╕
│Luke Faraone ╭Debian / Ubuntu Developer╮│
│http://luke.faraone.cc ╰Sugar Labs, Systems Admin╯│
│PGP: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 │
╘═════════════════════════════════════════════════════════════════╛

[Martin Owens (doctormo)]

Luke: Yes that's what I thought. I gave this branch a download last night myself and it worked perfectly on Ubuntu 10.04 i386 with 1.6.6 from the ppa. So this error must be something to do with some package installed on Brian's machine.

Brian can you confirm?

[Andrei Dziahel (adziahel.synesis)]

Affects me at groundcontrol 1.6.7 from ppa.
attached log mentions winrandom module.

[Andrei Dziahel (develop7)]

@doctormo, have you tried to reproduce this bug after installing mercurial?

[Martin Owens (doctormo)]

@Andrei - Yes, I just installed mecurial on ubuntu 10.10 and tried to download the branch shown in the logs. No error occurred :-(

[Jan Girlich (vollkorn)]

I can confirm this bug, too. I run the latest Ubuntu 10.10 with the ground-control 1.6.6-1 from the repositories.
Same error message, mercurial was installed all the time.

Running
touch ~/groundcontrol.log
nautilus --quit; nautilus --no-desktop

Lead to hundreds of nautilus windows opening and pestering my taskbar, but the windows were not clickable nor alt-tab helped reaching them. Console output was:
jan@jan-x61:~$ touch ~/groundcontrol.log
jan@jan-x61:~$ nautilus --quit; nautilus --no-desktop
Initializing nautilus-image-converter extension
Initializing nautilus-gdu extension
Bazaar nautilus module initialized
Initializing groundcontrol-1.6.6 extension
Initializing nautilus-dropbox 0.6.7
sys:1: GtkWarning: IA__gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed

[Jan Girlich (vollkorn)]

Oh, I got some output! Hinting at SSL problems. See attached logfile.

[Jan Girlich (vollkorn)]

And here goes groundcontrol.log, but it reveals no news.