http://bugs.winehq.org/show_bug.cgi?id=8607
------- Additional Comments From wine(a)eternaldusk.com 2007-05-06 22:39 -------
>> What distro?
As stated in my original bug report, this is what is seen when running on
Kubuntu 7.10 (Gutsy Gibbon - 2.6.22), which goes tribe 1 in two days.
>> Why are you compiling Wine from GIT and not using binary package?
Because that's what I've done for the last couple of years on various distros.
Well.. I was compiling from CVS back then, but "same difference" as they say.
Also, there are no wine packages available for Gutsy yet.
>> This is not place to ask how to use GIT. _Only_ to discuss Wine bugs _only_.
I was only asking for a friendly piece of advice from the more experienced (you)
so that I could help track down the bug. Without your assistance, the best
thing I could come up with was "git reset --hard HEAD~100" to keep backleveling
a chunk at a time.
>> No one had this problem so far.
That you are aware of, yes? No one ever reports a problem until the first
person does, and not everyone always experiences every problem, right? I'm
running a 64-bit bleeding edge distro on a dual-core system; I somehow always
tend to be one of the first to encounter a new bug - hehe.
>> I will keep this bug open, but you will have to find what's broken in your
setup/configuration/etc.
This is not a bug that affects my ability to use Wine at all... I'm only trying
to assist you guys. If you are sure no one else will encounter this and insist
on closing it, that's your prerogative.
As for searching for what's broken, I've completely deleted my .wine, removed my
Steam directory, made clean and installed from scratch. Either this is a bug in
wine, a bug in the newer GCC (which I pretty much ruled out by jumping back to
3.4 in my testing), or a bug in some supporting library that will likely affect
a lot of people eventually if we don't identify it now and alert the responsible
project (if it's actually a bug in a supporting library).
I backleveled all the way back to April so far, and still see the problem. If
no one else in no other 64-bit distro sees the problem (though we've only had a
day to have them stumble across this and chime in), I'm inclined to believe it's
a problem introduced by something new in Gutsy. I was using Feisty betas in
April, and believe I would have noticed this bug before - but can't be certain
since all I usually do is test to see what the DirectX patches do to/for the
actual games.
If it's a problem with a supporting library, do you have an idea as to which one
could have this sort of affect on the GUI? I'm willing to download the source
of likely candidates and install older versions to root out the culprit.
The Steam games themselves, like CS:S still run fine (kudos to all devs)... only
the steam GUI is showing this minor bug. I even turned off Beryl and tried KWin
as a window manager, to see if it had any effect -but it did not.
--
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=8617
Summary: Time of Defiance SetupDiGetClassDevsW
SetupDiEnumDeviceInterfaces infinite loop
Product: Wine
Version: 0.9.37.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sparr0(a)gmail.com
When trying to log into the MMORTS Time of Defiance, I end up with an infinite
loop of these two lines (a few dozen times per second) while the game client is
trying to initiate the connection to the server:
fixme:setupapi:SetupDiGetClassDevsW returning empty list
fixme:setupapi:SetupDiEnumDeviceInterfaces 0x90868d8, (nil),
{ec87f1e3-c13b-4100-b5f7-8b84d54260cb}, 0x00000000, 0x34f4bc
The first fixme is probably the real problem, as it is expected to produce a
non-empty list of interfaces/devices.
I don't know what Component this bug belongs in.
--
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=8615
vitaliy(a)kievinfo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #6631|application/octet-stream |text/plain
mime type| |
--
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=8577
vitaliy(a)kievinfo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From vitaliy(a)kievinfo.com 2007-05-06 21:31 -------
Confirming. Have this problem with TRL demo and virtual-desktop.
--
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=8608
------- Additional Comments From shacklein(a)gmail.com 2007-05-06 21:17 -------
I have been trying to find out more about this problem and it is not easy. What
would be useful is some way to show what sequencer client/port Wine is connected to.
The application I am running seems to detect SOME midi support, but I have not
been able to discover what it is connecting to. I'm guessing that it's
connecting to the first one it finds (ALSA 16:0) which as far as I can tell is
my soundcard's Gameport connector. I want it to be connected to 17:0, which is
the hardware Wavetable synthesiser.
Here is clarification of what I want to do: Windows provides a built-in software
midi synthesiser. Obviously this is not something that Wine should implement,
but what would be nice is a way to tell Wine which clients/ports are available
for internel synthesising (that would be played through the sound card), and
which are available for connecting external synthesisers (e.g., an external MIDI
keyboard).
--
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=8607
------- Additional Comments From vitaliy(a)kievinfo.com 2007-05-06 21:17 -------
What distro? Why are you compiling Wine from GIT and not using binary package?
This is not place to ask how to use GIT. _Only_ to discuss Wine bugs _only_.
No one had this problem so far. I will keep this bug open, but you will have to
find what's broken in your setup/configuration/etc.
--
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=8616
Summary: PCSpim doesn't install
Product: Wine
Version: CVS
Platform: PC
URL: http://www.ece.arizona.edu/~ece369/spim/spim.zip
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: juan_lang(a)yahoo.com
Download and unzip spim.zip. Run spimwin.exe, which is the setup program.
Accept the defaults (install to C:\Program Files\PCSpim), click Yes to create
the directory.
The install appears to complete (with an error dialog about not being able to
connect to Program Manager via DDE), but no files are copied.
The relevant part of a relay log is:
0012:Call KERNEL32.CopyFileA(0034f0a0 "Z:\\home\\juan\\spim\\mfc40.dll",0034ef98
"C:\\PROG~FBU\\PCSpim\\mfc40.dll",00000001) ret=00402a63
0012:Ret KERNEL32.CopyFileA() retval=00000000 ret=00402a63
CopyFileA is failing because the source file doesn't exist. Instead, it's been
unzipped to c:\windows\temp\<temporary directory>
--
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=8607
------- Additional Comments From wine(a)eternaldusk.com 2007-05-06 18:05 -------
Additional test, compiled with gcc 3.4 (instead of 4.1.3) and used -m32. Same
(broken) results.
Now doing bisect to see if it the skin looks right with older versions. I'm
just taking stabs with the "start" though. I'm reading through some Git
tutorials, but haven't found the command to just keep going backward, when
you're searching for a "good" version.
--
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.