April 2013 - Wine-bugs - list.winehq.org

[Bug 17660] New: Starcraft slow down when select any building or units
by wine-bugs＠winehq.org 09 Nov '18

09 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=17660 Summary: Starcraft slow down when select any building or units Product: Wine Version: 1.1.16 Platform: PC OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nathnett(a)gmail.com Starcraft slow down when select any building or unit/s. -- 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 39

[Bug 30402] New: Stalker (SoC and CoP) freezes on splash screen
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=30402 Bug #: 30402 Summary: Stalker (SoC and CoP) freezes on splash screen Product: Wine Version: 1.5.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: otaku(a)rambler.ru Classification: Unclassified Created attachment 39742 --> http://bugs.winehq.org/attachment.cgi?id=39742 terminal output with clean wineprefix Sometimes (every 5th time approximately) the game runs perfectly. -- 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 4

[Bug 31921] New: WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-G1GL0q/pkcs11: No such file or directory
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=31921 Bug #: 31921 Summary: WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-G1GL0q/pkcs11: No such file or directory Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kingpin4000(a)shaw.ca Classification: Unclassified Since the last update of wine I have been getting this error which is causing a ton of programs to not work anymore. WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-G1GL0q/pkcs11: No such file or directory I have tryed different distros to rule them out.. All of them get this error on this version of wine?? After restart the folder in the temp folder is renamed if that matters.. So for example its right now looking in folder keyring-G1GL0Q but on next reboot it will be different. Even typing in winecfg in the terminal gives that error so I know its a problem with wine not the distro. -- 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 8

[Bug 33129] New: Resident Evil 4: GLSL completely freeze computer
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=33129 Bug #: 33129 Summary: Resident Evil 4: GLSL completely freeze computer Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl AssignedTo: wine-bugs(a)winehq.org ReportedBy: aurelio(a)archlinux.info Classification: Unclassified with GLSL enabled if run RE4, game and computer (completely, i cannot kill game, X, and etc, i need reboot computer) freeze This freeze occur when approach of first home of game(+/- 1 sec after movie played) System: ArchLinux (Up-to-date) Wine: wine-1.5.25 Graphic card: Radeon 9600 (radeon OSS driver) Attached wine output I cannot attach output(because it's obvious, computer is freezed) -- 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 30331] New: World of Warcraft Mists of Pandaria Beta Unhandled Exception shortly after entering world
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=30331 Bug #: 30331 Summary: World of Warcraft Mists of Pandaria Beta Unhandled Exception shortly after entering world Product: Wine Version: 1.5.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: noah.mccalment(a)gmail.com Classification: Unclassified Created attachment 39639 --> http://bugs.winehq.org/attachment.cgi?id=39639 Console output of wine After loading the World of Warcraft Mists of Pandaria beta client and selecting a premade character, the game world loads just fine. However, shortly afterward, an unhandled exception occurs that crashes the game client. I've attached the straight output below. -- 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 5

