dos-box is shown while bazaar explorer is executing

Bug #433781 reported by Oscar Fuentes on 2009-09-21
64
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Gary van der Merwe
Bazaar Windows Installers
Undecided
Gary van der Merwe

Bug Description

On Windows XP, when bazaar-explorer is executed a console dos-box window is created and remains open until the application is closed.

Most likely, this is due to compiling bazaar explorer as a terminal application, not as a graphical (aka windows) application.

Related branches

Ian Clatworthy (ian-clatworthy) wrote :

This is more a packaging issue than something directly related to explorer so I'll switch the project accordingly.

affects: bzr-explorer → bzr-windows-installers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ian Clatworthy wrote:
> This is more a packaging issue than something directly related to
> explorer so I'll switch the project accordingly.
>
> ** Project changed: bzr-explorer => bzr-windows-installers
>

Sort of. I've poked around at this, but unfortunately it seems that
py2exe doesn't like PyQt 4.5.2 so I can't get things to build on my machine.

Specifically, 4.5.2 seems to have some python v3 code, and uses a
'sys.version' check to load the right subset.

If I just try to build, then py2exe dies because it can't import the
code. If I add the py3k code to an exclude list, then py2exe dies while
trying to 'load_tail' because it thinks the code doesn't exist. I
haven't figured out a way for it to not find the code and *not think*
that it wants it.

Anyway, we basically need a new target, so that instead of linking to
"bzr" and passing "explorer" as an argument, we link directly to a
"bzr_explorer.exe" that doesn't want a console.

Though I'll also note that until recently, we still prompted for
passwords in the DOS box, so I'd want to make sure all those bugs are
fixed, before we start silently hanging and giving no indication of what
to do.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq3lRoACgkQJdeBCYSNAAPp8QCgtBT2VqQ6HFsaMXSCVVSvikb+
AvoAn3aWH5GuGz0QKXUo7klfKbfhtblA
=46xn
-----END PGP SIGNATURE-----

Changed in bzr-windows-installers:
status: New → Confirmed
Gordon Tyler (doxxx) wrote :

Inada Naoki posted to the bzr windows list a little while back with a non-console version of bzr.exe called bzrw.exe, which worked fine for me.

Skrebbel (skrebbel) wrote :

A simple workaround is the following:

Make a file <program files>/Bazaar/bzrExplorer.js with:

  var WS_HIDDEN = 0;
  var shell = WScript.CreateObject("WScript.Shell");
  shell.Run("cmd /c bzr.exe explorer", WS_HIDDEN);

Add a shortcut to this .js file to the start menu (optionally with the icon of bzr.exe).

IMHO this might in fact also be a simpler and cheaper solution than including a second executable (either bzrExplorer.exe or bzrw.exe). You add a depencency to the Windows Scripting Host though (but afaik it is pretty ubiquitous).

Alexander Belchenko (bialix) wrote :

Skrebbel пишет:
> A simple workaround is the following:
>
> Make a file <program files>/Bazaar/bzrExplorer.js with:
>
> var WS_HIDDEN = 0;
> var shell = WScript.CreateObject("WScript.Shell");
> shell.Run("cmd /c bzr.exe explorer", WS_HIDDEN);
>
> Add a shortcut to this .js file to the start menu (optionally with the
> icon of bzr.exe).
>
> IMHO this might in fact also be a simpler and cheaper solution than
> including a second executable (either bzrExplorer.exe or bzrw.exe). You
> add a depencency to the Windows Scripting Host though (but afaik it is
> pretty ubiquitous).
>

Looks interesting.

Alexander Belchenko (bialix) wrote :

Skrebbel пишет:
> A simple workaround is the following:
>
> Make a file <program files>/Bazaar/bzrExplorer.js with:
>
> var WS_HIDDEN = 0;
> var shell = WScript.CreateObject("WScript.Shell");
> shell.Run("cmd /c bzr.exe explorer", WS_HIDDEN);
>
> Add a shortcut to this .js file to the start menu (optionally with the
> icon of bzr.exe).
>
> IMHO this might in fact also be a simpler and cheaper solution than
> including a second executable (either bzrExplorer.exe or bzrw.exe). You
> add a depencency to the Windows Scripting Host though (but afaik it is
> pretty ubiquitous).

I've added your JS to explorer sources. Now we should properly use it
from our installer(s).

Gary van der Merwe (garyvdm) wrote :

A fix for this has landed in lp:bzr/2.2. It will be included in the next installers.

Changed in bzr-windows-installers:
assignee: nobody → Gary van der Merwe (garyvdm)
status: Confirmed → Fix Committed
John A Meinel (jameinel) on 2010-08-06
Changed in bzr:
assignee: nobody → Gary van der Merwe (garyvdm)
importance: Undecided → Medium
milestone: none → 2.2.0
status: New → Fix Released
Changed in bzr-windows-installers:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions