October 2007 - Wine-bugs - list.winehq.org

[Bug 8033] TOPO 4.2.7: Unhandled Page Fault Using
by wine-bugs＠winehq.org 07 Oct '07

07 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #39 from James Hawkins <truiken(a)gmail.com> 2007-10-06 19:27:39 --- (In reply to comment #38) > (In reply to comment #37) > > It sounds like you're adding registry entries > > from Windows to make the app work in the first place. Is that the case? > > Of course not; the missing registry entries were presumably installed by either > the application itself or its installation process. (It's Windows - Windows > applications do that sort of thing!) > What missing registry entries? Are you copying over the app installation from a Windows install? > And yes, this is a regression of sorts in that I installed the application with > Wine 0.9.3x and it broke when I upgraded to Wine 0.9.35. The fix posted in bug > #8033 kept me running until 0.9.42 was released and then bug #9147 broke it > again. > > > Keeping a wineprefix between version is extremely common, but you miss the > > point that it's not guaranteed to work. > > No, I get that it's not guaranteed to work. It's the "(lack of) what happens > next" that I am having trouble with. In particular, your "sanitized" wineprefix > approach that just looks like a back-handed way of telling your users to go > away and reinstall all their applications. > > If you're going to create mandatory registry entries in Wine that will make > Wine crash/explode if they're not present then you need to find a way to update > the .reg files in users' .wine/ directories too. Or put all these critical > entries into an unmodifiable wine.reg file that every wine installation loads > at start up. Or SOMETHING. What mandatory registry entries are you talking about? Registry entries are created *only* when you run wineprefixcreate, so you have to remove the old .wine and generate a new .wine. This also gets rid of any cruft from installing other apps that may interfere with the bug (installation and uninstallation in Wine is not complete and that's another reason why this is the policy). > Because no-one who installs Wine as binary packages > is *ever* going to be interested in recreating his/her .wine directory each > time they update. E.g. do you have any idea how much work is involved to > install World of Warcraft, with all of its patches and expansion packs? > Do you read what I say? $ mv .wine .wine-save $ wineprefixcreate $ test app $ mv .wine-save .wine voila! Your old apps are back... -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 8033] TOPO 4.2.7: Unhandled Page Fault Using
by wine-bugs＠winehq.org 07 Oct '07

07 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #38 from rankincj(a)yahoo.com 2007-10-06 19:18:52 --- (In reply to comment #37) > It sounds like you're adding registry entries > from Windows to make the app work in the first place. Is that the case? Of course not; the missing registry entries were presumably installed by either the application itself or its installation process. (It's Windows - Windows applications do that sort of thing!) And yes, this is a regression of sorts in that I installed the application with Wine 0.9.3x and it broke when I upgraded to Wine 0.9.35. The fix posted in bug #8033 kept me running until 0.9.42 was released and then bug #9147 broke it again. > Keeping a wineprefix between version is extremely common, but you miss the > point that it's not guaranteed to work. No, I get that it's not guaranteed to work. It's the "(lack of) what happens next" that I am having trouble with. In particular, your "sanitized" wineprefix approach that just looks like a back-handed way of telling your users to go away and reinstall all their applications. If you're going to create mandatory registry entries in Wine that will make Wine crash/explode if they're not present then you need to find a way to update the .reg files in users' .wine/ directories too. Or put all these critical entries into an unmodifiable wine.reg file that every wine installation loads at start up. Or SOMETHING. Because no-one who installs Wine as binary packages is *ever* going to be interested in recreating his/her .wine directory each time they update. E.g. do you have any idea how much work is involved to install World of Warcraft, with all of its patches and expansion packs? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 7579] graphics output of MaCom2.dll does not work
by wine-bugs＠winehq.org 06 Oct '07

06 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=7579 --- Comment #12 from Ulf Mehlig <ulf.mehlig(a)gmx.net> 2007-10-06 18:44:24 --- (In reply to comment #11) > Could you test this program again using a recent Wine version? Sorry for the delay -- already one of the previous wine versions released after your last comment did work, so I suppose this bug can be closed. There are some new problems apparently related to drawing of the window frame with 0.9.46 (contents is drawn but window frame does not appear initially, or it appears flickering and "disturbed" during updates of the window contents), but this is probably something for a different bug report ... I'll have a closer look later. Thanks alot! Ulf -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 8033] TOPO 4.2.7: Unhandled Page Fault Using
by wine-bugs＠winehq.org 06 Oct '07

