http://bugs.winehq.org/show_bug.cgi?id=30763
Bug #: 30763
Summary: Please turn autoclose on in bugzilla
Product: Wine
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: butraxz(a)gmail.com
Classification: Unclassified
I propose turning autoclose on in bugzilla.
The reason is, that I have now gone experimentally thru about 300 old bugs, not
touched for 600-900 days. I have got around 15 saying yes, the bug is still
relevant to them, around 15 saying theirs can be abandoned, a few that have
been reported as fixed but not closed in time and the rest, around 260 bugs got
no answer. Which means propably that those are abandoned too.
Wine Bugzilla now has over 7000 open bugs from which over 4000 of which have
not been touched for a year and about 700 for two or more years. Based on the
findings above, I believe there would only be 10-15% bugs relevant today and
all others are abandoned. The work of manually closing bugs imho no longer
works in practice and I will stop it now as I believe I am able to draw the
conclusions.
Every day 2-5 new bugs are logged, 0-4 closed and about 10 new gets more than
600 days old. This means that in practice Bugzilla grows larger and larger and
searching what is relevant becomes harder and harder. I believe that the
current manual bugzilla closing practice can no longer bring relevant state of
wine to contributors.
In 2-3 years technology advances with great pace and interest in what wine can
do changes too. Programs get born and die. Programs famous six months ago may
no longer be famous today, for example most games are short to play and
short-lived in these days. HW is updated and interests change. In 6 months wine
gets 12 new releases and if I log a bug and no-one wants to touch it for six
months, it is most likely a zombie.
I have found in practice, that when I ask whether a person could update the
status of a zombie bug that they have created, some people just neglet it and
some get hostile of it being touched without me first testing whether it is
still relevant, althought I they themselves have not bothered to update their
own bugs for 2-3 years.
I feel that the open bug situation in bugzilla has got out of hands.
Therefore I propose turning autoclose on in bugzilla for bugs with no activity
for 6 monts. There are multiple of implementations of autoclose in
bugzilla.org, so this is not a technical issue.
The text could be on the lines :
'This bug has been automatically closed by bugzilla as abandoned because it has
had no activity for 6 months. OP or Administrator can reopen this bug after
retesting with latest version of wine and supplying up to date information
about the status of this bug'.
Nothing would be lost, bugs would only get closed and could be manually
reopened as often as OP or admin feels like it. Wine project itself says that
it provides only the APIs that are relevant to running the currently popular
set of programs.
It does not support old programs forever, dos is being phased out, windows 9x
is given minimal effort, win8 with winRT is coming etc. If all zombies would be
closed, could the relevant ones be immediately seen. Autoclose is also neutral
job unlike a person closing it. I feel that up to date bugs are much more
relevant to wine than faster and faster cumulating number of thousands upon
thousands bugs in unknown state.
Sorry that I am not able to do more, just giving this as my five cents worth…
--
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=30679
Bug #: 30679
Summary: Error running Rosetta Stone 3.4.7
Product: Wine
Version: 1.5.3
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alen.siljak(a)gmail.com
Classification: Unclassified
Created attachment 40170
--> http://bugs.winehq.org/attachment.cgi?id=40170
Backtrace
Fedora 17, x86_64.
After installation of Rosetta Stone this error pops up on start.
Seems related to video/d3d/fonts but can't figure out where exactly to submit.
--
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=22817
Summary: Perfect World International: rendering issues with
some models
Product: Wine
Version: 1.2-rc1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: itiliehl(a)yandex.ru
Some models (mostly those added in 'Rising Tide' update) are rendered
incorrectly. One triangle of model get displaced and leaves a hole in a mesh
and sticks out.
--
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=30698
Bug #: 30698
Summary: Mouse won't be able to "go thru the borders" while
playing ANY game. (You can't move the camera
infinitely thru the x-axis, only like 180°)
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alex-gustafsson(a)live.se
Classification: Unclassified
EVERY game I've tried (quite a few...) have come to this problem. When I try to
turn around or something like that, the mouse gets stuck at the border of the
window, while on PC I would be able to turn infinitely.
This is a quite severe bug making most games unplayable.
Using Engine WS9Wine 1.5.4 & Wrapper version 2.5.5
--
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=30624
Bug #: 30624
Summary: "d3d: wined3d_occlusion_query_ops_get_data" delays
gameplay in Fear 3
Product: Wine
Version: 1.5.3
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: elcuriosoaqui(a)hotmail.com
Classification: Unclassified
-I installed d3dx9, d3dx10, d3dx11, msvcr90, quartz, winhttp, wininet, dplayx,
dlls required for this game. Libs 32bits, winbind, all.
-Some distributions linux, you need execute "echo 0|sudo tee
/proc/sys/kernel/yama/ptrace_scope", same error with "StarCraft 2"
-"OffscreenRenderingMode"="fbo" This is correct. Reinstall Video drivers
(Nvidia for me, Video Card GTS250).
When I change the videosettings in game, black screen appears. With the mouse I
leave the game basing on the sound and position of the options(click on Quit
with blackscreen "blind mode").
-Problems (same problems with wine 1.4 and 1.3.28):
err:wgl:is_extension_supported No OpenGL extensions found, check if your OpenGL
setup is correct! (I installed Nvidia drivers (privative) 295.49 Linux-x86_64)
fixme:d3d:wined3d_occlusion_query_ops_get_data 0x18a02c68 Wrong thread,
returning 1. (this error appears in the game, this is caused by the lights of
the lamps on the stage (multiplayer and campaign). These lights can pass
through walls in the game and I can see supplies, soldiers, Alma Wade (girl)
and lamps. "0x18a02c68" changes many times and it delays the gameplay).
May be, these problems must be repaired for this game becomes Platinum
"AlwaysOffScreen"="enabled"
"DirectDrawRenderer"="opengl"
"Multisampling"="enabled"
"OffscreenRenderingMode"="fbo"
"PixelShaderMode"="enabled"
"UseGLSL"="disabled"
"msvcr90"="native,builtin"
--
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=29607
Bug #: 29607
Summary: Counter-Strike Source Video Stress Test Camera Aim
Broken
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winehq.org(a)eternaldusk.com
Classification: Unclassified
This is an odd one, but there appears to be a new bug that's affecting a couple
of things in Counter-Strike Source (and potentially other Valve games using the
same engine). It's been a while since I tested with this game, so I don't know
when the actual regression started (and if it was triggered by a Wine update,
or a CSS update, or a driver update). Anyway, here are the symptoms:
When running the Video Stress Test, the camera always remains in it's original
orientation - which is pointing at the ground. Not only is it boring, but it
makes the results of the stress test inaccurate as a comparative reference.
I'm uploading a video demonstrating the bug to: http://youtu.be/A5hZ_E4zMoE
In my brief testing I only noticed one other new issue that might be related to
the same bug: On the character selection screen, the animated models that you
select are looking and pointing their weapons straight up.
My system:
Ubuntu 12.04 Alpha
i980x
12GB RAM
PNY GTX 560 Ti
nVidia binary drivers (nvidia-current-updates: 290.10-0ubuntu1)
Wine 1.3.36 (latest package available - can't currently get .configure to
succeed in Precise due to multiarch integration, so I can't compile 1.3.37)
--
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=30580
Bug #: 30580
Summary: Wine incompatible with alsaequal
Product: Wine
Version: 1.5.3
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winealsa.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: chasevasic(a)gmail.com
Classification: Unclassified
Created attachment 40010
--> http://bugs.winehq.org/attachment.cgi?id=40010
Log from me trying to start starcraft ii
WINE will not work with any program I have which uses the soundcard. The
problem appears to be linked to the alsaequal plugin.
The error I am getting is:
Failed to load plugin "/usr/lib/ladspa/caps.so": /usr/lib/ladspa/caps.so: wrong
ELF class: ELFCLASS64
---
Here is my .asoundrc
ctl.equal {
type equal;
}
pcm.plugequal {
type equal;
slave.pcm "plughw:0,0";
}
pcm.!default {
type plug;
slave.pcm plugequal;
}
------
If I delete .asoundrc wine functions just fine, so my first impression is that
there is some sort of incompatibility with alsaequal. I am however not a linux
dev and the exact error I get seems to be more related to LADSPA which makes no
sense to me.
--
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=14243
Summary: FedExShipManager installer fails with
"fixme:msxml:domdoc_createNode unhandled node type 2"
Product: Wine
Version: CVS/GIT
Platform: Other
URL: http://fedex.com/us/software/
OS/Version: other
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
To reproduce (and get past bug 14241):
wget http://kegel.com/wine/winetricks
sh winetricks dotnet20 vjrun20 wsh56 vcrun2005 vcrun2005sp1 vb6run msxml3
wget ftp://ftp.fedex.com/pub/us/software/FedExShipManager_2356.exe
wine FedExShipManager_2356.exe
This succeeds, but starting the app fails. It seems that the
installer didn't register the app's bin/applogic.exe properly?
0009:Call ole32.CLSIDFromProgID(01313ad8 L"Applogic.Document",0032c308)
ret=782502c1
0009:Call advapi32.RegOpenKeyW(80000000,001ab7b8
L"Applogic.Document\\CLSID",0032c248) ret=7eba3245
0009:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7eba3245
0009:Ret ole32.CLSIDFromProgID() retval=800401f3 ret=782502c1
0009:Call KERNEL32.GetLastError() ret=0169aafb
0009:Ret KERNEL32.GetLastError() retval=0000007a ret=0169aafb
0009:Call advapi32.RegCreateKeyExA(80000002,01313ad8
"Software\\FEDEX\\SHIPNET2000\\SETTINGS",00000000,0032b93b,00000000,0002001f,00000000,0032b940,0032b93c)
ret=0102c253
0009:Ret advapi32.RegCreateKeyExA() retval=00000000 ret=0102c253
0009:Call advapi32.RegQueryValueExA(00000230,0131c528
"InstallDir",00000000,0032b9b0,00000000,0032b9ac) ret=0102c4b6
0009:Ret advapi32.RegQueryValueExA() retval=00000002 ret=0102c4b6
0009:Call user32.MessageBoxA(00020036,0131cb38 "FedEx Ship Manager can not
create a dispatch to the Application Logic. Please make sure the file
\"APPLOGIC.EXE\" resides in the \"\\Bin\" directory.\nFedEx Ship Manager will
now terminate.",008b7d0c "Fatal Error",00000010) ret=0169a287
--
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.