[Bug 22354] New: Xfire crash after upgrade to Ubuntu 10.04
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=22354 Summary: Xfire crash after upgrade to Ubuntu 10.04 Product: Wine Version: 1.1.34 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: redplug(a)web.de Created an attachment (id=27353) --> (http://bugs.winehq.org/attachment.cgi?id=27353) Wine Output with WINEDEBUG=+all after upgrade to Ubuntu 10.04 Xfire dont start anymore. It crash with the this bugreport: <?xml version="1.0" encoding="utf-8" ?> <ExceptionReport Version="4"> <Application Build="42127" Command="C:\Programme\Xfire\Xfire.exe"/> <OperatingSystem Type="2"><Version Major="5" Minor="1" Build="2600"/></OperatingSystem> <Exception Code="C0000005" Address="7A6AB486"></Exception> <Registers EAX="00000001" EBX="00000000" ECX="00000000" EDX="00000000" ESI="00000009" EDI="793233C8" CS="0023" EIP="7A6AB486" SS="002B" ESP="0032F1E4" EBP="00000000" DS="002B" ES="002B" FS="0063" GS="006B" Flags="00010246"/> <BackTrace> </BackTrace> </ExceptionReport> -- 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 12

[Bug 31373] New: Bioshock cause Radeon to freeze (GPU lockup)
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=31373 Bug #: 31373 Summary: Bioshock cause Radeon to freeze (GPU lockup) Product: Wine Version: 1.5.9 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: michael(a)araneidae.co.uk Classification: Unclassified Playing Bioshock (1.0, Steam version) causes graphical lockup after a few minutes of play. My graphics stack is [lib32-]ati-dri (etc) 8.0.4-1 or -2 on Arch with a HD 6950 graphics card. In dmesg I see: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec followed by a detailed status dump. In output from startx I see numerous backtraces (I'll have to make a separate message for these, at it seems I can only make one attachment at a time) in X. I'm afraid I've got nothing to report from wine itself as any messages there might have been are drowned in a flood of fixme:d3d:resource_check_usage Unhandled usage flags 0x8. messages! -- 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 8

[Bug 21896] New: sigaltstack: invalid argument
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=21896 Summary: sigaltstack: invalid argument Product: Wine Version: 1.1.39 Platform: x86 URL: http://translate.google.com/translate?hl=en&sl=ja&u=ht tp://quasiquote.org/log2/Erlang&ei=BS2LS5GIHoOulwerrIH PAQ&sa=X&oi=translate&ct=result&resnum=3&ved=0CA4Q7gEw Ag&prev=/search%3Fq%3D%2522sigaltstack%2Binvalid%2Barg ument%2522%26hl%3Den%26client%3Dfirefox-a%26hs%3DPib%2 6rls%3Dcom.ubuntu:en-US:official OS/Version: OpenBSD Status: NEW Keywords: download, source Severity: enhancement Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com When running wine on OpenBSD, you see sigaltstack: Invalid argument several times. It seems to be related to pthread, see: http://quasiquote.org/log2/Erlang google translated: http://translate.google.com/translate?hl=en&sl=ja&u=http://quasiquote.org/l… -- 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 5

[Bug 32947] New: Broken font rendering with many fonts (including Microsoft core fonts) in wine 1.5
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=32947 Bug #: 32947 Summary: Broken font rendering with many fonts (including Microsoft core fonts) in wine 1.5 Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: constantine.gavrilov(a)gmail.com Classification: Unclassified This is a long standing issue with 1.5 versions. Several bugs have been opened and closed but they usually do not get to the core issue. One of the issues (that is listed as closed) is 29250. Here is the beef of the matter. Many true type fonts including core Microsoft fonts (Arial, Times New Roman, Courier New, Tahoma, Verdana) and all built-in true type fonts shipped with Wine (Tahoma, ms-sans-serif, etc.) will use subpixel rendering only at unrealistically big sizes (>= 16), and event then the quality is awful. Other fonts (typically from Dejavu or Vera families) will render just fine and will use subpixel rendering at default sizes. Asking wine to log font decisions shows that wine has decided to disable antialiasing for "problematic" fonts because of the info it got from GASP table. I would like to stress that this is not a problem of fontconfig settings or fontconfig or wine font substitutions. Nor it is a problem of wrong DPI. Native linux applications display just fine, and wine will display similar to Linux if Dejavu or Vera fonts are forced. Additionally, ClientSideGraphics=N (or =Y) has nothing to do with this problem either. Under both settings, the fonts look similar and the decisions based on the GASP table are the same. This setting does not affect the decision to antialias or not, it affects the quality with ClientSideGraphics=N giving better results that are also consistent with the Linux desktop. This feature (using the GASP tables the way they are used) is actually a misfeature because: * shipped wine fonts are not usable for dialogs and menus * native Windows fonts cannot be used because they will not use subpixel rendering but they are still recommended in documentation. I understand that someone desired to get a closer picture to Windows, but what we have is unusable now. As far as I can see, Windows will antialias these fonts just fine (at least starting from size 12), and even when ClearType is not used for size 10, the font is still very crisp and readable. Bottom line, when wine decides to skip antialias for most fonts, the result is very very ugly. I would even say it is not possible to use. I also would like to claim that fontconfig uses subpixel rendering for these fonts just fine (native Linux applications look great) and I would say the results are better (at least definitely not worse) compared to Windows rendering for cases when it decides to skip antialiasing because the size is small. Can we have a configuration setting to opt out of GASP table decisions? -- 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 21

[Bug 31914] New: Recorded frames are in reversed order
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=31914 Bug #: 31914 Summary: Recorded frames are in reversed order Product: Wine Version: 1.5.10 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thedesti(a)yahoo.com Classification: Unclassified I'm using glc-capture to record apllications and games. https://github.com/nullkey/glc/wiki Up to WINE-1.5.9 it was working OK, making a picture like this: http://www.twitch.tv/nuclear_power_plant/b/334759327 Sine the update to WINE-1.5.10, the recorded frames are in reversed order, making the first pixel to the last pixel. It's now looking like this: http://www.twitch.tv/nuclear_power_plant/b/334768276 Also when starting recording the console got flooded with this error: err:d3d:context_bind_fbo >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glBindFramebuffer() @ /var/tmp/portage/app-emulation/wine-1.5.10/work/wine-1.5.14/dlls/wined3d/context.c / 84 It's reproduce able with WINE-1.5.10 to 1.5.14. -- 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 11