wine-bugs December 2014

wine-bugs@winehq.org

1 participants
9003 discussions

[Bug 20648] New: DX-Ball crashes at startup on x86-64 system
by wine-bugs＠winehq.org 19 Apr '15

19 Apr '15

http://bugs.winehq.org/show_bug.cgi?id=20648 Summary: DX-Ball crashes at startup on x86-64 system Product: Wine Version: unspecified Platform: PC-x86-64 URL: http://www.magicwandsoft.com/games/dxball/download.htm l OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: b.brachaczek(a)gmail.com Created an attachment (id=24640) --> (http://bugs.winehq.org/attachment.cgi?id=24640) log from console DX-Ball (free to download, link in URL) crashes every time at startup if it's run under Wine compiled under an x86-64 system. Tried with Ubuntu 9.10 amd64 with official Ubuntu Wine packages. I can also reproduce the same issue if I compile Wine under i386 with gcc flags -msse -msse2 -mfpmath=sse - they're default for x86-64 and probably that's the problem. Log attached. -- 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 10

[Bug 32859] New: Mathematica 8 occasionally crashes on startup
by wine-bugs＠winehq.org 18 Apr '15

18 Apr '15

http://bugs.winehq.org/show_bug.cgi?id=32859 Bug #: 32859 Summary: Mathematica 8 occasionally crashes on startup Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com Classification: Unclassified Created attachment 43395 --> http://bugs.winehq.org/attachment.cgi?id=43395 Backtrace Start Mathematica. If it doesn't crash, try close it and start again, if still not, try other tty or try first wineserver -k or launch with a different LC_ALL... I couldn't find any reliable way to reproduce the bug, it happens in ~10% cases, and it *seems* manipulations above somewhat improve reproducibility. -- 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 23

[Bug 37750] New: Assassin's Creed: graphical issues in the menus and in-game
by wine-bugs＠winehq.org 18 Apr '15

18 Apr '15

https://bugs.winehq.org/show_bug.cgi?id=37750 Bug ID: 37750 Summary: Assassin's Creed: graphical issues in the menus and in-game Product: Wine Version: 1.7.29 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: ee8a5b7dd1e554ef32229c766715f23ba17c9f6c Distribution: --- Created attachment 50263 --> https://bugs.winehq.org/attachment.cgi?id=50263 screenshot (comparison) Text in the menus is too bright/blurred. There are visual glitches in the game as well, as you can see in the attached screenshot. These messages are filling the terminal as soon as the problem appears: >err:d3d:wined3d_debug_callback 0x35a3538: "GL_INVALID_VALUE error generated. Size and/or offset out of range.". >err:d3d_surface:wined3d_volume_upload_data >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glTexSubImage3D @ volume.c / 114 I see the same messages in a couple of other games as well (Metro: Last Light, Burnout Paradise, XCOM:Enemy Unknown). The problem is present since ee8a5b7dd1e554ef32229c766715f23ba17c9f6c is the first bad commit commit ee8a5b7dd1e554ef32229c766715f23ba17c9f6c Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Wed Oct 8 08:47:20 2014 +0200 wined3d: Track texture allocation per-texture. :040000 040000 02dba0093d24ae89c3c4ebcb3de609d01a618614 e5bf7a4032c6c2959631cc5b49d7ba9b73a47a2b M dlls Please let me know if you need debug logs. wine-1.7.33-40-gca51e11 Fedora 20 Geforce 250 / Nvidia binary drivers 340.65 -- 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 17

[Bug 36809] New: valgrind shows an unitialized variable in dlls/dmscript/tests/dmscript.c
by wine-bugs＠winehq.org 17 Apr '15

17 Apr '15

