http://bugs.winehq.org/show_bug.cgi?id=1486
tony_lambregts(a)telusplanet.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mike(a)globalgroup.co.za
------- Additional Comments From tony_lambregts(a)telusplanet.net 2004-09-09 20:41 -------
*** Bug 2470 has been marked as a duplicate of this bug. ***
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2470
tony_lambregts(a)telusplanet.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From tony_lambregts(a)telusplanet.net 2004-09-09 20:40 -------
*** This bug has been marked as a duplicate of 1486 ***
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2473
Summary: Can't start wine
Product: Wine
Version: 20040813
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: peter.talken(a)telia.com
This happens
[peter@etab peter]$ wine
Wine called with no arguments. Wine requires at least one argument - the name
of the Windows application you would like to run.
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
wine --help Display this help and exit
wine --version Output version information and exit
wine --native Use DLLs from a native MS-Windows (TM)
installation
Which is OK, but:
[peter@etab peter]$ wine --help
wine: could not exec /usr/local/kde/bin//usr/bin/wine-pthread
[peter@etab peter]$ wine --version
wine: could not exec /usr/local/kde/bin//usr/bin/wine-pthread
[peter@etab peter]$ notepad
wine: could not exec /usr/local/kde/bin//usr/bin/wine-pthread
[peter@etab peter]$
PATH looks like:
[peter@etab peter]$ echo $PATH
/usr/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin/:/usr/lib/jre-1.4.2_04/bin:/usr/lib/qt3/bin:/home/peter/bin:/usr/local/kde/bin
[peter@etab peter]$
If I start wine-pthread:(just to test)
[peter@etab peter]$ wine-pthread
wine client error:9: version mismatch 147/131.
Your wine binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?
[peter@etab peter]$
[peter@etab peter]$ whereis wine-pthread
wine-pthread: /usr/bin/wine-pthread
[peter@etab peter]$
[peter@etab peter]$ whereis wine
wine: /usr/bin/wine /usr/bin/wine.bin-kthread /usr/bin/wine.bin /usr/bin/wine.bin-pthread /etc/wine /usr/lib /usr/share/wine /usr/share/man/man1/wine.1.bz2
[peter@etab peter]$
wineserver is started.
wine version:
wine-20040813-2mdk.i586.rpm
from Mandrake cooker
Using Mandrake Linux 10.0
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1486
------- Additional Comments From jarto(a)starsoft.fi 2004-09-09 06:04 -------
I just tested the latest patch with some of my Delphi apps. It does solve the
problem. Thank you Michael :)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1486
------- Additional Comments From hallo(a)michael-kaufmann.ch 2004-09-09 04:54 -------
I've found another way to fix this bug without breaking a test case. There's no
need to keep disputing ;-)
Although no other WINE developer has responded to my proposed patch yet, I think
it has good chances to be included in WINE.
http://www.winehq.org/hypermail/wine-devel/2004/09/0279.html
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1486
------- Additional Comments From saulius.krasuckas(a)elst.vtu.lt 2004-09-09 03:14 -------
Some offtopic (excuse me):
Jarto, a new patches arrives every day and amount of people interested in
*fixing the root* of the bug would decrease, thus making bug getting buried
deeper and deeper.
IMHO many people consider this as a harm to future life of Wine. There is even
joke story about it:
* The greatest programming project of all took six days; on the seventh day
* the programmer rested. We've been trying to debug the *&^%$#@ thing ever
* since.
*
* Moral: design before you implement.
You wrote:
> 1. Accept Michael's patch
> 2. Let's find out what the patch breaks
The suggestion about some investigation of what gets broken is quite
interesting. It would shed some light on the amount of stuff got broken. Only
this the area of action should not belong to official Wine.
Its unclear for me: why do you need the patch to be in official Wine tree? Does
something restrict you from applying it by your hand and making your own Wine
package for your favourite distro?
Can you make this to be a separate project, call it Wine-smoof, for example?
IMHO this is the route by which both the CrossOver and Transgaming went. And it
would attract lots of advanced users which are too hot to stay on wait for one
year more. I would join it if it stays uncommercial.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1486
------- Additional Comments From jarto(a)starsoft.fi 2004-09-09 02:17 -------
I've read all the discussions about Michael's patch. It's unfortunate that the
patch was dropped. However, it's good that we know the root cause and it's
documented here in Bugzilla.
It's now about two years since I first noticed that menus don't work in the
Delphi apps I've created. It took another year before I was able to make a
simple test case. At this point I tried to solve the bug myself. When I
couldn't, I submitted this bug.
If I understand right, the patch won't be accepted because:
1. Somebody will reimplement the menu code properly at some point
2. The fix may break some other apps
IMHO the first reason is a bad one. Nobody can say for sure when the menu code
will be rewritten. There will always be areas to improve in Wine and lots of
other bugs and features will end up getting a higher priority in the future. We
might still be using the same menu code two more years from now.
What we know is that lots of Delphi apps don't work. But we don't know what the
patch may break.
I'd like to suggest:
1. Accept Michael's patch
2. Let's find out what the patch breaks
3. Revert back to the old code if it broke some important application
After that we'd at least know more which is better than guessing.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1486
------- Additional Comments From saulius.krasuckas(a)elst.vtu.lt 2004-09-09 00:56 -------
Samuel Herzog writes:
> -The user wants a working application.
> -The user wants to have the functions in the mainmenu.
> -The user does not know what a TestCases is.
> -The user is not interested in TestCases.
So you urge to sacrifice Wine architecture fineness, scalability, perspective of
future growth just for the few users to be able to run few applications?
So, you mean Wine should be designed for minority of the world? You mean all
the world should work just for few people? You are despotic person then. :-)
Wine should not, IMHO. Wines license doesn't restrict you from applying any
patch in your box/at your home. So, if you are using CVS to compile wine, you
can do this even automatically (by adding some lines to cvs-update script once).
I have just did this:
--- ../cvs_update 2004-09-09 08:51:58.000000000 +0200
+++ ../cvs_update_w_patch 2004-09-09 08:50:25.000000000 +0200
@@ -55,10 +55,18 @@
export CVSROOT=:pserver:cvs@cvs.winehq.com:/home/wine
#export CVSROOT=:pserver:cvs@rhlx01.fht-esslingen.de:/home/wine
push_to_CVS_dir
+ # unapplying the patch:
+ cd wine
+ w3m -dump "http://www.winehq.com/hypermail/wine-patches/2004/09/0074.html" |
patch -Rp0 --forward
+ cd ..
+ # updating:
if [[ $1 == "" ]];
then cvs update -PAd;
else cvs update -PdD "$1";
fi
+ # applying the patch:
+ cd wine
+ w3m -dump "http://www.winehq.com/hypermail/wine-patches/2004/09/0074.html" |
patch -p0
pop_dir
}
and it works. It may be better idea to move the reversing/forwarind patch game
to simple separate script. This would let you control several patches at once
and you will be easily able to do it by hand also.
Wine is supposed not to restrict you from being free, and you vote for
restricting Wine. Boo! ;-)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2394
------- Additional Comments From saulius.krasuckas(a)elst.vtu.lt 2004-09-09 00:03 -------
IMHO this has a lot to do with a bug (or even meta-bug) number 709.
I suppose you can always try using one more native dll and succeed:
WINEDLLOVERRIDES=riched32=n wine ...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.