http://bugs.winehq.org/show_bug.cgi?id=34213
Bug #: 34213 Summary: winemenubuilder.exe fails every time Product: Wine Version: 1.6-rc5 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: skrinak@gmail.com Classification: Unclassified
Created attachment 45515 --> http://bugs.winehq.org/attachment.cgi?id=45515 Crash report
I brew installed wine 1.6 on a retina MBP running OSX 10.8.4 (Darwin Kernel Version 12.4.0). I installed to run Inno Setup 5 which fails to run. In fact, whenever I run any command, even putty, I get a popup that says: winemenubuilder.exe has encountered a serious problem. Please help!
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #1 from Skrinak skrinak@gmail.com 2013-08-05 19:20:14 CDT --- Note: Also brew installed XQuartz 2.7.4 and gcc compiled wine.
http://bugs.winehq.org/show_bug.cgi?id=34213
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal
--- Comment #2 from Austin English austinenglish@gmail.com 2013-08-06 00:35:03 CDT --- Not a blocker.
Does this happen with a clean WINEPREFIX?
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #3 from Skrinak skrinak@gmail.com 2013-08-06 11:41:01 CDT --- Created attachment 45519 --> http://bugs.winehq.org/attachment.cgi?id=45519 crash log after using clean WINEPREFIX
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #4 from Skrinak skrinak@gmail.com 2013-08-06 12:15:25 CDT --- Created attachment 45522 --> http://bugs.winehq.org/attachment.cgi?id=45522 Did a clean install on a new mac and got the same
I did a fresh brew install on a MBP running 10.7.5 and have pretty much the same result.
http://bugs.winehq.org/show_bug.cgi?id=34213
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #5 from Austin English austinenglish@gmail.com 2013-08-07 17:44:19 CDT --- (In reply to comment #3)
Created attachment 45519 [details] crash log after using clean WINEPREFIX
Thanks, that's bug 34188. There's a patch you can use to fix it.
*** This bug has been marked as a duplicate of bug 34188 ***
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #6 from Skrinak skrinak@gmail.com 2013-08-07 21:14:42 CDT --- Created attachment 45540 --> http://bugs.winehq.org/attachment.cgi?id=45540 No luck with patch
Pretty much exact same behavior post-patch.
http://bugs.winehq.org/show_bug.cgi?id=34213
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ken@codeweavers.com
--- Comment #7 from Austin English austinenglish@gmail.com 2013-08-07 21:20:42 CDT --- cc'ing Ken
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #8 from Ken Thomases ken@codeweavers.com 2013-08-07 21:32:33 CDT --- This doesn't seem like the same behavior. First there was a crash of winemenubuilder. Then there was a failure to create a new wineprefix (bug 34188). You applied the fix patch from that bug and that got you past that, now you have a crash in putty.exe.
Are you able to run regedit? If so, try switching to the X11 driver:
[HKEY_CURRENT_USER\Software\Wine\Drivers] "Graphics"="x11"
If you can't run regedit, then make sure there are no running Wine processes, edit the user.reg file within the wineprefix, and add these lines (similar but not identical):
[Software\Wine\Drivers] "Graphics"="x11"
Does that make things work?
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #9 from Skrinak skrinak@gmail.com 2013-08-08 08:18:23 CDT --- Created attachment 45545 --> http://bugs.winehq.org/attachment.cgi?id=45545 Putty crash log.
That's correct. The winemenubuilder.exe error is now a putty error. The x11 edit did not work completely. I've attached the crash log. My interest is getting Inno to work. I'm opening a new ticket for that.
Thanks again for all your help!
Kris
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #10 from Ken Thomases ken@codeweavers.com 2013-08-08 10:16:16 CDT --- OK. So, it's not related to the Mac driver. Also not a duplicate of bug 34188, although that cropped up.
Are you able to run things other than Putty? Regedit? Notepad?
I suspect it's due to the build. The various Mac compilers have had problems compiling Wine. I know that Apple's gcc-4.2 works. (I also know that MacPorts can install that. Don't know about Homebrew.) That's different from llvm-gcc-4.2, which doesn't work. I know that versions of Clang prior to 3.1 don't work. I'm not certain that more recent versions of Clang do.
In comment 2, you said, "gcc compiled wine". Can you be more specific?
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #11 from Skrinak skrinak@gmail.com 2013-08-08 10:46:47 CDT --- Many thanks for your help.
1st time around I installed with with homebrew using the --use-gcc option. I had to recompile to include the patch so this second time I used the XCode compiler. I did a brew uninstall gcc49 to get it out of the way. This time I used:
$ /usr/bin/gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)
Yes, I'm able to run many apps, just not the ones I need! I can run Notepad and even iexplore (but it throws up a lot).
My objective is to install Inno Setup so I can do a comprehensive build of both mac and windows apps on a java program. I've inherited the build script from a previous developer who seems to have no trouble running Inno on his machine.
I'm happy to pursue the putty issue but I've opened a new bug on Inno: 34231. I want to do what I can to support the community. As both my macs are fresh installs, that is the OS is fresh and so is the wine install, I'm certain I'm not the only one out there experiencing these issues.
Kris
(In reply to comment #10)
OK. So, it's not related to the Mac driver. Also not a duplicate of bug 34188, although that cropped up.
Are you able to run things other than Putty? Regedit? Notepad?
I suspect it's due to the build. The various Mac compilers have had problems compiling Wine. I know that Apple's gcc-4.2 works. (I also know that MacPorts can install that. Don't know about Homebrew.) That's different from llvm-gcc-4.2, which doesn't work. I know that versions of Clang prior to 3.1 don't work. I'm not certain that more recent versions of Clang do.
In comment 2, you said, "gcc compiled wine". Can you be more specific?
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #12 from Ken Thomases ken@codeweavers.com 2013-08-08 10:55:03 CDT --- (In reply to comment #11)
$ /usr/bin/gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)
That's llvm-gcc-4.2. Known not to work for Wine.
At http://wiki.winehq.org/MacOSX/Building#head-f6eb9d865f21b525ac313d62cbb73ca36e07a0a3 it's recommended that you install Apple's gcc-4.2 and specify the use of that when configuring. Give that a try.
http://bugs.winehq.org/show_bug.cgi?id=34213
--- Comment #13 from Skrinak skrinak@gmail.com 2013-08-08 12:26:46 CDT ---
it's recommended that you install Apple's gcc-4.2 and specify the use of that when configuring. Give that a try.
Installed gcc-4.2.1 using these instructions: http://caiustheory.com/install-gcc-421-apple-build-56663-with-xcode-42
$ /usr/local/bin/gcc-4.2 --version i686-apple-darwin11-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
$ export CC=/usr/local/bin/gcc-4.2 $ make clean $ ./configure && make depend && make
From configure output:
checking for gcc... /usr/local/bin/gcc-4.2
After recompile more problems:
$ wine isetup-5.5.3.exe fixme:process:SetProcessDEPPolicy (1): stub
$ wine putty.exe wine: Unhandled page fault on read access to 0xffffffff at address 0x7bc638ce (thread 0009), starting debugger...
http://bugs.winehq.org/show_bug.cgi?id=34213
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Austin English austinenglish@gmail.com 2013-08-08 16:25:37 CDT --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=34213
Ken Thomases ken@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|DUPLICATE | Summary|winemenubuilder.exe fails |Putty crashes |every time | Ever Confirmed|0 |1
--- Comment #15 from Ken Thomases ken@codeweavers.com 2013-08-08 18:00:00 CDT --- Re-opening because it was closed accidentally. Also, not a duplicate.
https://bugs.winehq.org/show_bug.cgi?id=34213
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|REOPENED |NEW URL| |http://www.chiark.greenend. | |org.uk/~sgtatham/putty/down | |load.html CC| |focht@gmx.net
--- Comment #16 from Anastasius Focht focht@gmx.net --- Hello folks,
please avoid switching to different problems in between!
'winemenubuilder' crashing is bug 19241
Please retest 'putty' with a _recent_ Wine version which has been properly built for Mac OS X platform or the bug will be closed abandoned.
Regards
https://bugs.winehq.org/show_bug.cgi?id=34213
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |ABANDONED
--- Comment #17 from Jeff Zaroyko jeffz@jeffz.name --- Resolving abandoned. No response from reporter.
Putty 0.63 works fine here on OS X El Capitan, wine-1.6.1 and wine-1.9.3-217-g0f8a0fd.
https://bugs.winehq.org/show_bug.cgi?id=34213
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #18 from Jeff Zaroyko jeffz@jeffz.name --- Closing abandoned.
-
wine-bugs＠winehq.org