https://bugs.winehq.org/show_bug.cgi?id=36809 Bug ID: 36809 Summary: valgrind shows an unitialized variable in dlls/dmscript/tests/dmscript.c Product: Wine Version: 1.7.20 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-dmusic Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==20119== Use of uninitialised value of size 4 ==20119== at 0x427A0CD: _itoa_word (_itoa.c:180) ==20119== by 0x427D856: vfprintf (vfprintf.c:1634) ==20119== by 0x429E4E1: vsprintf (iovsprintf.c:42) ==20119== by 0x428429E: sprintf (sprintf.c:32) ==20119== by 0x4BC691C: wine_dbgstr_guid (test.h:533) ==20119== by 0x4BC5B0F: test_scripttrack (dmscript.c:222) ==20119== by 0x4BC5D40: func_dmscript (dmscript.c:249) ==20119== by 0x4BC6B3B: run_test (test.h:584) ==20119== by 0x4BC6F29: main (test.h:654) ==20119== Uninitialised value was created by a stack allocation ==20119== at 0x4BC597E: test_scripttrack (dmscript.c:206) ==20119== ==20119== Conditional jump or move depends on uninitialised value(s) ==20119== at 0x427A0D3: _itoa_word (_itoa.c:180) ==20119== by 0x427D856: vfprintf (vfprintf.c:1634) ==20119== by 0x429E4E1: vsprintf (iovsprintf.c:42) ==20119== by 0x428429E: sprintf (sprintf.c:32) ==20119== by 0x4BC691C: wine_dbgstr_guid (test.h:533) ==20119== by 0x4BC5B0F: test_scripttrack (dmscript.c:222) ==20119== by 0x4BC5D40: func_dmscript (dmscript.c:249) ==20119== by 0x4BC6B3B: run_test (test.h:584) ==20119== by 0x4BC6F29: main (test.h:654) ==20119== Uninitialised value was created by a stack allocation ==20119== at 0x4BC597E: test_scripttrack (dmscript.c:206) ==20119== ==20119== Conditional jump or move depends on uninitialised value(s) ==20119== at 0x427ADD7: vfprintf (vfprintf.c:1634) ==20119== by 0x429E4E1: vsprintf (iovsprintf.c:42) ==20119== by 0x428429E: sprintf (sprintf.c:32) ==20119== by 0x4BC691C: wine_dbgstr_guid (test.h:533) ==20119== by 0x4BC5B0F: test_scripttrack (dmscript.c:222) ==20119== by 0x4BC5D40: func_dmscript (dmscript.c:249) ==20119== by 0x4BC6B3B: run_test (test.h:584) ==20119== by 0x4BC6F29: main (test.h:654) ==20119== Uninitialised value was created by a stack allocation ==20119== at 0x4BC597E: test_scripttrack (dmscript.c:206) ==20119== ==20119== Conditional jump or move depends on uninitialised value(s) ==20119== at 0x427AE43: vfprintf (vfprintf.c:1634) ==20119== by 0x429E4E1: vsprintf (iovsprintf.c:42) ==20119== by 0x428429E: sprintf (sprintf.c:32) ==20119== by 0x4BC691C: wine_dbgstr_guid (test.h:533) ==20119== by 0x4BC5B0F: test_scripttrack (dmscript.c:222) ==20119== by 0x4BC5D40: func_dmscript (dmscript.c:249) ==20119== by 0x4BC6B3B: run_test (test.h:584) ==20119== by 0x4BC6F29: main (test.h:654) ==20119== Uninitialised value was created by a stack allocation ==20119== at 0x4BC597E: test_scripttrack (dmscript.c:206) ==20119== ==20119== Conditional jump or move depends on uninitialised value(s) ==20119== at 0x427AEC5: vfprintf (vfprintf.c:1634) ==20119== by 0x429E4E1: vsprintf (iovsprintf.c:42) ==20119== by 0x428429E: sprintf (sprintf.c:32) ==20119== by 0x4BC691C: wine_dbgstr_guid (test.h:533) ==20119== by 0x4BC5B0F: test_scripttrack (dmscript.c:222) ==20119== by 0x4BC5D40: func_dmscript (dmscript.c:249) ==20119== by 0x4BC6B3B: run_test (test.h:584) ==20119== by 0x4BC6F29: main (test.h:654) ==20119== Uninitialised value was created by a stack allocation ==20119== at 0x4BC597E: test_scripttrack (dmscript.c:206) ==20119== ==20119== Conditional jump or move depends on uninitialised value(s) ==20119== at 0x402EB3D: bcmp (vg_replace_strmem.c:965) ==20119== by 0x4BC5B2E: test_scripttrack (dmscript.c:222) ==20119== by 0x4BC5D40: func_dmscript (dmscript.c:249) ==20119== by 0x4BC6B3B: run_test (test.h:584) ==20119== by 0x4BC6F29: main (test.h:654) ==20119== Uninitialised value was created by a stack allocation ==20119== at 0x4BC597E: test_scripttrack (dmscript.c:206) ==20119== ==20119== Conditional jump or move depends on uninitialised value(s) ==20119== at 0x4BC5F76: winetest_vok (test.h:311) ==20119== by 0x4BC6184: winetest_ok (test.h:357) ==20119== by 0x4BC5B4C: test_scripttrack (dmscript.c:222) ==20119== by 0x4BC5D40: func_dmscript (dmscript.c:249) ==20119== by 0x4BC6B3B: run_test (test.h:584) ==20119== by 0x4BC6F29: main (test.h:654) ==20119== Uninitialised value was created by a stack allocation ==20119== at 0x4BC597E: test_scripttrack (dmscript.c:206) ==20119== -- 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 33723] New: EA Origin needs job objects
by wine-bugs＠winehq.org 17 Apr '15

