Ticket #128 (reopened defect)

Opened 14 months ago

Last modified 2 months ago

Empty Winetricks

Reported by: xjeff Owned by: mike
Priority: critical Milestone: 1.2.3
Component: WineStatus winetricks Version: 1.2.3
Keywords: Cc: rocking_benny, 2xAA, codeman38, linxet, NielsR, kpm13579, asavage, tsigo, ciriux, Chris, lkraav, Michael, mihawk90

Description

I installed WineBottler (v1.1.44) on my Macbook Pro with Mac OS X (v10.6.6). When I tried to create a custom prefix, I found the Winetricks list box is empty. I updated Wine to v1.2.2 and found the issue persists.

Change History

comment:1 Changed 14 months ago by rocking_benny

  • Cc rocking_benny added
  • Priority changed from major to critical

Same problem, in wine as well as in winebottler. Some weeks ago it worked perfect. Perhaps an os x update issue. Reinstalled XQuartz and deleted all caches with no effect.

comment:2 Changed 14 months ago by 2xAA

  • Cc 2xAA added

Same problem here, only noticed it today ):

comment:3 Changed 14 months ago by jwfranks

Same Problem. New install blank winetricks list.

comment:4 Changed 14 months ago by codeman38

Same thing just happened here when I tried to create a new Wine bottle. Guessing it's probably related to some recent OS update, though I know not which.

comment:5 Changed 14 months ago by codeman38

  • Cc codeman38 added

comment:6 Changed 14 months ago by edoardo

same for me macbook pro 10.6.7 on first start of 1.1.44 I updated wine to 1.2.2 the list of winetricks is always empty

comment:7 Changed 14 months ago by amarolima

the same happened to me. Macbook 10.5.8. First i tried winebottlerCombo_1.1.44.dmg without updating wine, as it did not work, I remove it all and tried to install again, now updating wine 1.1.2, but still did not work. Somehow winetricks can not be installed. Interestingly a similar problem happens trying to install winetricks directly from macports.

Last edited 14 months ago by amarolima (previous) (diff)

comment:8 Changed 14 months ago by linxet

The same for me. I'm on 10.7 (I don't recommend to install it, it's plenty of bugs, but it's really pretty) but in 10.6.7 doesn't work either. I tried to reinstall all and erasing all folders with no success. I think is some file that i could't find, because i downloaded the version 1.1.35 and it doesn't work either.

comment:9 Changed 14 months ago by linxet

  • Cc linxet added

comment:10 Changed 14 months ago by NielsR

  • Cc NielsR added

comment:11 Changed 14 months ago by Exeman

  • Version changed from 1.1.44 to 1.2

The same problem here. iMac '27 10.6.6. I guess this happens because of the changes in winetricks 20110311, particularly "the menu has been broken up into sections (it was getting too big)". Does winetricks update automatically, BTW?

comment:12 Changed 14 months ago by Exeman

  • Version changed from 1.2 to 1.1.44

Oh, sorry, ocassionally changed the version.

comment:13 Changed 14 months ago by kpm13579

  • Cc kpm13579 added

Same thing here.

Mac OS X 10.6.6

Wine 1.2

WineBottler 1.1.44

MacBookPro8,2

Intel Core i7

Last edited 14 months ago by kpm13579 (previous) (diff)

comment:14 Changed 14 months ago by asavage

  • Cc asavage added

comment:15 Changed 14 months ago by tsigo

  • Cc tsigo added

Same problem here. Wine.app 1.1.44 and 1.2, Mac OS X 10.6.6, MacPro? 4,1

comment:16 Changed 14 months ago by ciriux

  • Cc ciriux added
  • Version changed from 1.1.44 to 1.2

Same problem here, MacBook? Pro 13 early 2011 empty winetricks.

comment:17 Changed 14 months ago by robotguy4

Ditto.

I first noticed the problem after I updated Mac OS X, but I can't be certain if this was the thing that started the problem as I wasn't using wine for a few weeks. I updated Mac OS X and X11 from http://xquartz.macosforge.org/trac/wiki.

Using Wine v 1.2 Mac OS 10.5.8 Intel Core 2 Duo

Also, not sure if this makes a difference, but when I press apply (FYI: apparently you can apply nothing!) one of the lines on the "All messages" section of the Console reads:

4/3/11 3:56:06 PM Wine[50368] DIPSPLAY.....................: /tmp/launch-UOMYuB/org.x:0

Is "DIPSPLAY" a typo?

comment:18 Changed 14 months ago by Chris

  • Cc Chris added

comment:19 Changed 13 months ago by lkraav

at first sight this seems to be caused by not setting $WINE correctly in the scripts. WINE={$WINE:-wine} doesn't seem very sane to me, is "wine" supposed to somehow magically get into PATH by just dragging some .apps into /Applications?

try:

cd /Applications/WineBottler.app/Contents/Resources
WINE=/Applications/Wine.app/Contents/Resources/bin/wine sh winetricks.sh <yourtrick>

comment:20 Changed 13 months ago by lkraav

  • Cc lkraav added

comment:21 Changed 13 months ago by rocking_benny

doesnt really understand what to do... Should I apply the tricks via commandline or do I just have to set the WINE PATH?

comment:22 Changed 9 months ago by robotpriest

Maybe Winebottler could include the binary for Zenity and when you select Winetricks, it would just launch the normal Winetricks GUI.

comment:23 Changed 6 months ago by Michael

  • Cc Michael added

comment:24 Changed 3 months ago by mike

  • Status changed from new to closed
  • Version changed from 1.2 to 1.1.44
  • Resolution set to fixed
  • Milestone changed from uncertain to 1.2.3

comment:25 Changed 3 months ago by mihawk90

  • Cc mihawk90 added
  • Status changed from closed to reopened
  • Version changed from 1.1.44 to 1.2.3
  • Resolution fixed deleted

Despite being "closed" and "fixed" for 1.2.3 the problem still persists for me, is it only me?

Using completely reinstalled Wine and WineBottler using RemoveWineBottler on mac OS X.5.8 (yeah quite old I know). No files containing "wine" were found on spotlight

Used latest available WineBottlerCombo? for installing

Last edited 3 months ago by mihawk90 (previous) (diff)

comment:26 Changed 2 months ago by mihawk90

I have absolutely no idea what happened, I didn't change anything (because I was out of ideas), but now winetricks appear again and also predefined prefixes are showed again

No idea what happened and I'm completely confused o.O

Note: See TracTickets for help on using tickets.