August 2010 - Wine-bugs - list.winehq.org

[Bug 14076] New: UT3 Wine C++ Runtime Library
by wine-bugs＠winehq.org 01 Oct '10

01 Oct '10

http://bugs.winehq.org/show_bug.cgi?id=14076 Summary: UT3 Wine C++ Runtime Library Product: WineHQ Apps Database Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: blocker Priority: P1 Component: appdb-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: Gendeck(a)gmail.com Critical error when i launch the game. I have last wine version. The game no works with UT3v1.0 and UT3v1.2 with same error. Wine is compatible with aticrossfire?.. Because i have 2 ati 3850 :) -- 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 34

[Bug 16636] New: Black & White 2 Graphics Glitches and Crash
by wine-bugs＠winehq.org 01 Oct '10

01 Oct '10

http://bugs.winehq.org/show_bug.cgi?id=16636 Summary: Black & White 2 Graphics Glitches and Crash Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ryanshow(a)gmail.com Created an attachment (id=18212) --> (http://bugs.winehq.org/attachment.cgi?id=18212) a zipped logfile, made from the command "wine white.exe > bw2err.log 2>&1" I have the latest wine git as of December 26th 2008. I installed Black and White 2, with both the version 1.1 and 1.2 patches. I also installed the No-CD patch for SecuROM reasons. The game opens just fine. The menus work great. The intro video works great as well. After the video the game loads and that's where the graphical glitches begin. It looks as if there are two seperate rendering schemes going on at the same time. One of the schemes only renders the game's water, and the other renders the game's land. I have the game in a 800x600 virtual wine desktop, and the water rendering portion seems to occupy a 640x480 square in the bottom left corner of the game. The rest is occupied by the land rendering. Interactive objects such as the game's "creature" the player hand, and scrolls seem to be unaffected by this issue. I've also attached a screenshot so that what I'm saying might be better understood. The second issue is that the game crashes not long after selecting a creature. If you skip the tutorial island and go straight to the mainland (by pressing ESC). The game will progress into an in-game video where you're flying over a reddish sea to an island. Half-way to that island the game crashes. The attached log files seem to indicate that I'm running out of memory, but my computer's memory shouldn't be an issue. I'm running Ubuntu Intrepid 64 bit with 4 gigs of ram and an nVidia 8600 GTS with 512MB of vram. Also, for some reason when I attempted to direct the output of stdout and stderr to the log file, the debug output wasn't fully captured. I've included the history of my bash prompt so that it shows the debug output of the previous run as well, which had identical results to the one I captured in the log file. -- 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 13

[Bug 20865] New: Steam login window jumps around the screen when moved
by wine-bugs＠winehq.org 01 Oct '10

01 Oct '10

http://bugs.winehq.org/show_bug.cgi?id=20865 Summary: Steam login window jumps around the screen when moved Product: Wine Version: 1.1.33 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austin.lund(a)gmail.com When running steam in Wine, at login screen if you move the window around, it appears to jump across the screen in a jerky manner, especially if the cursor is moved quickly. A trace using WINEDEBUG='+tid,+event,+x11drv,+win,+relay' (attached) shows that sometimes the X11 driver is getting ConfigureNotify messages after the window has moved but they seem to contain the wrong values for the position on the window. Sometimes the window is moved by the ConfigureNotify handler back to where it was originally, just for Steam to move it again. It is possible to see this if you parse the log with: grep -E 'win:SetWindowPos|x11drv:sync_window_position|event:X11DRV_ConfigureNotify' -- 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 46

[Bug 22321] New: Spotify cant cant be maximized
by wine-bugs＠winehq.org 30 Sep '10

30 Sep '10

http://bugs.winehq.org/show_bug.cgi?id=22321 Summary: Spotify cant cant be maximized Product: Wine Version: 1.1.42 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: Eldmannen+wine(a)gmail.com The maximize button in the Spotify title bar does not work. When I click it, Spotify stays the same size but gets moved to the top-left corner. -- 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 20993] New: Spotify window does not maximise
by wine-bugs＠winehq.org 30 Sep '10

30 Sep '10

http://bugs.winehq.org/show_bug.cgi?id=20993 Summary: Spotify window does not maximise Product: Wine Version: 1.1.34 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: leighmanthegreat(a)hotmail.com Created an attachment (id=25169) --> (http://bugs.winehq.org/attachment.cgi?id=25169) terminal output when clicking the maximise button Clicking the maximise button just blinks the window, it does not maximise. -- 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 15

[Bug 23315] New: amp3dj.ocx fails to register
by wine-bugs＠winehq.org 29 Sep '10

29 Sep '10

http://bugs.winehq.org/show_bug.cgi?id=23315 Summary: amp3dj.ocx fails to register Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alerinaldi(a)linuxzogno.org Created an attachment (id=29060) --> (http://bugs.winehq.org/attachment.cgi?id=29060) The OCX file Hello, amp3dj.ocx is used in many DJ and radio automation software. It fails to register in Wine, so those programs cannot be used. -- 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 14

[Bug 23070] New: BitComet: Black background in treeview
by wine-bugs＠winehq.org 28 Sep '10

28 Sep '10

http://bugs.winehq.org/show_bug.cgi?id=23070 Summary: BitComet: Black background in treeview Product: Wine Version: 1.2-rc2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=28640) --> (http://bugs.winehq.org/attachment.cgi?id=28640) Image showing the problem Steps to reproduce: 1) remove ~/.wine 2) winetricks gecko 3) wine bitcomet_setup.exe do default installation 4) wine BitComet.exe Behaviour: Background under treeview is black Expected behaviour: Background should be white (or transparent?) winetricks cc580 helps Additional info: Please be sure that you're running Wine from git repository at least from 07.06.2010 as it should incorporate Nikolay Sivov patch which is named "Fix index check condition for RB_SHOWBAND" -- 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 9

