May 2010 - Wine-bugs - list.winehq.org

[Bug 6787] Execution of .exe file cause nothing in Servant Salamander
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=6787 --- Comment #18 from Petr Dlouhý <petr.dlouhy(a)email.cz> 2010-05-10 04:49:35 --- > According to the comments #10 and #11 this bug is fixed. Hm ... maybe it get broken before 1.1.30 release, or I am doing something differently. > Which notepad.exe is that, a built-in one? Yes, but I tried also other (non built-in) executables. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 6787] Execution of .exe file cause nothing in Servant Salamander
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=6787 --- Comment #17 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-05-10 04:45:03 --- (In reply to comment #16) > Maybe I am doing something wrong, but it seems, that this bug was never fixed. According to the comments #10 and #11 this bug is fixed. > I tried it with Wine 1.1.30 (from old .deb archives) with deleted ~/.wine , but > it doesn't work there - I was trying to execute notepad.exe. Which notepad.exe is that, a built-in one? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 6787] Execution of .exe file cause nothing in Servant Salamander
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=6787 --- Comment #16 from Petr Dlouhý <petr.dlouhy(a)email.cz> 2010-05-10 04:34:04 --- Maybe I am doing something wrong, but it seems, that this bug was never fixed. I tried it with Wine 1.1.30 (from old .deb archives) with deleted ~/.wine , but it doesn't work there - I was trying to execute notepad.exe. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 3037] LTspice: broken internal windows resizing
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=3037 Andrew Gaydenko <a(a)gaydenko.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|LTspice: UI glitches |LTspice: broken internal | |windows resizing -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 3037] LTspice: UI glitches
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=3037 --- Comment #52 from Andrew Gaydenko <a(a)gaydenko.com> 2010-05-10 04:16:47 --- Heh.. Ok, I'll try to describe the issue again :-) Say, we have internal window inside main window, and the first one doesn't touch any edge of the second. Now, let's try to resize intenal window this way: take with mouse, say, right bottom corner and drag it towards right bottom corner of the main window. At the moment when you drop "resize mouse pointer" - and last one touches any edge or right-bottom corner of main window, scroll bar(s) suddenly appears. Expected (and old, very old :-)) behavior: after dropping resize pointer, intenal window is resized to be *adjoining* internal window edges. *Without* any scrollbars. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 22642] New: [NOT A BUG] Wine doesn't need 1.2 release
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=22642 Summary: [NOT A BUG] Wine doesn't need 1.2 release Product: Wine Version: unspecified Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: t.artem(a)mailcity.com Hello, everyone! Recently Alexander Julliard announced plans concerning stable Wine 1.2 release. Let me voice my opinion here and some thoughts concerning Wine development and future. The whole point of releasing Wine 1.0 was to attract developers and say to the world, “We are stable” you can join us; you can even port Windows applications to Linux using Wine-lib. AFAIK, not too many developers joined afterwards, AFAIK few to zero Windows applications have been ported to Linux using Wine 1.0(.1) codebase. So, we shook the world by releasing the first stable open source Win32 API and it was good for Wine's publicity and popularity. However no such point exists at present, Wine is well known and there is no need to announce the next stable release. Another point of releasing Wine 1.0 was to *maintain* a stable Wine. Time has shown no one wants to maintain stable Wine releases (do not tell me the single update counts as an example of maintaining a project). So, it seems to me two most important reasons of releasing a "stable" version of Wine are completely irrelevant. The third reason of why doing this doesn't make too much sense is that any newer Wine release (like 1.1.44) can successfully run for more applications than semi-stable Wine 1.0. Forcing developers to resolve 1.2 nominee bugs also doesn't seem a good idea - some of those bugs simply need paid developers because bugs are so complicated they need developers' sweat and blood, so external contributors will not likely be interested and if they start fixing them, they can be distracted from working on other no less relevant problems. Wine's real problem is that it lacks profound regression testing. Generally, every new Wine release is better than a previous one, but since regressions are introduced regularly, people complain. The bottom line is that Wine does not need the next stable release (which will be a waste and strain of developers’ time and energy); Wine only needs a good regression testing. My only proposal is to change Wine releases naming scheme. Right now we have quite meaningless 1.1.XX releases, which is dull at best. I propose a scheme based on a year and a release number within this year. So, the first release of year 2010 will be 10.1, the second release 10.2 and so on and so forth. Releases' numbers are assigned on a day of release to avoid confusion. Since this scheme has not been used before, I propose instead of releasing Wine 1.2, start a new versioning scheme, where the next Wine release will be 10.1. That will be a bomb, and Wine we will be a super star once again. Thanks everyone for their hard work, Artem S. Tashkinov P.S. Please, repost this message to wine-devel if you find it deserving other developers' attention. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2

[Bug 3037] LTspice: UI glitches
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=3037 --- Comment #51 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-05-10 03:24:28 --- (In reply to comment #50) > I have not tested as far as I'm not aware about (and have not) Windows apps at > all, except for LTspice and another free app (last one has not MDI). Regarding your question, MDI applications work in Wine, it's not clear to me from the description what kind of a problem your app has. > BTW, current bug description is misleading, as far as initially the bug > included two parts in accordance with first message. Currently the second one > is remaining. Is it possible to rename the bug with more corresponding and > speaking to wine team manner? Sure, it's your bug. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 3037] LTspice: UI glitches
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=3037 --- Comment #50 from Andrew Gaydenko <a(a)gaydenko.com> 2010-05-10 02:21:45 --- I have not tested as far as I'm not aware about (and have not) Windows apps at all, except for LTspice and another free app (last one has not MDI). BTW, current bug description is misleading, as far as initially the bug included two parts in accordance with first message. Currently the second one is remaining. Is it possible to rename the bug with more corresponding and speaking to wine team manner? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 3037] LTspice: UI glitches
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=3037 --- Comment #49 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-05-10 02:13:33 --- (In reply to comment #48) > Dmitry, it seems I'm not experienced enough, especially taking in mind I have > the only (and new, and critical) environment in hands. A lot of users perform the regression testing, it's really not that hard. > Not having Windows distribution I, of course, have not Windows applications :-) > - LTspice is almost the only I use (and the second and last one is also free). > I wonder, is LTspice the only MDI app having the problem? Do other MDI apps > work fine? The case LTspice is unique seems to me too surprising. Have you tested other MDI applications? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 3037] LTspice: UI glitches
by wine-bugs＠winehq.org 10 May '10

10 May '10

http://bugs.winehq.org/show_bug.cgi?id=3037 --- Comment #48 from Andrew Gaydenko <a(a)gaydenko.com> 2010-05-10 01:33:04 --- Dmitry, it seems I'm not experienced enough, especially taking in mind I have the only (and new, and critical) environment in hands. Not having Windows distribution I, of course, have not Windows applications :-) - LTspice is almost the only I use (and the second and last one is also free). I wonder, is LTspice the only MDI app having the problem? Do other MDI apps work fine? The case LTspice is unique seems to me too surprising. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0