Summary: | app-emulation/wine 1.3.x: file open / save dialog broken after reemerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Quasimodo <quasi> |
Component: | Current packages | Assignee: | Wine Maintainers <wine> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | antonbaklanov |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info on amd64
emerge --info on x86 emerge --info |
Description
Quasimodo
2010-09-23 11:29:46 UTC
emerge --info please Created attachment 248505 [details]
emerge --info on amd64
As you wished, here is my emerge --info from my amd64 machine
Created attachment 248506 [details]
emerge --info on x86
And from my x86 machine
I have exactly the same problem have the same problem Created attachment 248529 [details]
emerge --info
i've reverted wine to 1.1.44 and deleted my ~/.wine and it does not fix the problem.
I'm having the same problem here. if you remove the wine-1.3-shell32-fortify.patch, does it make a difference ? (In reply to comment #8) > if you remove the wine-1.3-shell32-fortify.patch, does it make a difference ? will try it tomorrow, thanks Removing that patch from the ebuild fixes it for me. Now I have some very conflicting feelings about this. On the one hand I am glad this bug is resolved, on the other hand I am very disappointed that I have spent hours splitting hairs inspecting my emerge logs, recompiling my toolchain and recompiling wine numerous times with different settings and generally be confused to no end because __every Wine ebuild has been modified yet their version remained the same__. This is a terrible practice. I haven't checked Gentoo's guidelines regarding ebuilds but I thought that in ebuilds, the number after "-r" meant "revision" and I expected that everytime an ebuild is modified that number would be increased. So yeah, no wonder that downgrading to Wine 1.3.2 would not fix it, the last working wine-1.3.2.ebuild doesn't exist anymore, it's been replaced with a broken wine-1.3.2.ebuild. Please don't ever alter an ebuild again without changing its number. Thanks. I was experienced the same problem on a ~amd64 Gentoo. Removing wine-1.3-shell32-fortify.patch fixes the problem. ive dropped the fortify patch then. back to the drawing board in bug 336887. |