[Bug 20257] New: Left 4 Dead:Crashes when viewing MOTD while in 'Crash Course' map.
by wine-bugs＠winehq.org 25 Sep '10

25 Sep '10

http://bugs.winehq.org/show_bug.cgi?id=20257 Summary: Left 4 Dead:Crashes when viewing MOTD while in 'Crash Course' map. Product: Wine Version: 1.1.30 Platform: PC-x86-64 URL: http://ubuntuforums.org/showthread.php?p=8048763#post8 048763 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: darkandor2003(a)yahoo.com See URL. My user name is 'blattengel' on there. '8Kuula' is another with the same problem. Read that thread for lots of details about this bug. I'll reiterate the details below. When you join a server in Left 4 Dead, sometimes you see a box named MOTD (Message Of The Day). A setting on the server toggles the visibility of the MOTD on start. The client has no control in the MOTD popping up. The game crashes strait to the desktop (no wine error window) when I join a server that displays the MOTD on the 'Crash Course' map. It has happened on a few other occasions (MOTD and a different map), but I didn't keep track of what other map(s) it was. 8Kulla claimed a couple other maps (see URL). The game does not crash if the MOTD is not viewed. Wine Version was 1.1.30 with the crashes. I tried out 1.1.29, and I still got the MOTD crash. I did not try out 1.1.28, I skipped it and used 1.1.27 when hearing 8Kuula's suggestion. I don't get the mentioned MOTD crash with 1.1.27. Regression? I didn't use a clean .wine directory. 8Kuula stated he used a clean one with a few modifications. I'm using a wine prefix dedicated to steam, I might have installed mono in that prefix. Also in that prefix, I installed the fonts, and some registry changes in regard to graphics: [HKEY_CURRENT_USER\Software\Wine\Direct3D] "DirectDrawRenderer"="opengl" "Multisampling"="disabled" "OffscreenRenderingMode"="fbo" "PixelShaderMode"="enabled" "RenderTargetLockMode"="textex" "UseGLSL"="enabled" "VertexShaderMode"="hardware" "VideoMemorySize"="1024" Here is the line I use to launch Left 4 Dead (it is inside a script): DISPLAY=:1.0 WINEDEBUG=-all XMODIFIERS='' WINEPREFIX="/home/andrew/.PlayOnLinux/wineprefix/Steam" wine steam.exe -applaunch 500 +mat_hdr_level 0 +mat_queue_mode 2 -w 1280 -h 1024 -dxlevel 81 As an explanation of that line, I used .PlayOnLinux to install steam in a new prefix. I launch Left 4 Dead using "steam.exe -applaunch 500". Each sequential argument is sent to Left 4 Dead. The mat_hdr_level, and mat_queue_mode make the game run faster. w and h set the resolution. dxlevel set to 81 (8.1) makes the game run faster. In regard to the DISPLAY I'm running the game in a separate X session (fixes issues with the keyboard not putting input into the applications and stuff). This stuff shouldn't be relevant, but I'm putting it there just in case. You'll see 8Kuula's crash output, as well as a mini dump at the URL. Kinda nice how Left 4 Dead leaves a mini dump when it crashes. If you need me to do anything, just ask me, and tell me how to do it. I'd really like to see this fixed. -- 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 18

[Bug 24080] New: [HL2+Portal] wine client error:34: write: Bad file descriptor
by wine-bugs＠winehq.org 24 Sep '10

24 Sep '10

http://bugs.winehq.org/show_bug.cgi?id=24080 Summary: [HL2+Portal] wine client error:34: write: Bad file descriptor Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: michael.monreal+wine(a)gmail.com Created an attachment (id=30291) --> (http://bugs.winehq.org/attachment.cgi?id=30291) Full log Half-Life 2 (and Portal) starts up find but just exits when I try to start a game. The menu background "map" is rendered correctly though. On the console, the only hint is wine client error:34: write: Bad file descriptor You will find the full log attached. I tried to produce a debug log but that was quickly at 1gb before the steam window was even up and running... I tried "WINEDEBUG=+relay,+seh,+tid" as mentioned in the FAQs. Please tell me what else I can try to get a usable log. Some notes: - wine 1.2.0 from Fedora 13 - SELinux is disabled on this system - same results with both pulseaudio on and completely off (using alsa) - GeForce 7950 with 195.36.31 drivers - other steam games (Torchlight) work great - reinstalled everything on a clean WINEPREFIX which now only has steam -- 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 17

[Bug 14586] New: Installer fails with "access denied" error.
by wine-bugs＠winehq.org 23 Sep '10

23 Sep '10

http://bugs.winehq.org/show_bug.cgi?id=14586 Summary: Installer fails with "access denied" error. Product: Wine Version: 1.0.0 Platform: PC URL: http://www.anquet.co.uk/demo.aspx OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: prlewis(a)letterboxes.org Please note that this is a different installer from the one described in bug #14585. When running the demo installer, downloaded from http://www.anquet.co.uk/demo.aspx (the file should be called Anquet_Maps_v06_6.2.2.exe, NOT setup.exe), the installer crashes very early on. Wine produces the following on the console: C:\windows\temp\WZSE0.TMP>.\AnquetMapsV06.msi Access denied Thanks. -- 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 13