http://bugs.winehq.org/show_bug.cgi?id=425
Dmitry Timoshkov <dmitry(a)codeweavers.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pedro.m.ferreira(a)mail.cm-po
| |rtel.pt
--- Comment #12 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2009-06-17 06:04:56 ---
*** Bug 16112 has been marked as a duplicate of this bug. ***
--
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=18967
Summary: winedevice.exe has encountered an error at each start
(ntoskrnl.exe.MmLockPagableDataSection not
implemented)
Product: Wine
Version: 1.1.23
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mick.mis(a)gmail.com
Each time i launch a windows application with wine i have a dialog box saying
"The program winedevice.exe has encountered a serious problem and needs to
close ..."
In the terminal :
wine: Call from 0x7ee05dc7 to unimplemented function
ntoskrnl.exe.MmLockPagableDataSection, aborting
wine: Unimplemented function ntoskrnl.exe.MmLockPagableDataSection called at
address 0x7ee05dc7 (thread 001a), starting debugger...
--
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=8942
--- Comment #16 from Christian Convey <christian.convey(a)gmail.com> 2009-06-17 03:18:40 ---
(In reply to comment #15)
> Is this still an issue in current (1.1.23 or newer) wine?
Actually, with 1.1.23 I can't even install the game any more. The
installer hangs at what looks like the very end of the process.
(Using Ubuntu Studio 9.04, current wine version from winehq as of 16 June 2009)
--
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=18740
Summary: Use of "unsafe" subset of ALSA causes problems with
PulseAudio
Product: Wine
Version: 1.1.22
Platform: PC
URL: http://0pointer.de/blog/projects/guide-to-sound-apis.h
tml
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
Blocks: 10910
http://0pointer.de/blog/projects/guide-to-sound-apis.html
If we want PulseAudio to work well, we have to limit ourselves to the safe
subset of the ALSA API.
DONTS:
* Do not use "async handlers", e.g. via snd_async_add_pcm_handler() and
friends. Asynchronous handlers are implemented using POSIX signals, which is a
very questionable use of them, especially from libraries and plugins. Even when
you don't want to limit yourself to the safe ALSA subset it is highly
recommended not to use this functionality. Read this for a longer explanation
why signals for audio IO are evil.
* Do not parse the ALSA configuration file yourself or with any of the ALSA
functions such as snd_config_xxx(). If you need to enumerate audio devices use
snd_device_name_hint() (and related functions). That is the only API that also
supports enumerating non-hardware audio devices and audio devices with drivers
implemented in userspace.
* Do not parse any of the files from /proc/asound/. Those files only
include information about kernel sound drivers -- user-space plugins are not
listed there. Also, the set of kernel devices might differ from the way they
are presented in user-space. (i.e. sub-devices are mapped in different ways to
actual user-space devices such as surround51 an suchlike.
* Do not rely on stable device indexes from ALSA. Nowadays they depend on
the initialization order of the drivers during boot-up time and are thus not
stable.
* Do not use the snd_card_xxx() APIs. For enumerating use
snd_device_name_hint() (and related functions). snd_card_xxx() is obsolete. It
will only list kernel hardware devices. User-space devices such as sound
servers, Bluetooth audio are not included. snd_card_load() is completely
obsolete in these days.
* Do not hard-code device strings, especially not hw:0 or plughw:0 or even
dmix -- these devices define no channel mapping and are mapped to raw kernel
devices. It is highly recommended to use exclusively default as device string.
If specific channel mappings are required the correct device strings should be
front for stereo, surround40 for Surround 4.0, surround41, surround51, and so
on. Unfortunately at this point ALSA does not define standard device names with
channel mappings for non-kernel devices. This means default may only be used
safely for mono and stereo streams. You should probably prefix your device
string with plug: to make sure ALSA transparently reformats/remaps/resamples
your PCM stream for you if the hardware/backend does not support your sampling
parameters natively.
* Do not assume that any particular sample type is supported except the
following ones: U8, S16_LE, S16_BE, S32_LE, S32_BE, FLOAT_LE, FLOAT_BE, MU_LAW,
A_LAW.
* Do not use snd_pcm_avail_update() for synchronization purposes. It should
be used exclusively to query the amount of bytes that may be written/read right
now. Do not use snd_pcm_delay() to query the fill level of your playback
buffer. It should be used exclusively for synchronisation purposes. Make sure
you fully understand the difference, and note that the two functions return
values that are not necessarily directly connected!
* Do not assume that the mixer controls always know dB information.
* Do not assume that all devices support MMAP style buffer access.
* Do not assume that the hardware pointer inside the (possibly mmaped)
playback buffer is the actual position of the sample in the DAC. There might be
an extra latency involved.
* Do not try to recover with your own code from ALSA error conditions such
as buffer under-runs. Use snd_pcm_recover() instead.
* Do not touch buffering/period metrics unless you have specific latency
needs. Develop defensively, handling correctly the case when the backend cannot
fulfill your buffering metrics requests. Be aware that the buffering metrics of
the playback buffer only indirectly influence the overall latency in many
cases. i.e. setting the buffer size to a fixed value might actually result in
practical latencies that are much higher.
* Do not assume that snd_pcm_rewind() is available and works and to which
degree.
* Do not assume that the time when a PCM stream can receive new data is
strictly dependant on the sampling and buffering parameters and the resulting
average throughput. Always make sure to supply new audio data to the device
when it asks for it by signalling "writability" on the fd. (And similarly for
capturing)
* Do not use the "simple" interface snd_spcm_xxx().
* Do not use any of the functions marked as "obsolete".
* Do not use the timer, midi, rawmidi, hwdep subsystems.
DOS:
* Use snd_device_name_hint() for enumerating audio devices.
* Use snd_smixer_xx() instead of raw snd_ctl_xxx()
* For synchronization purposes use snd_pcm_delay().
* For checking buffer playback/capture fill level use
snd_pcm_update_avail().
* Use snd_pcm_recover() to recover from errors returned by any of the ALSA
functions.
* If possible use the largest buffer sizes the device supports to maximize
power saving and drop-out safety. Use snd_pcm_rewind() if you need to react to
user input quickly.
--
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=18972
Summary: wine progman => Help on Help pagefaults
Product: Wine
Version: 1.1.23
Platform: PC
URL: http://winehq.org
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: adys.wh(a)gmail.com
$ wine progman
Help => Help on Help pagefaults, winedbg.exe then proceeds to pagefault as well
when trying to output the backtrace.
adys@azura:~/src/wine$ wine progman
wine: Unhandled page fault on read access to 0x00000028 at address 0x7ec1cf03
(thread 0022), starting debugger...
wine: Unhandled page fault on write access to 0x7ebc9999 at address 0x7ebc3e40
(thread 0024), starting debugger...
wine: Unhandled page fault on write access to 0x7ebd5999 at address 0x7ebcfe40
(thread 0026), starting debugger...
wine: Unhandled page fault on write access to 0x7ebc9999 at address 0x7ebc3e40
(thread 0028), starting debugger...
--
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=8133
EA Durbin <ead1234(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|Other |PC
Version|unspecified |1.1.23
--
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=14722
Summary: dialog box problem while installing medal of honor
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Windows XP
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aeleneski(a)comcast.net
When installing Medal of Honor the dialog boxes seem to come up in the
background. An example is when the dialog is presented to enter the serial
number, that opens in another window and you have to click on the taskbar to
access it and then enter it. But then later on, after doing that another box
pops up (saying that the directory does not exist, would you like to create it)
and it does not show up in the foreground. When clicking on the "InstallShield
Wizard" item in the taskbar does not bring it up, but if you Alt-Tab you are
able to see and access the dialog boxes.
--
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=18969
Summary: wined3d driver description string is empty for unknown
cards instead of "Display"
Product: Wine
Version: 1.1.23
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: trisk-winehq(a)forkgnu.org
A minor regression introduced by the new driver description reporting in
http://source.winehq.org/git/wine.git/?a=commit;h=f2e2e3e49947490368900ef06…
is that for cards that are not in the supported list, the driver description is
an empty string instead of the previous "Display".
--
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=18961
Summary: TopoL is crashing immediately after execution
Product: Wine
Version: 1.1.23
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fojtik(a)penguin.cz
Try to run TopoL.exe. A wine crashes instead of running application. The crash
dump is attached in attachment.
I have extracted EXE file and several DLLs, that exactly reproduce the problem.
Please download exe files here.
http://www.penguin.cz/~fojtik/topol/
Please let me know when I omit some DLL.
--
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=9030
EA Durbin <ead1234(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unspecified |1.1.23
--
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.