Displaying 4 results from an estimated 4 matches for "got_data_sink".
2012 Oct 29
15
[Bug 56535] New: Resident evil 4 with wine: crash
https://bugs.freedesktop.org/show_bug.cgi?id=56535
Priority: medium
Bug ID: 56535
Assignee: nouveau at lists.freedesktop.org
Summary: Resident evil 4 with wine: crash
Severity: critical
Classification: Unclassified
OS: Linux (All)
Reporter: king.infet at gmail.com
Hardware: x86 (IA32)
Status:
2012 May 06
1
wine not recognizing my graphics card
I have several games installed, but only one of them (diablo 2) is working. All of the others give me some error about not being able to find a graphics card that works. All of the games have worked before, under a previous kubuntu release (am currently using 12.04).
One of the game tips from winehq (i believe for nwn2) was to go into regedit and change the entries in
2011 Oct 19
0
Steins;Gate crashes on start up
...d usage flags" errors]
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:gstreamer:init_new_decoded_pad Linking: 0
fixme:gstreamer:no_more_pads Done
fixme:gstreamer:got_data_sink Triggering 0x79b42e48 0xb2c
err:d3d:resource_init Out of memory!
fixme:d3d_texture:texture_init Failed to create surface 0x10d20c48, hr 0x8876017c
wine: Unhandled page fault on read access to 0x00000000 at address 0x4a44a7 (thread 0009), starting debugger...
Unhandled exception: page fault on read...
2012 Mar 01
2
Eligium on Ubunto 11.10 Wine 1.3.28
...pad Linking: 0
fixme:gstreamer:no_more_pads Done
fixme:gstreamer:event_sink 0x7888f8a0 stub tag
fixme:gstreamer:event_sink 0x79208878 stub tag
fixme:gstreamer:event_sink 0x792088a0 stub tag
fixme:gstreamer:event_sink 0x792088c8 stub tag
fixme:gstreamer:event_sink 0x79208918 stub tag
fixme:gstreamer:got_data_sink Triggering 0x78899000 0x264
fixme:gstreamer:watch_bus mpegaudioparse0: GStreamer encountered a general stream error.
fixme:gstreamer:GST_QueryInterface No interface for {56a868b3-0ad4-11ce-b03a-0020af0ba770}!
Followed 60 seconds later by what is at the end of this log below.
Code:
[14:11:19...