https://bugs.winehq.org/show_bug.cgi?id=39450
Bug ID: 39450
Summary: The polish FAQ is absolutely terrible
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: d33tah(a)gmail.com
Distribution: ---
I just stumbled upon this wiki article:
http://wiki.winehq.org/FAQ_pl
Somewhere in the middle of the article there are so many spelling mistakes and
the style is so bad it's barely comprehensible. There might be some useful
information there, but the article needs a lot of work from someone who knows
how to write proper Polish. Could you let the Polish translation team know?
Also, I replaced a word starting with "drug" (drugi? drugÄ…? either of those)
meaning "second" to "kolejny" ("next") because the word "drug" is not allowed.
The spam filter is actually making it much more difficult to write articles.
--
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=29590
Bug #: 29590
Summary: Search results do not update on webpage (IE8)
Product: Wine
Version: 1.3.36
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: msxml3
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ocean04(a)suomi24.fi
Classification: Unclassified
winetricks ie8
Open http://asunnot.oikotie.fi
Search should update automatically every time you make changes to form fields,
but does nothing.
Workaround winetricks msxml3
I'll attach msxml log. Most interesting parts are:
003d:fixme:msxml:httprequest_get_statusText stub 0x3c82428 0x2b53cd8
and many lines like:
003d:trace:msxml:domdoc_loadXML
(0x36ce620)->(L"{\"responseHeader\":{\"status\":0,\"QTime\":11},\"response\":{\"numFound\":22852,\"start\":0,\"docs\":[]}}"
0x268c612)
003d:err:msxml:doparse Start tag expected, '<' not found
003d:trace:msxml:domdoc_loadXML (0x3cef120)->(L"{\"time\":1326303123.1712}"
0x268bfb2)
003d:err:msxml:doparse Start tag expected, '<' not found
--
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=33100
Bug #: 33100
Summary: ALSA Audio playback in WINE locks up ALSA capture by
other applications
Product: Wine
Version: 1.5.25
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winealsa.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: torsten.crass(a)eBiology.de
Classification: Unclassified
Hi there,
when trying to record sound (e.g. using arecord) played by some
application running on WINE (e.g. vlc.exe) via ALSA, and if the
recording application is launched *before* the playback application,
recording stops immediately when playback starts, and after a while ALSA
reports an "Input/output error". This does not happen with native
playback applications, e.g. the Linux version of vlc.
Funny enough, if recordings starts *after* playback has begun,
everything works fine.
How to reproduce:
1. In a terminal, issue
sudo alsactl restore; arecord -D default -f dat -v -V stereo test.wav
2. In another terminal, launch vlc.exe by issuing something like
WINEPREFIX=/path/to/prefix wine /path/to/vlc.exe /path/to/some/audiofile
3. Wait for a few seconds... and see arecord complaining:
arecord: pcm_read:1801: read error: Input/output error
4. Re-launch arecrod:
sudo alsactl restore; arecord -D default -f dat -v -V stereo test.wav
5. Watch arecord recording happily ever after.
I initially suspected WINE to somehow force access to my soundcard's
capture device (A SB Live, which seems not to be dsnoop'd by default),
but after creating a dsnoop'd device (which did allow for multiple
simultaneous recordings with arecord when playing back audio with
Linux's vlc) and teaching WINE to actually use it, the problem
unfortunately remained.
Best regards --
Torsten
P.S. If filed this bug with Debian's wine-unstable-alsa package some two months
ago already, but since there hasn't been a single reply up to now and since the
problem still remains with 1.5.25 (Debian is still at 1.5.6), I found it
appropriate to directly re-file this report at WINE's bug tracking system.
--
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=35260
Bug ID: 35260
Summary: Sound weirdness with XCOM: Enemy Within
Product: Wine
Version: 1.7.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winealsa.drv
Assignee: wine-bugs(a)winehq.org
Reporter: lama(a)lamamail.de
Classification: Unclassified
This is a strange one... I'll just describe what happened:
- I'm using the digital out on my sound card. This works fine with everything
but this game in WINE
- Got the game working after registering XAudio2_7.dll
- There is no sound whatsoever ingame (also no sound options beyond a mixer)
- After running the game I have no sound anywhere anymore, even after closing
all WINE processes. No errors while playing though (so it's not blocked), just
quiet
- Mixer settings are fine
- Turns out the default ALSA device has been changed to the analog output,
even after explicitly selecting the digital output (instead of default) in
WINE. Only a reboot fixes this. ALSA documentation doesn't even mention this as
a possibility. Oh, and game audio still isn't played through that either.
I've tested this with WINE 1.7.9 and built from GIT.
--
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=36694
Bug ID: 36694
Summary: Using PBM_SETPOS to change the position of a progress
bar to what it was before after a style change (for
instance, leaving marquee mode) does not redraw the
progress bar
Product: Wine
Version: 1.7.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: pietro10(a)mac.com
Created attachment 48733
--> http://bugs.winehq.org/attachment.cgi?id=48733
The test program that can be used to duplicate this behavior.
If you do this when you switch out of marquee mode on a progress bar:
SendMessage(pbar, PBM_SETMARQUEE, FALSE, 0);
SetWindowLongPtr(pbar, GWL_STYLE, GetWindowLongPtr(hwnd, GWL_STYLE) &
~PBS_MARQUEE);
SendMessage(pbar, PBM_SETPOS, currentPos, 0);
the progress bar will not redraw, and thus will continue to show the marquee
animation frozen at the place it was at the time of the above call.
Attached is a sample program that will demonstrate this behavior. Set one
value, then click Marquee and Set again. On Windows XP (at least), the progress
bar will redraw properly with the second click of Set. The attached file is
also available at
https://github.com/andlabs/misctestprogs/blob/master/winprogresstest.c.
(As marquees are a comctl32 version 6 feature, you may need a manifest file.)
Looking at the soruce, I see here -
http://source.winehq.org/source/dlls/comctl32/progress.c#L639 - that the
implementation's handling of PBM_SETPOS only draws the progressbar if the new
position is different. Thus, I could come up with a variety of ways to fix it,
such as adding a style change check there, or always redrawing the progress
bar, or redrawing on a style change... but I don't know which is the most
correct, so I'll leave it to the experts.
Thanks.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39010
Bug ID: 39010
Summary: Wine msiexec fails while trying to install PhysX
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: ban.artem.v(a)gmail.com
Distribution: ---
Created attachment 51964
--> https://bugs.winehq.org/attachment.cgi?id=51964
Output I got trying to install PhysX with winetricks
I tried to install Mass Effect 2. Firstly I tried to run PhysX installer
from game setup. I got message 'The program msiexec.exe has encountered
a serious problem and needs to close. We are sorry for the inconvenience'.
Then I tried to install PhysX with winetricks. Then I downloaded different
versions of PhysX from official site and runned 'wine msiexec /i' manually.
Then I tried using msiexec downloaded from the Internet. I got the same
error every time.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=37538
Bug ID: 37538
Summary: WineBottler: winetricks flashplayer checksum error
Product: Wine
Version: 1.7.30
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: darylhokw(a)gmail.com
Created attachment 49955
--> https://bugs.winehq.org/attachment.cgi?id=49955
Screenshot taken from the error message
Tried to isntall a .exe file using flashplayer in winetricks but i got
winetricks flashplayer checksum error
--
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=21454
Summary: Dolphin Wii/GCN Emulator Crashes On Rom Load Due To
Graphical Errors?
Product: Wine
Version: 1.1.35
Platform: x86-64
OS/Version: Mac OS X 10.6
Status: UNCONFIRMED
Severity: critical
Priority: P5
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: justinsboyd(a)gmail.com
The Dolphin app starts up normally, and runs perfectly until you begin the
emulation.
When you launch a rom, the following occurs-
A window appears saying No Possible Memory Base Pointer Found!
Then I get a message saying that the app has encountered a serious problem and
needs to close...
I have traced the problem to a possible solution though-
A graphical error...
Looking at the Dolphin website, I saw the following.
======= Runtime Library Requirements =======
Dolphin needs you have to have the libraries listed below installed.
[Windows]
-MS Visual C++ Runtime 2008 SP1: This fixes the "side by side" / "application
config" & model errors
Microsoft VC++ 2008 SP1 Redist x86 - For 32bit Windows
Microsoft VC++ 2008 SP1 Redist x64 - For 64bit Windows
-The DirectX March 2009 Runtime: This fixes the plugin loading errors
Note: THIS MEANS UPDATE YOUR DIRECTX EVEN IF YOU HAVE THE VERSION 9.0c or 10 or
10.1!!!!!!
Microsoft DirectX Updater
[Linux]
-install libbluetooth: fixes the "PANIC failed to load plugin
Plugins/libPlugin_wiimote.so" error for linux users
======= Video Card Requirements =======
You must have a video card that support OpenGL 2.x fully or Direct3D 9.0c.
Note: The Direct3D9 video plugin is old/outdated and it looks like it doesn't
work anymore. We recommend using the Dolphin OpenGL Video plugin for better
video emulation.
Note: Make sure your drivers are up to date!
So I tried using winetricks to install these missing programs, but found that
Dolphin still encountered the same problem as before.
--
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=33581
Bug #: 33581
Summary: Wine does not quit gracefully
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: olaf.schumann(a)gmx.de
Classification: Unclassified
Quitting Wine will not ask the open programs to quit. It just shuts down
everything.
--
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=12217
Summary: Documentation should be in XML and not SGML format
Product: Wine
Version: 0.9.58.
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: documentation
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
We need to convert the documentation to proper XML format instead of SGML.
Aside from allowing us to use modern build tools, this also allows Wine's
documentation to happily sit alongside other system documentation and, for
instance, be indexed by scrollkeeper.
--
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.