wine-bugs January 2016

wine-bugs@winehq.org

1 participants
9491 discussions

[Bug 39968] New: alsa sound problem recognizing Logitech USB wireless soundcard
by wine-bugs＠winehq.org 22 Feb '16

22 Feb '16

https://bugs.winehq.org/show_bug.cgi?id=39968 Bug ID: 39968 Summary: alsa sound problem recognizing Logitech USB wireless soundcard Product: Wine Version: 1.9.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)winehq.org Reporter: susancragin(a)gmail.com Distribution: --- Wine alsa does not recognize my wireless usb sound card. I have tested with Dragon Naturally Speaking 13 and Windows Audacity. I set up the wine prefix with sound=alsa before installing. Pulseaudio is disabled on my system. Alsamixer info: Card 2 (set as default using asoundrc) USB-Audio - Logitech Wireless Headset Logitech Logitech Wireless Headset at usb-0000:00:14.0-1, full speed In winecfg, the device seems to be recognized appropriately. It has e.g. Out: Logitech Wireless Headset - USB And the Test Sound works. But when running the program, the sound is very faint and is I believe coming from my system's soundcard. -- 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.

1 3

[Bug 33100] New: ALSA Audio playback in WINE locks up ALSA capture by other applications
by wine-bugs＠winehq.org 22 Feb '16

22 Feb '16

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.

1 6

[Bug 40050] New: Audio device hw:0 gets busy with some games but not all
by wine-bugs＠winehq.org 22 Feb '16

22 Feb '16

https://bugs.winehq.org/show_bug.cgi?id=40050 Bug ID: 40050 Summary: Audio device hw:0 gets busy with some games but not all Product: Wine Version: 1.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sworddragon2(a)aol.com Distribution: --- If I'm starting specific games (currently noticed this in "The Forest") and then trying to capture the sound (for example with "ffmpeg -f alsa -i hw:0 ~/tmp/test.mkv") ffmpeg claims that the audio device hw:0 is busy. But in other games like Guild Wars the device doesn't get busy so that I can capture on it. -- 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.

1 1

[Bug 39743] New: Dragon NaturallySpeaking 13.0 does not train new user or run old one with sound error
by wine-bugs＠winehq.org 22 Feb '16

22 Feb '16

https://bugs.winehq.org/show_bug.cgi?id=39743 Bug ID: 39743 Summary: Dragon NaturallySpeaking 13.0 does not train new user or run old one with sound error Product: Wine-staging Version: 1.7.55 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: susancragin(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 53012 --> https://bugs.winehq.org/attachment.cgi?id=53012 NaturallySpeaking 13.0 crash when installing user voice I created a new 32-bit wine prefix this morning, set the Windows version to 10 (sorry) and installed Dragon NaturallySpeaking 13.0 into it. (Under winecfg, the sound was set to default, which had worked previously.) The NatSpeak installation appeared to go flawlessly. But the program will not run. It starts normally but then says it cannot use my "user," that is, the set of files with my voice data in it. I have tried creating a new user, and that does not work either. I also tried changing the sound to pulseaudio in winecfg, ditto on the no work. An error message says that the program cannot find my sound source. Debian LXDE with all updates. wine-1.7.55 (Staging) Attached: crash report, terminal output. -- 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.

1 14

[Bug 35260] New: Sound weirdness with XCOM: Enemy Within
by wine-bugs＠winehq.org 22 Feb '16

22 Feb '16

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.

1 10

[Bug 36694] New: 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
by wine-bugs＠winehq.org 22 Feb '16

22 Feb '16

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.

1 6

[Bug 39760] New: MDK (MDKD3D.EXE) graphics not drawn correctly
by wine-bugs＠winehq.org 20 Feb '16

20 Feb '16

https://bugs.winehq.org/show_bug.cgi?id=39760 Bug ID: 39760 Summary: MDK (MDKD3D.EXE) graphics not drawn correctly Product: Wine Version: 1.8-rc3 Hardware: x86 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeffz(a)jeffz.name I'm not sure that bug #3569 was actually fixed, but seeing as two different bugs were actually being discussed there (the DirectDraw version of MDK, and the Direct3D version), things were not very clear. I'm splitting it here. Tested on OSX 10.9.5. http://jeffz.name/mdkdemo_repack.tar.bz2 winecfg virtual desktop set to 640x480 cd ~/.wine/drive_c && tar xf ~/mdkdemo_repack.tar.bz2 && cd mdkdemo_repack wine MDKD3D.EXE Credit/intro screen loads. Main menu loads. Start a new game and the loading screen persists to flicker over the game graphics. Confirmed that this bug does not happen on Windows 7. It works fine there. -- 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.

1 5

[Bug 39010] New: Wine msiexec fails while trying to install PhysX
by wine-bugs＠winehq.org 20 Feb '16

20 Feb '16

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.

1 7

[Bug 37538] New: WineBottler: winetricks flashplayer checksum error
by wine-bugs＠winehq.org 20 Feb '16

20 Feb '16

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.

1 3

[Bug 21454] New: Dolphin Wii/GCN Emulator Crashes On Rom Load Due To Graphical Errors?
by wine-bugs＠winehq.org 19 Feb '16

19 Feb '16

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.

1 16

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs January 2016