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

[Bug 8300] Title bar shown in window style that does not have one
by wine-bugs＠winehq.org Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8300 --- Comment #7 from Jaime Rave <jaimerave(a)gmail.com> 2007-10-07 19:49:30 --- Created an attachment (id=8456) --> (http://bugs.winehq.org/attachment.cgi?id=8456) Screenshot showing the problem -- 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 8300] Title bar shown in window style that does not have one
by wine-bugs＠winehq.org Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8300 Jaime Rave <jaimerave(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jaimerave(a)gmail.com --- Comment #6 from Jaime Rave <jaimerave(a)gmail.com> 2007-10-07 19:48:13 --- This problem is also affecting MSN Messenger, you can't hide the border, when you press the button to hide the border, only the menus disappear but the tittle stays there. -- 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 Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #56 from rankincj(a)yahoo.com 2007-10-07 19:44:34 --- (In reply to comment #52) > This has been turned into an issue of upgrading > between releases, when the original request to remove the wineprefix had > nothing to do with differences between releases or problems handling such an > upgrade. For the record, it looks as Wine is crashing for me because someone defined some new registry entries, and the code assumes that those entries are always going to be there. Given time, I can probably find the exact new keys in question. However, this now leaves me with a problem: how to update my registry while keeping all my settings and game state, because updating Wine by using "yum update" certainly doesn't touch the .reg files in the .wine directory. (It looks as if the app installed an entry in system.reg that told it where the CD was mounted, and then refused to run if this entry was not present. Adding this entry to a "fresh" wineprefix avoided the crash.) So when you say "The bug is fixed/closed", you *really* mean that it is closed only for that small percentage of users who will install the app from scratch, and that everyone else can go hang. -- 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 Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #55 from rankincj(a)yahoo.com 2007-10-07 19:27:31 --- (In reply to comment #50) > Anonymous coward with an e-mail rankincj(a)yahoo.com, If you had the slightest iota of initiative you could enter my email address into Google and find out my full name in mere seconds. (And then hopefully kick yourself for not guessing it from my email address in the first place!) But that would be "work", wouldn't it, and rudeness is *so* much easier... > you forgot what I told you: use separate WINEPREFIX. Oh, I remember all right. What you fail to appreciate is that it wouldn't help. My original app is already installed in one WINEPREFIX that contains all my game state and settings. To install the app into a second WINEPREFIX would create me a brand new and up-to-date registry, but would lose me those settings and game state. Hence installing into a new WINEPREFIX is not an option. And in the meantime, there is *still* a code-path in Wine 0.9.46 that dereferences a NULL pointer! -- 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 Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #54 from James Hawkins <truiken(a)gmail.com> 2007-10-07 17:24:15 --- (In reply to comment #53) > Actually I am the one who originally reported the bug with TOPO and I did > comment on the fact that the fix by Dan Kegel eliminated the problem. As a > matter of fact I have been using TOPO successfully since Dan introduced the > fix. Also with wine version 0.9.43 I did not need to make the changes Dan > explained. > And we appreciate your help Nick. This bug is fixed partly because of your help. My comments were for Whit and rankincj(a)yahoo.com. -- 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 Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #53 from Nick <goodfella005(a)gmail.com> 2007-10-07 17:19:28 --- Actually I am the one who originally reported the bug with TOPO and I did comment on the fact that the fix by Dan Kegel eliminated the problem. As a matter of fact I have been using TOPO successfully since Dan introduced the fix. Also with wine version 0.9.43 I did not need to make the changes Dan explained. -- 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 Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #52 from James Hawkins <truiken(a)gmail.com> 2007-10-07 17:09:12 --- (In reply to comment #51) > The point in getting to 1.0 is to put all the stuff that 1.0 needs to have in > place _before_ 1.0 is released. That includes: > > (1) Having staff (even volunteers) trained to respect the users. Users who take > the time and effort to submit meaningful bug reports are among your best > assets. Those who have shown up prior to 1.0, if you can build a good > relationship with them, especially so. > > (2) Having the mechanisms in place to allow smooth version upgrades. Taking the > stance that these will be the absolutely last thing added to move to 1.0 > assures that they most likely will not be of release quality precisely when you > move to 1.0. > I'm sorry I have to say it, but by definition, you and rankincj(a)yahoo.com are ignorant on this topic. This has been turned into an issue of upgrading between releases, when the original request to remove the wineprefix had nothing to do with differences between releases or problems handling such an upgrade. The real issue is that there are finitely many variables that affect a bug, and the more variables we can eliminate as a cause of the bug, the easier it is to find the actual bug. 95% of the time, a bug has nothing to do with having a dirty .wine, but there is that 5% where this is a problem, and we ask users to remove their wineprefix to remove this variable so the debugging process is easier. At this point in the development process, there are very few changes to the code base that require a new wine prefix. After 1.0, there should be next to none. > Maybe being in competition with Windows makes you feel you can skimp on user > relations and quality control, but exactly the opposite is true. An OS project > is exactly as valuable as the community it attracts. You're very ungrateful of all the time and energy we spend on managing our bugzilla and fixing bugs. We do the best that we can with the manpower we have. If you want professional support, buy a professional product. >Trusting someone like V. > to be gatekeeper here is costing you dearly. Actually, you might not like his manner, but Vitaliy does a lot for the project, and we'd be at a loss without him. >It's time to look at _why_ it's > taking you so long to get to 1.0. > It's taking so long because we don't have the manpower to work any faster. We've gotten a tremendous amount accomplished with the few developers we do have. Whatever bug there is with TOPO might actually have positive attention paid to it if the reporter actually did what the developers asked him/her to do instead of complaining. -- 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 2759] Cannot start WinMX 3.53
by wine-bugs＠winehq.org Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=2759 --- Comment #14 from Anastasius Focht <focht(a)gmx.net> 2007-10-07 16:53:06 --- Created an attachment (id=8454) --> (http://bugs.winehq.org/attachment.cgi?id=8454) Implements WebBrowser::TheaterMode to let WinMX successfully start Hello, you need WebBrowser::TheaterMode property too to get WinMX to work. Attached patch implements this. Tested with wine 0.9.46+ and WinMX 3.54 beta 4. Starts fine. Regards -- 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 Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #51 from Whit Blauvelt <wine(a)transpect.com> 2007-10-07 16:52:11 --- The point in getting to 1.0 is to put all the stuff that 1.0 needs to have in place _before_ 1.0 is released. That includes: (1) Having staff (even volunteers) trained to respect the users. Users who take the time and effort to submit meaningful bug reports are among your best assets. Those who have shown up prior to 1.0, if you can build a good relationship with them, especially so. (2) Having the mechanisms in place to allow smooth version upgrades. Taking the stance that these will be the absolutely last thing added to move to 1.0 assures that they most likely will not be of release quality precisely when you move to 1.0. Maybe being in competition with Windows makes you feel you can skimp on user relations and quality control, but exactly the opposite is true. An OS project is exactly as valuable as the community it attracts. Trusting someone like V. to be gatekeeper here is costing you dearly. It's time to look at _why_ it's taking you so long to get to 1.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 8033] TOPO 4.2.7: Unhandled Page Fault Using
by wine-bugs＠winehq.org Oct. 7, 2007

Oct. 7, 2007

http://bugs.winehq.org/show_bug.cgi?id=8033 --- Comment #50 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2007-10-07 16:46:56 --- Anonymous coward with an e-mail rankincj(a)yahoo.com, you forgot what I told you: use separate WINEPREFIX. If you need to get more information about that, I'm sure you know how to do 'man wine'. THIS BUG IS CLOSED. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0