http://bugs.winehq.org/show_bug.cgi?id=21633
Summary: Regression - Psychonauts
Product: Wine
Version: 1.1.38
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: webmobster(a)gmail.com
Between 1.1.27 and 1.1.28 Psychonauts regresses, to crash at certain areas in
the game when a new object possibly a texture appears, this has occurred twice
for me, once when killing the telekinetic bear and once in the first tank
battle when the tanks aiming arrow turns red.
The program crashes with "err:seh:raise_exception Exception frame is not in
stack limits => unable to dispatch exception." and creates a .dmp file
(attached)
--
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.
http://bugs.winehq.org/show_bug.cgi?id=6971
Vitaliy Margolen <vitaliy(a)kievinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|berillions(a)gmail.com, |
|linuxuser-sky(a)gmx.de |
--
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.
http://bugs.winehq.org/show_bug.cgi?id=6971
Jon Rosen <holy.smoking.floorboards.batman(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|holy.smoking.floorboards.ba |
|tman(a)gmail.com |
--
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.
http://bugs.winehq.org/show_bug.cgi?id=21583
Summary: Memeo autobackup launcher doesn't work
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: komaksab(a)fastmail.fm
MemeoLauncher2.exe gives a program error when trying to launch. Works fine
under Windows.
I'm running Wine on Ubuntu 9.10. I know there are native Linux backup progs
available, but none of them work with my Bufallo NAS, and the NAS ships with
Memeo autobackup so wanted to give that a try under Wine.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=9220
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Final Fantasy 7 hangs in |Final Fantasy 7 crashes
|winmm |
--
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.
http://bugs.winehq.org/show_bug.cgi?id=9220
--- Comment #20 from Jörg Höhle <hoehle(a)users.sourceforge.net> 2010-02-08 11:37:31 ---
Somebody with admin rights or Stefan, please either change the subject line --
ff7demo hangs no more, it crashes -- or perhaps close this issue.
I've done some more testing, on MacOS as well as on Linux. Timing seems
involved in the crash, perhaps dsound, and graphics as well. Alas I can't rule
out a winmm/MIDI issue.
There seem to be 3 crash points:
1. knight swings the sword
2. a little later in the intro, facing 3 monsters
3. unresponsive menus appear, zooming into one of the 3 monsters.
I never got past 1. on MacOS. On Linux, using "DirectDrawRenderer"="gdi" in
the registry seems to reliably get past point 1. and crash in 2. or 3.
Sometimes I reached point 3. with the default settings.
Using "gdi" works despite the message
err:d3d7:IDirect3DImpl_7_CreateDevice The application wants to create a
Direct3D device, but non-opengl surfaces are set in the registry. Please set
the surface implementation to opengl or autodetection to allow 3D rendering
Other issues:
On MacOS, unless using "gdi", the content of the configuration window is never
rendered until you move another window over it. That's a bug on its own. Even
after it's rendered, it's not refreshed e.g. when you click the second tab.
On both Linux and MacOS, sometimes a yellow icon is drawn in the top left of
the configuration window. It looks like the window should normally have a title
bar, and that would be the title bar icon; all window content should perhaps
appear 1cm lower (there's void space at the bottom).
Using Ubuntu Intrepid with Intel i915 graphics or MacOS 10.5.8 with nVidia
9400GM.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #321 from Sven <septim.dt(a)gmail.com> 2010-02-08 09:30:56 ---
(In reply to comment #320)
> My 2 cents to the hack vs fix flamewar.
>
> I know as a dev (I develop in python) it is important to have clean code
> without hacks and workarounds but this bug affects many applications and most
> of them are games.
>
> And gamers want to play their games.
>
> When this means to patch wine source so we can play our game than lets do it!
The problem is that it's a hack and that it also breaks things. People
reporting bugs with this thing switched on waste a lot of valuable time. Then
every week, or at the moment every day someone posting that the hack does, or
doesn't work doesn't help. This is just some additional useless information in
this bug and it's also useless for the devs entering their mailbox. About 90%
of the last part of this page is spam and this bug is really hard to read like
it is. This is bugzilla, not a forum.
> I would say:
>
> Lets patch us __our__ wine version with hacks/patches wahtever so we can play
> or FIX it in the svn and stop moaning.
This is not something you do in a few days. It requires a lot of work.
> This is actually the idea behind open source everyone can submit a patch to
> make the application work again for him.
It also BREAKS things, which means it doesn't belong here. Some people will
just apply the patch, see things are broken, and report bugs with their broken
wine versions. Or they'll just post information about the hacks, which isn't
what the bug report is about.
> I know that there was a discussion that this bug is fixed in a new Xorg release
> or something but till this is here and the Distros are using it we can patch
> our versions.
>
> I dont see the point as long as the patches are not pasted into svn there is no
> problem in the svn code with hacks and stuff and this is actually only a place
> where ppl submit their solution to a problem. If devs read this thread and
> think omg another hack they have 2 choices:
>
> 1. Get angry because of a patch that is not in svn and is not seen in the
> actual code
>
> 2. See that others try to help other people with a problem in __their__ wine
> version and be glad to see the open source spirit around. Then close this
> thread and continue to work on clean wine code
>
> just my thoughts
What someone SHOULD do is create a wiki page, post their hack there and write a
clear disclaimer at the top of the wiki page and everywhere near a download
link, because some people really do their best to miss every warning. Now if
the patch is broken for a certain version of wine, one could edit the wiki
page, and tell it's broken, so everyone who's interested knows it's broken.
Then they can wait for someone to fix the hack for the newer version.
This would mean no more spam here, no more useless hacks here, and a clear
disclaimer that this hack will break things. Then everyone who wants a hack can
get their hack, and everyone who only cares about the actual bug and about
REALLY fixing it can come here.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #320 from Manuel Soukup <linuxuser-sky(a)gmx.de> 2010-02-08 08:46:34 ---
My 2 cents to the hack vs fix flamewar.
I know as a dev (I develop in python) it is important to have clean code
without hacks and workarounds but this bug affects many applications and most
of them are games.
And gamers want to play their games.
When this means to patch wine source so we can play our game than lets do it!
I would say:
Lets patch us __our__ wine version with hacks/patches wahtever so we can play
or FIX it in the svn and stop moaning.
This is actually the idea behind open source everyone can submit a patch to
make the application work again for him.
I know that there was a discussion that this bug is fixed in a new Xorg release
or something but till this is here and the Distros are using it we can patch
our versions.
I dont see the point as long as the patches are not pasted into svn there is no
problem in the svn code with hacks and stuff and this is actually only a place
where ppl submit their solution to a problem. If devs read this thread and
think omg another hack they have 2 choices:
1. Get angry because of a patch that is not in svn and is not seen in the
actual code
2. See that others try to help other people with a problem in __their__ wine
version and be glad to see the open source spirit around. Then close this
thread and continue to work on clean wine code
just my thoughts
--
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.
http://bugs.winehq.org/show_bug.cgi?id=201
Carsten Clasohm <info(a)clasohm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |info(a)clasohm.com
--
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.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #319 from Gilboa Davara <gilboad(a)gmail.com> 2010-02-07 23:25:11 ---
(In reply to comment #318)
> (From update of attachment 26091 [details])
> What part of NO HACKS don't you Bontas Marcel understand?
Vitally,
Not trying to get into the hack vs. patch solution - but you do understand that
as long as there is not official solution and/or officially sanctioned hack to
solve this issue this bugzilla entry (or anyone that follows it) will continue
to get flooded by hacks and semi-working patches, right?
Trying to fight it will not help, it'll simply increase the noise to signal
ratio...
- Gilboa
--
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.