Bug#769791: wine32 doesn't work after fresh install

2014-11-30 Thread Michael Gilbert 
control: forcemerge 771104 -1

On Sun, Nov 16, 2014 at 8:38 AM, Andreas Barth wrote:
 wine32 doesn't start anymore after upgrade with a clean directory.
 This is a duplicate of #739863 which had been closed in wine-unstable
 which had been removed from unstable afterwards, so this bug is
 present in testing.

I did a clean install, and found wine not working as described, but
the root cause is #771104 (some missing i386 dependencies), not
#739863.

Best wishes,
Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): Re: Bug#769791: wine32 doesn't work after fresh install

2014-11-30 Thread Debian Bug Tracking System 
Processing control commands:

 forcemerge 771104 -1
Bug #771104 [wine] [wine] wine is no more usable
Bug #769473 [wine] wine: starts in a tiny and inoperable window
Unable to merge bugs because:
package of #769791 is 'wine32' not 'wine'
Failed to forcibly merge 771104: Did not alter merged bugs


-- 
769473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769473
769791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769791
771104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#769791: wine32 doesn't work after fresh install

2014-11-16 Thread Andreas Barth 
Package: wine32
Version: 1.6.2-16
Severity: serious

Hi,

wine32 doesn't start anymore after upgrade with a clean directory.
This is a duplicate of #739863 which had been closed in wine-unstable
which had been removed from unstable afterwards, so this bug is
present in testing.


Andi


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#769791: [pkg-wine-party] Bug#769791: wine32 doesn't work after fresh install

2014-11-16 Thread Stephen Kitt 
Hi Andi,

On Sun, 16 Nov 2014 14:38:09 +0100, Andreas Barth a...@ayous.org wrote:
 wine32 doesn't start anymore after upgrade with a clean directory.
 This is a duplicate of #739863 which had been closed in wine-unstable
 which had been removed from unstable afterwards, so this bug is
 present in testing.

Could you show me what you're doing exactly?

When I do the following:

$ rm -rf ~/.wine-test
$ WINEPREFIX=~/.wine-test wine winecfg
wine: created the configuration directory '/home/steve/.wine-test'
wine: configuration in '/home/steve/.wine-test' has been updated.

the Wine configuration dialog starts correctly...

(This is using wine 1.6.2-16 of course.)

Regards,

Stephen


pgpt4EHbwFcxP.pgp
Description: OpenPGP digital signature

Processed: Re: Bug#769791: wine32 doesn't work after fresh install

2014-11-16 Thread Debian Bug Tracking System 
Processing control commands:

 tags -1 patch
Bug #769791 [wine32] wine32 doesn't work after fresh install
Added tag(s) patch.

-- 
769791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#769791: wine32 doesn't work after fresh install

2014-11-16 Thread jre 
control: tags -1 patch


Hi,

[my answer/patch is based upon the mentioned #739863, otherwise we
really need more info from Andi:]


1.)
this happens in wine-wrapper (regedit, regsvr32, wineboot, winecfg,
winefile, winepath), but not in wine/wine32/wine64.

So wineboot fails with:
  cat: /home/jens/.wine/system.reg: No such file or directory
  /usr/bin/wineboot: 32: exec: wineboot.exe: not found

while wine wineboot or wine32 wineboot work. Instead of wineboot a
normal windows exe also works fine here.



2.)
... and only if $WINEPREFIX/system.reg is missing.

IF WINEARCH is not specified, then $WINEPREFIX/system.reg is used to
figure out which wine to use (wine32 or wine64). After a fresh install
obviously system.reg

With attached patch (taken from #739863) wine-wrapper falls back to
using /usr/bin/wine if system.reg is missing. This will then again
choose wine32, unless WINELOADER is specified.


Of course this is only a fix. In the long run (= wine(-development) post
Jessie) I'd suggest to move all 32/64-bit logic to wine(-development).
So add the system.reg test there, next to the existing WINEARCH and
WINELOADER tests and probably add a PE32+ check (for 64-bit binfmt
support, #769234.) Or should I post a patch for this now?


Mike, the git repository is out of date:
branch jessie is at release 1.6.2-15 (while 1.6.2-16 is current)


Greets
jre
diff --git a/debian/scripts/wine-wrapper b/debian/scripts/wine-wrapper
index 95d2c8f..5c9a3f4 100644
--- a/debian/scripts/wine-wrapper
+++ b/debian/scripts/wine-wrapper
@@ -24,7 +24,11 @@ appname=`basename $0 .exe`.exe
 
 if test -z $WINEARCH; then
 test ! -z $WINEPREFIX || WINEPREFIX=$HOME/.wine
-wine=$(cat $WINEPREFIX/system.reg | grep ^\#arch= | cut -d= -f2 | sed s/win/wine/)
+if test -f $WINEPREFIX/system.reg; then
+wine=$(cat $WINEPREFIX/system.reg | grep ^\#arch= | cut -d= -f2 | sed s/win/wine/)
+else
+wine=/usr/bin/wine
+fi
 else
 wine=$(echo $WINEARCH | sed s/win/wine/)
 fi