http://bugs.winehq.org/show_bug.cgi?id=3077
rmay(a)ou.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|20050524 |0.9.28.
------- Additional Comments From rmay(a)ou.edu 2007-05-01 10:06 -------
Any more, no tricks whatsoever should be needed to run this with a clean wine
install. Only using the full path to run the program is required (which happens
to be required on windows as well). I still get this problem in Weatherscope
1.4.1 on Wine 0.9.28, running under Gnome 2.16 on Gentoo AMD64.
--
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=7084
Summary: Weatherscope fails to correctly generate menu link for
running program
Product: Wine
Version: 0.9.28.
Platform: PC-x86-64
URL: http://sdg.ocs.ou.edu/builds/final/win/WeatherScope/Weat
herScope-1.4.1.exe
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-user
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rmay(a)ou.edu
When installing Weatherscope (any version), the installer fails to create a link
for executing the program. A link _is_ created for the uninstaller (which does
not work), but nothing is created for running the program. On the command line,
I only get the following error message:
err:menubuilder:InvokeShellLinker failed to fork and exec wineshelllink
Weatherscope is freely available and can be downloaded at the given URL.
--
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=2096
------- Additional Comments From carl.sopchak(a)cegis123.com 2007-05-01 09:51 -------
The application still crashes, using wine 0.9.27 (as distributed by the Fedora
Project as wine-core-0.9.27-1.fc6), as this trace shows:
trace:bitmap:CreateBitmapIndirect 20x16, 65536 colors returning 0x4358
trace:bitmap:CreateCompatibleBitmap 0x4358
trace:bitmap:CreateCompatibleBitmap (0x31c,20,16) =
trace:bitmap:CreateBitmapIndirect 20x16, 65536 colors returning 0x435c
trace:bitmap:CreateCompatibleBitmap 0x435c
trace:bitmap:CreateBitmapIndirect 1614982020x1615206720, 2 colors returning 0x4484
trace:bitmap:CreateBitmapIndirect 1614982020x1615206720, 2 colors returning 0x4488
trace:bitmap:CreateCompatibleBitmap (0x31c,1614982020,1615206720) =
fixme:bitmap:CreateCompatibleBitmap got bad width 1614982020 or height
1615206720, please look for reason
trace:bitmap:CreateCompatibleBitmap (nil)
trace:bitmap:CreateCompatibleBitmap (0x31c,1614982020,1615206720) =
fixme:bitmap:CreateCompatibleBitmap got bad width 1614982020 or height
1615206720, please look for reason
trace:bitmap:CreateCompatibleBitmap (nil)
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 53 (X_CreatePixmap)
Serial number of failed request: 9234
Current serial number in output stream: 9261
Unfortunately, this is the most recent version of wine that I have readily
available. More unfortunate is the fact that I don't have enough time to spend
on getting to the root cause, although I've spent considerable time on this in
the past. If someone is willing to spend some time with me on this, I can be
persuaded to dive back in (although it might be time consuming just to get to a
point where I'm able to do any real debugging work - i.e., set up a working cvs
version).
I can't verify this, but after looking at the patch, it seems to me that I tried
it to no avail. If this bug becomes active again, I could give it another shot.
However, after refreshing my memory on C syntax, it doesn't look like it will
work in the case provided above (both height and width are huge). (It looks like
it just prevents the message if one of the height or width is zero. Am I
reading this right? It's been a while since I've used C...)
This is a real pain when printing checks, but the checks do print (the crash is
after sending the spool file). I just have to manually enter the check numbers
- after re-launching Quicken, of course...
HTH,
Carl
--
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=7083
Summary: low fps, delays in glsl_shader.c Vanguard Beta crashes
after 5 min. play
Product: Wine
Version: CVS
Platform: PC-x86-64
URL: http://appdb.winehq.org/appview.php?iVersionId=6422
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nospam(a)thenerdshow.com
Follow instructions in the appdb. You can create a character and enter the world!
FPS is really low (1-2FPS) and the game crashes after a minute of play because
of what appears to be 1-2 sec. delays in glsl_shader.c although that might not
be the real problem... I'm in the process of generating an error log. More
clues about the delays may be revealed with sysprof utility.
--
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=6171
ead1234(a)hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From ead1234(a)hotmail.com 2007-04-01 21:13 -------
works with current git
--
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=6972
ead1234(a)hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From ead1234(a)hotmail.com 2007-04-01 21:12 -------
works with current git
--
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=5819
------- Additional Comments From ead1234(a)hotmail.com 2007-04-01 20:39 -------
This works for me under wine on 3 distros( Ubuntu, Sabayon Linux, and Gentoo)
--
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=6978
------- Additional Comments From linux(a)ikiru.ch 2007-04-01 20:14 -------
No. When I launch another kind of software, which open a file from their very
own directory, I do not observe the same behaviour.
For instance, using a software like Whereisit, works perfectly with the command
line
wine "c:\Program Files\Whereisit\whereisit.exe"
but
wine "c:\Program Files\UBS e-banking\UBSPay\UBSPay.exe"
It could be related to the software itself, I don't know.
--
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=5141
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From tony.lambregts(a)gmail.com 2007-04-01 19:47 -------
Resolving Fixed then.
--
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.