http://bugs.winehq.org/show_bug.cgi?id=17344
Summary: Lightwave Screamernet: v9.6 fails to start with
"gcore9.ll failed to initialize"
Product: Wine
Version: 1.1.14
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: philip(a)emcorp.force9.co.uk
Created an attachment (id=19379)
--> (http://bugs.winehq.org/attachment.cgi?id=19379)
Debug trace (+relay,+seh,+tid)
Overview:
Attempting to run Newtek Lightwave Screamernet (LWSN.EXE) version 9.6 results
in the following error message:
err:module:attach_process_dlls "gcore9.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for
L"C:\\lwsn96\\lwsn.exe" failed, status c000001d
Steps to reproduce:
Kick off LWSN from the command line in mode 3, eg:
wine C:/lwsn96/lwsn.exe -3 -cC:/lwsn96/Config -dC:/Content scenes/testscene.lws
1 1 1
Actual result:
LSWN.EXE fails to start (error message above)
Expected result:
LWSN.EXE should load the Lightwave scene data, render a 3D image and save it.
Build & Platform:
Wine 1.1.14 on openSUSE 11.1 & openSUSE 11.0
Additional Info:
Trial version of Lightwave 9.6 (which includes LWSN.EXE) available here:
http://www.newtek.com/lightwave/lwtrial.php
NOTE: All versions 9.x prior to 9.6 work fine with Wine 1.1.14 on openSUSE 11.0
& 11.1
--
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=18898
Summary: Steam: EULA window is blank and unresponsive
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shdocvw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: stonej4(a)mcmaster.ca
Created an attachment (id=21740)
--> (http://bugs.winehq.org/attachment.cgi?id=21740)
Debug output from running Steam then running Unreal to get EULA Window
The EULA window for Unreal and Unreal Tournament(possibly other apps) does not
fill and becomes unresponsive bringing steam down with it. Debug output
included.
--
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=13839
Summary: Steam hangs in SteamStartup() attempting to connect to
servers
Product: Wine
Version: 1.0-rc4
Platform: All
OS/Version: Solaris
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: trisk+winehq(a)acm.jhu.edu
Created an attachment (id=13899)
--> (http://bugs.winehq.org/attachment.cgi?id=13899)
Gzipped output of WINEDEBUG=trace+relay wine Steam.exe
Running Steam results in strange behaviour on Solaris and OpenSolaris.
When Steam is first installed (using either the current MSI installer or an
older standalone installer), it successfully updates itself and automatically
restarts.
,
On restart, it spews extensive messages to the console about connection
attempts to all 100+ CSDS servers with latency.
For example, the last couple of lines are:
CellID: Connecting to 87.248.209.212:27031. . .
CellID: Connect to 87.248.209.212:27031 took 110 MS
CellID: !! Got Cell ID 2 from server 69.28.153.90:27031
It then makes no further progress and appears to hang. If interrupted with
Ctrl-C, it displays a "SteamStartup() failed" messagebox before exiting.
When started again, Steam.exe prints set of "CellID:" messages showing that is
is connecting to a particular server, then blocks for at least a minute, then
connects to a different server. This goes on indefinitely.
I'm attaching a WINEDEBUG=trace+relay log (to reduce log size, this Steam
instance was interrupted after about 30 seconds). I can't do
WINEDEBUG=trace+all because it results in an error message from Steam about
being unable to load SteamUI.dll.
This seems to be a network related issue, but I'm not entirely certain.
--
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=15431
Summary: Problem with several Xservers
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lich(a)math.spbu.ru
Created an attachment (id=16294)
--> (http://bugs.winehq.org/attachment.cgi?id=16294)
screenshot
I have several Xservers with different geometry:
:0 - real Xorg server - 1280x1024
:1 - vnc server (or Xnest) - 1024x768
If I run any wine app first time in smaller X (:1) and then on bigger X (:0),
it gets corrupted outside 1024x768 region - exactly the size of smaller X.
If I use wine virtual desktop feature (X server does not matter), this bug
does not appear.
--
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=18909
Summary: Avid media composer doesn't work
Product: Wine
Version: 1.1.23
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P1
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wiccio84(a)yahoo.it
Created an attachment (id=21756)
--> (http://bugs.winehq.org/attachment.cgi?id=21756)
I tried to launch avid media composer 2.8
Wen i launch the application avid media composer wine show me the error report
in the attached file
--
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=15682
Summary: Naviter Seeyou ignores 'Register' button
Product: Wine
Version: 1.1.6
Platform: Other
URL: http://www.naviter.si/products/seeyou.php?Itemid=213
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
A user complained in the appdb that he could not register Naviter SeeYou,
so I gave it a try.
To register, you have to do Help / Register, type in your key, and click
the Register button.
Sure enough, clicking that button seems to do nothing.
Annoyingly, the app's main menu was detached when I ran it, and
the floating main menu was behind all the windows. So if you
can't find the Help menu, try closing the app's inner windows.
--
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=12045
Summary: foobar2000 0.9.4.4 - window close lag
Product: Wine
Version: 0.9.57.
Platform: PC
URL: http://www.foobar2000.org/
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquid.acid(a)gmx.net
I have some mysterious lag when working with foobar2000 version 0.9.4.4
When having windows (opened by foobar2k itself) open, like the file property
dialogue, or a file scan result window and I close this particular window
SOMETIMES (not always) I have some serious lag. Which means I click the
X-button, and at first nothing happens.
Now I can do different things:
1) Sometimes moving the mouse around triggers window closing
2) Sometimes dragging the still open window around triggers closing
3) Pushing the X a second time sometimes does the trick
I didn't notice this with wine-0.9.56, so it seems to be a regression. I'm
still trying to figure out some actions to always reproduce the problem, but
currently I'm not successful.
This problem is not bound to CPU usage. It also appears when the CPU is idling
at 99%.
Gonna try a bisect, but as I know no way to accurately reproduce it...
Someone with similar problems? Maybe not only fb2k?
Thanks,
Tobias
--
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=18627
Summary: Sudden Strike 2 crashes after first movie.
Product: Wine
Version: 1.1.21
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dik_again(a)yahoo.com
Created an attachment (id=21327)
--> (http://bugs.winehq.org/attachment.cgi?id=21327)
output to a console
A game crashes after it plays the intro movie. Or, when it find no movie, then
crashes immediatly with the same backtrace.
details in an attaachment
--
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=14848
Summary: PVPGN loader for Warcraft 3 v1.22
Product: WineHQ Apps Database
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: appdb-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: saidin54(a)gmail.com
Running w3l.exe produces a "Memory protection" error. The line of code which
fails has a call to VirtualProtectEx. A copy of the loader can be found at
http://war3.co.za/downloads/patches/w3l-1.22.rar. My Linux distribution is
Gentoo. I have this bug on all versions of Wine. I have tried updating to 1.1.2
off the wine-9999 ebuild for git - and it worked. But, as soon as I reset the
machine, the problem returned. Uninstalling and reinstalling 1.1.2 did not
(even temporarily) fix the problem.
--
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=19021
Summary: Settler 2 - The Next Generation needs
fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context
recreation support to SetDepthStencilSurface
Product: Wine
Version: 1.1.23
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nospam-abuse(a)bloodgate.com
Starting a German Settlers 2 - The next generation (Siedler 2 - die nächste
Generation) patched to 11757, I get the following error in a tiny message box:
Can't create device!
The console shows:
te@te-laptop:~/.wine/drive_c/Program Files/Ubisoft/Funatics/The Settlers II -
10th Anniversary$ wine bin/S2DNG
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x13c690,0x13c590): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x92f268,0x00000000), stub!
fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to
SetDepthStencilSurface
fixme:winmm:MMDRV_Exit Closing while ll-driver open
The result does not change wether I use a no-cd patch version, or not. Running
from inside the root dir or the bin/ subdir doesn't change it, either.
Adding a d3dx9_29.dll and/or d3dx9_36.dll to my wine/windows/system32 doesn't
help either.
Googling around leads me to believe my graphic card might be the culprit, but I
don't know for sure.
Specs:
* Dell Inspiron 6400
* 2Gb memory
* Linux version 2.6.24-24-generic (Ubuntu 8.04 Hardy 32bit)
* Genuine Intel(R) CPU T2080 @ 1.73GHz (dual-core)
* wine 1.1.23
* 1280x800 @ 24bit
* Intel integrated graphics 945GM/GMS/GME 943/940GML (Couldn't find out which
one exactly it is)
If there is anything more I can do, please ask.
--
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.