http://bugs.winehq.org/show_bug.cgi?id=2082
Claudio <sick_soul(a)yahoo.it> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sick_soul(a)yahoo.it
--- Comment #37 from Claudio <sick_soul(a)yahoo.it> 2007-12-15 16:55:05 ---
(In reply to comment #35)
> Regarding the status, that is just a bugzilla category. A new bug is
> "UNCONFIRMED", when people confirm it it becomes "NEW". The next step is
> "RESOLVED" - with various reasons, e.g. FIXED, WONTFIX, ABANDONED, ..., after
> that CLOSED. So "NEW" doesn't mean that the bug isn't older than $DAYS. The
> "NEW" is what you mean with confirmed propably.
Ok. The category names confused me.
Thanks for your explanation.
> As far as fixing this bug is concerned, an open source project isn't
> something where you can drop in and order something to be done.
I know. I work on free software projects of my own.
I did not mean to order anyone to do anything.
Through my vote and comment I meant to suggest to change the status
(based on a wrong understanding of the categories),
and morph the current workarounds in a fix available for default wine.
> Possible reasons why this
> bug isn't fixed could be
>
> a) None of the developer has personal or commercial interest in the specific
> games
> b) None of the developers has time to fix it. Remember, many are working on
> Wine in their free time.
> c) No volunteer got around to fix it yet(as everyone only demands that it gets
> fixed)
> d) The bug is harder to fix than the simple workaround suggests. There might
> even be architectural differences between Windows and X11 which make it
> impossible to fix correctly.
This is one of the main problems with wine for me.
I do not have the time to try to fix wine bugs myself.
More so since I tried to invest time once to do that,
but my patches remained out of tree (which is fine by itself),
but I did not reach an open, satisfying discussions about the
issues underlying them.
So say I want some bugs fixed (not workarounds, but
fixes in order to make the api behave as the MS implementation),
by paying wine developers to do that.
I think there _is_ a company behind wine. So do you have
anything in place? Is paying for each bug enough to
generate the commercial interest in fixing them?
> In case of this bug, it's a combination of all 3 issues.
My main interest is for vanilla wine to be better, as I see Wine
as a powerful tool to facilitate the move towards free software.
But it has a long way to go to reach the level of compatibility
with the win32 API I (and I guess many others) would like to see.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8498
Jaime Rave <jaimerave(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jaimerave(a)gmail.com
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7285
--- Comment #17 from Giel van Schijndel <me(a)mortis.eu> 2007-12-15 11:47:23 ---
(In reply to comment #16)
> This indicates serious problem in your kernel. Please open bug with your
> distro, not Wine.
Would you happen to know what about the kernel could cause this (e.g. some
specific module or range of modules?). Since all non-stock modules (for a
default Debian kernel) that I've got loaded is an nVidia GFX driver. And I'm
using the same driver @ my laptop where WINE doesn't exhibit this issue.
> The only possible cause of that on Wine side would be hung I/O with some
> storage device. Are all your HDDs, CD-ROMs functioning properly?
Yes, all of them are functioning properly.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=1880
--- Comment #5 from Raul Sanchez <falotron(a)gmail.com> 2007-12-15 11:32:52 ---
(In reply to comment #3)
> Not sure why this bug was marked invalid.
>
> FWIW, it looks like you have to use IE to
> even download their client now.
>
Right!
Solved
Downloading & installing the GS Arcade through IE makes program run perfectly
Note:
I have installed IE this way
http://www.tatanka.com.br/ies4linux/page/Es/Instalaci%C3%B3n
If you do the same you must take on care that IE creates its own wine drive
folders, so you must put your folder games on it
For example...
I had some game on
/home/USER/.wine/drive_c/Archivos de programa
Then you must copy it on
/home/USER/.ies4linux/ie*/drive_c/Archivos de programa
ie* where * is the number of Internet Explorer version you want to use (I only
could run GS at 100% with Internet Explorer 6)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #22 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2007-12-15 11:05:42 ---
And make sure you do have at least read access to the device itself (not just
the mount point).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #21 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2007-12-15 11:05:10 ---
You have to map that device to a drive in winecfg. Since your HAL either broken
or not available for Wine.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7285
--- Comment #16 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2007-12-15 11:02:39 ---
(In reply to comment #15)
> I tried all of wine 0.9.44, 0.9.47 and 0.9.51 today. Every single one of them
> hung when attempting to create config files. And in all cases the respective
> wineserver wouldn't die when sending SIGKILL signals.
>
This indicates serious problem in your kernel. Please open bug with your
distro, not Wine.
The only possible cause of that on Wine side would be hung I/O with some
storage device. Are all your HDDs, CD-ROMs functioning properly?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #20 from Alexander K. Seewald <alex(a)seewald.at> 2007-12-15 11:00:31 ---
Have switched on automount. Plugging in the device as described mounts it
automatically. Still no new drive letter in winefile, though; and the
connection with TomTom HOME still does not work.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8979
Vitaliy Margolen <vitaliy(a)kievinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hein(a)kde.org
--- Comment #8 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2007-12-15 10:53:25 ---
*** Bug 10776 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 watching all bug changes.