17 Apr '15

http://bugs.winehq.org/show_bug.cgi?id=33723 Bug #: 33723 Summary: EA Origin needs job objects Product: Wine Version: 1.5.31 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: ariscop(a)gmail.com Classification: Unclassified It uses job objects + completion ports to determine if a game is running or has exited. as it doesn't notice a game being closed, you cannot relaunch the game without restarting origin. fixme:ntdll:NtCreateJobObject stub: 0xa32e83c 1f001f <null> fixme:ntdll:NtSetInformationJobObject stub: 0xdead 9 0xa32e890 112 trace:ntdll:NtCreateIoCompletion (0xa32e83c, 1f0003, (nil), 0) fixme:ntdll:NtSetInformationJobObject stub: 0xdead 7 0xa32e934 8 fixme:ntdll:NtAssignProcessToJobObject stub: 0xdead 0xc70 -- 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 27

[Bug 35337] New: GOG.com installer--a small line appears on the progress bar after some time
by wine-bugs＠winehq.org 17 Apr '15

17 Apr '15

http://bugs.winehq.org/show_bug.cgi?id=35337 Bug ID: 35337 Summary: GOG.com installer--a small line appears on the progress bar after some time Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs140(a)gmail.com Classification: Unclassified Created attachment 47135 --> http://bugs.winehq.org/attachment.cgi?id=47135 GOG Installer Log A small vertical line appears on the installer progress bar, you can see it by the end of the installation process. I've marked it with the red circle in the screenshot. I don't know if the issue affects all versions of the GOG.com installer. You can test it with the free Tyrian 2000 installer. -- 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 8

[Bug 32719] New: WISIS.EXE Crash on opening a db
by wine-bugs＠winehq.org 17 Apr '15

17 Apr '15

http://bugs.winehq.org/show_bug.cgi?id=32719 Bug #: 32719 Summary: WISIS.EXE Crash on opening a db Product: Wine Version: 1.5.21 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: alessio(a)dba.it Classification: Unclassified Created attachment 43174 --> http://bugs.winehq.org/attachment.cgi?id=43174 Backtrace of the error Crash every we try to open a db with WISIS.EXE -- 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

[Bug 36897] New: No sound recording
by wine-bugs＠winehq.org 17 Apr '15

17 Apr '15

http://bugs.winehq.org/show_bug.cgi?id=36897 Bug ID: 36897 Summary: No sound recording Product: Wine Version: 1.7.22 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: minor Priority: P2 Component: wineoss.drv Assignee: wine-bugs(a)winehq.org Reporter: abi(a)abinet.ru I have a problem to use microphone in Teamspeak3. I tried several other simple windows programs and got the same behavior, so I suspect something wrong globally with microphone support for OSS. 1. I tried USB microphone and analog one. 2. Native software works. 3. I can choose correct OSS device in winecfg and in teamspeak client. 4. No visible errors generated. 5. Download link is http://dl.4players.de/ts/releases/3.0.15/TeamSpeak3-Client-win32-3.0.15.exe 6. I tried FreeBSD 10 and PC-BSD is case I compiled something wrong. 7. Attach is USB microphone. The same (except other pcm device) applies to analog test with rear or front panel. -- 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 26333] New: Star Wars GB CC 1.0x: crash on pressing "Multiplayer"->"Show Games"
by wine-bugs＠winehq.org 17 Apr '15

17 Apr '15

http://bugs.winehq.org/show_bug.cgi?id=26333 Summary: Star Wars GB CC 1.0x: crash on pressing "Multiplayer"->"Show Games" Product: Wine Version: 1.3.15 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: bojan(a)antonovic.ch Created an attachment (id=33552) --> (http://bugs.winehq.org/attachment.cgi?id=33552) crash log for Wine 1.3.15 A plain crash. -- 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 7

[Bug 11364] New: WinRar doesn' t fully utilize two CPU cores in multithreading mode
by wine-bugs＠winehq.org 17 Apr '15

17 Apr '15

http://bugs.winehq.org/show_bug.cgi?id=11364 Summary: WinRar doesn't fully utilize two CPU cores in multithreading mode Product: Wine Version: CVS/GIT Platform: PC URL: http://rarlabs.com/download.htm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: t.artem(a)mailcity.com WinRar doesn't fully utilize two cores of an SMP system if it has detected them. On average WinRar's CPU usage is around 140-160% on a dual core SMP system, while the best usage will be 200%. Anyway thank you for resolving bug 7551. -- 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 45

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 December 2014