06 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #37 from James Hawkins <truiken(a)gmail.com> 2007-10-06 18:32:18 --- (In reply to comment #36) > (In reply to comment #35) > > I don't think you understand how the development process works. > > I'm a *user* of Wine (via Fedora 7), not one of its developers. Wine is > included in many Linux distributions as RPM files, and these RPM files are > occasionally updated. From the sound of it, someone needs to have a nice > (polite) chat with the Fedora packagers (and probably the others too) because > you seem to be saying that the RPM update process is likely to be slowly > *trashing* everyone's Wine installations. Sweet. > As a user, you are a part of the development process by submitting bug reports. Please read [1] to get a better understanding of what alpha software means. [1] http://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha > > Wine is alpha and the developers make no guarantee of stability. > > I'm not expecting stability. However, I do expect considerably more interest in > bug reports. All of the reported crashes have happened with clean package > installations and so qualify as bona-fide bugs. > If we weren't interested in bug reports, no one would be responding to this bug at all. > Basically: Wine now has USERS - get used to it. > > > All you have to do to get them back is > > > > $ mv .wine-save .wine > > Then what's the point of wineprefix? I need to be able to update my *existing* > .wine installation, or the Wine developers must make it plain that anyone who > wants to update his/her Wine packages is expected to uninstall all their > Windows programs beforehand and then reinstall them afterwards. (And then see > how many people are left using Wine...) > You don't understand the idea of a wineprefix, and that's making this conversation difficult. You can have several wineprefixes along with several different versions of Wine installed. Honestly that's besides the point though. If you upgrade Wine and an app breaks, then that is a regression and we would ask you to run a regression test to see which commit broke the app. Keeping a wineprefix between version is extremely common, but you miss the point that it's not guaranteed to work. > > To sum it up, if you can't reproduce this bug with a clean .wine, then this > > bug will be closed as invalid. > > That is a very sad attitude - the bug exists and I have posted the traces to > prove it. This particular game doesn't even *start* with a "clean" .wine, > presumably because important registry keys are missing, so there's a nice > little "catch-22" for you! And if you're saying that Wine crashes simply > because it can't find a registry key then that sounds like very sloppy coding > to me. > Attitude? It's Wine policy. It sounds like you're adding registry entries from Windows to make the app work in the first place. Is that the case? If so, this bug is definitely invalid. To file a bug report, you have to be able to provide step-by-step instructions to reproduce the bug. That starts with a clean wineprefix: $ mv .wine .wine-save $ wineprefixcreate $ wine setup.exe $ cd [dir containing exe] $ wine app.exe [crashes, bad behavior, etc] -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 8033] TOPO 4.2.7: Unhandled Page Fault Using
by wine-bugs＠winehq.org 06 Oct '07

06 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #36 from rankincj(a)yahoo.com 2007-10-06 18:16:57 --- (In reply to comment #35) > I don't think you understand how the development process works. I'm a *user* of Wine (via Fedora 7), not one of its developers. Wine is included in many Linux distributions as RPM files, and these RPM files are occasionally updated. From the sound of it, someone needs to have a nice (polite) chat with the Fedora packagers (and probably the others too) because you seem to be saying that the RPM update process is likely to be slowly *trashing* everyone's Wine installations. Sweet. > Wine is alpha and the developers make no guarantee of stability. I'm not expecting stability. However, I do expect considerably more interest in bug reports. All of the reported crashes have happened with clean package installations and so qualify as bona-fide bugs. Basically: Wine now has USERS - get used to it. > All you have to do to get them back is > > $ mv .wine-save .wine Then what's the point of wineprefix? I need to be able to update my *existing* .wine installation, or the Wine developers must make it plain that anyone who wants to update his/her Wine packages is expected to uninstall all their Windows programs beforehand and then reinstall them afterwards. (And then see how many people are left using Wine...) > To sum it up, if you can't reproduce this bug with a clean .wine, then this > bug will be closed as invalid. That is a very sad attitude - the bug exists and I have posted the traces to prove it. This particular game doesn't even *start* with a "clean" .wine, presumably because important registry keys are missing, so there's a nice little "catch-22" for you! And if you're saying that Wine crashes simply because it can't find a registry key then that sounds like very sloppy coding to me. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 6971] Mouse "escapes" window or is confined to an area in the full screen program
by wine-bugs＠winehq.org 06 Oct '07

06 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=6971 Vitaliy Margolen <vitaliy(a)kievinfo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.0.0 --- Comment #29 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2007-10-06 17:55:25 --- Well I don't want to nominate my own bug, but this really should be fixed by 1.0.0 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 7510] Super Copyright (free software) fails to install and run
by wine-bugs＠winehq.org 06 Oct '07

06 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=7510 --- Comment #12 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> 2007-10-06 17:53:24 --- Created an attachment (id=8423) --> (http://bugs.winehq.org/attachment.cgi?id=8423) patch Could you try the attached patch? (Try it on a new ~/.wine, so move away your old one) The debug log showed it had problems opening a *.chm file. After this patch the installation claims it was successfull for me. Didn't try the app itsself yet, could you test the app itsself too? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 8033] TOPO 4.2.7: Unhandled Page Fault Using
by wine-bugs＠winehq.org 06 Oct '07

06 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #35 from James Hawkins <truiken(a)gmail.com> 2007-10-06 17:23:08 --- I don't think you understand how the development process works. Wine is alpha and the developers make no guarantee of stability. A part of helping with the development process is running apps in a clean .wine environment so that no external factors affect the bug. Of course your gecko and configuration settings didn't show up when you moved away .wine and called wineprefixcreate. All you have to do to get them back is $ mv .wine-save .wine It sounds like you need to read the Wine User Guide to get a better understanding of how Wine works, especially regarding wine prefixes. http://winehq.org/site/docs/wineusr-guide/index To sum it up, if you can't reproduce this bug with a clean .wine, then this bug will be closed as invalid. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 5321] msvc4.0 ide crashes with null pointer if you use "run to cursor"
by wine-bugs＠winehq.org 06 Oct '07

06 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=5321 --- Comment #1 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2007-10-06 17:16:33 --- Is this still an issue? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 8291] wwiionline: Mouse cursor sticks in the center
by wine-bugs＠winehq.org 06 Oct '07

06 Oct '07

http://bugs.winehq.org/show_bug.cgi?id=8291 --- Comment #5 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2007-10-06 17:14:22 --- Is this still a problem in current Wine version? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0