http://bugs.winehq.org/show_bug.cgi?id=24577
Summary: Insaniquarium Deluxe 1.1 does not run at all with
FGLRX
Product: Wine
Version: 1.3.3
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gururise(a)gmail.com
I have Insaniquarium Deluxe 1.1 installed on two different computers for my
kids. Both are running the latest Ubuntu 10.04 using wine 1.3.3
On one, I run the nvidia binary driver and Insaniquarium works fine (in desktop
mode) under wine.
On the other, I run the fglrx binary driver (v 10.9 hotfix) and Insaniquarium
will not even start up and spit outs the following error:
fixme:win:EnumDisplayDevicesW ((null),0,0x32ef50,0x00000000), stub!
fixme:ddraw:ddraw7_GetMonitorFrequency iface 0x134820, frequency 0x5d453c stub!
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to
16
fixme:mixer:ALSA_MixerInit No master control found on HDA ATI HDMI, disabling
mixer
err:seh:setup_exception_record stack overflow 876 bytes in thread 0009 eip
7ed9e177 esp 00230fc4 stack 0x230000-0x231000-0x330000
--
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=31261
Bug #: 31261
Summary: League of Legends: server always busy with builtin
wininet; crashes with native
Product: Wine
Version: 1.5.9
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wininet
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rmmartins(a)gmail.com
Classification: Unclassified
When I try to log in to League of Legends with builtin wininet (no override) it
always answers with "server busy, try again later". When I install wininet with
winetricks and try to log in again, it crashes with attached backtrace, no
matter what login/password I use.
My system is Debian Sid 32-bit, wine 1.5.9 (compiled by me, with patches, as
instructed by Daniel Riffo on AppDB). I don't know if it helps, but the exact
same problem happens with wine 1.4.1 provided by Sid's apt repo.
It's my first bug report, so if I need to send any more info, please tell me.
--
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=31281
Bug #: 31281
Summary: Red Alert 3 on Mac renders vertices in software
Product: Wine
Version: 1.5.9
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cdavis(a)mymail.mines.edu
Classification: Unclassified
Playing Red Alert 3 on my Mac (the Windows version, with Wine, since I bought
it before there even was a Mac version) is extremely slow, almost to the point
of being unplayable.
So, I investigated with Apple's handy OpenGL Profiler, and I discovered, much
to my horror, that the GL was rendering the vertices in software. Huh?
In general, this normally happens when Mac OS thinks the GPU can't do it in
hardware. I can't figure out why it thinks that in this case, though. As far as
I can tell, we aren't exceeding any of the limits that we can query with GL's
Get command, so I suspect that the vertex shader is exceeding some sort of
limit.
Hacking Mesa to set the NoRecovery PFA doesn't help. I was baffled... until I
went back, re-read the documentation, and discovered that NoRecovery *only
affects fragment processing*. What? So there's no way to force only-hardware
vertex processing? (Thank God fragment processing was still in hardware, or it
would have been even worse.)
--
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=23865
Summary: Microsoft Wine Guide (16-bit) unable to find files
whose names end with .
Product: Wine
Version: 1.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Created an attachment (id=29962)
--> (http://bugs.winehq.org/attachment.cgi?id=29962)
+relay,+int21,+mmio log compressed with bzip2
This bug applies to Microsoft Wine Guide 1.0a, a multimedia CD-ROM from 1995
which works with Windows 3.1 and later.
The program is unable to read some files from the CD-ROM which have names
ending in a dot. For example:
$ ls -l /media/cdrom/mswptime/vo/
total 5142
-rwxrwxrwx 1 root root 136888 1995-01-28 12:48 bordeaux.
-rwxrwxrwx 1 root root 133676 1995-01-28 12:48 burgundy.
-rwxrwxrwx 1 root root 82410 1995-01-28 12:48 flute.
-rwxrwxrwx 1 root root 123796 1995-01-28 12:49 port.
-rwxrwxrwx 1 root root 206696 1995-01-28 12:50 red.
-rwxrwxrwx 1 root root 3494956 1995-04-05 13:00 score.
-rwxrwxrwx 1 root root 91972 1995-01-28 12:53 sherry.
-rwxrwxrwx 1 root root 705278 1995-01-20 15:07 title.
-rwxrwxrwx 1 root root 178492 1995-01-28 12:41 title.2
-rwxrwxrwx 1 root root 108658 1995-01-28 12:54 white.
The program appears to be trying to open the corresponding name without a dot.
Start wine.exe in the root directory of the CD-ROM. A Microsoft Home splash
window opens, and there are several error dialog boxes about DLLs; click Ignore
to dismiss each one. The main window then opens. A sound should play but
doesn't. This console output:
err:mmio:MMIO_ParseExtA No . in szFileName: "F:\\MSWPTIME\\vo\\title"
Click WINE TASTING WITH OZ, then THE BASICS, then GLASSES. Each loudspeaker
icon should play a sound clip when clicked. Instead you get console output like
this (one line on clicking each button):
err:mmio:MMIO_ParseExtA No . in szFileName: "F:\\MSWPTIME\\vo\\port"
err:mmio:MMIO_ParseExtA No . in szFileName: "F:\\MSWPTIME\\vo\\sherry"
err:mmio:MMIO_ParseExtA No . in szFileName: "F:\\MSWPTIME\\vo\\red"
err:mmio:MMIO_ParseExtA No . in szFileName: "F:\\MSWPTIME\\vo\\white"
err:mmio:MMIO_ParseExtA No . in szFileName: "F:\\MSWPTIME\\vo\\flute"
err:mmio:MMIO_ParseExtA No . in szFileName: "F:\\MSWPTIME\\vo\\burgundy"
err:mmio:MMIO_ParseExtA No . in szFileName: "F:\\MSWPTIME\\vo\\bordeaux"
The attached log is for WINEDEBUG=+relay,+int21,+mmio, starting wine.exe,
clicking Ignore for each dialog box, then clicking the above sequence.
--
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=28817
Bug #: 28817
Summary: kernel32/tests/thread.ok fails under valgrind
Product: Wine
Version: 1.3.30
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Classification: Unclassified
After adding compiler options to work around bug 28640,
kernel32/thread.ok passes on ubuntu 11.10, but under valgrind
it fails with
thread.c:1413: Test failed: Expected FPU control word 0x27f, got 0x37f.
thread.c:1416: Test failed: Expected FPU control word 0x27f, got 0x37f.
thread.c:1420: Test failed: Expected FPU control word 0xf60, got 0xf7f.
thread.c:1423: Test failed: Expected FPU control word 0x27f, got 0x37f.
thread.c:1426: Test failed: Expected FPU control word 0xf60, got 0xf7f.
This could well be a problem with valgrind or how I'm using it. I'm using
VALGRIND_OPTS="--trace-children=yes --track-origins=yes \
--gen-suppressions=all --suppressions=`pwd`/suppressions \
--leak-check=no --num-callers=30 --workaround-gcc296-bugs=yes \
--vex-iropt-precise-memory-exns=yes -v"
export VALGRIND_OPTS
and the stock valgrind 3.6.1 that comes with ubuntu 11.10.
--
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=13606
Summary: msys is *incredibly* slow
Product: Wine
Version: 1.0-rc3
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kirr(a)landau.phys.spbu.ru
When running configure of a program in msys under wine the whole process is
incredibly slooooow compared to the same under Windows.
I've tracked the problem down to following:
$ export WINEPREFIX=`pwd`/msystest
$ wineboot -i
$ cd msystest/drive_c
$ wget -c
http://downloads.sourceforge.net/mingw/msysCORE-1.0.11-2007.01.19-1.tar.bz2
$ mkdir msys
$ cd msys
$ tar xfj ../msysCORE-1.0.11-2007.01.19-1.tar.bz2
$ wineconsole bin/sh.exe --login -i
--- in msys console ---
# time for i in 1 2 3 4 5; do echo $i; done
...
real 0m0.021s
# time for i in 1 2 3 4 5; do /bin/echo $i; done
...
real 0m3.396s
i.e. each fork of /bin/echo takes approximately almost *1* second!
On Windows both examples runs fast, although /bin/echo case is slightly slower,
but still speed ratio is not *that* big.
Thanks beforehand.
--
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=24602
Summary: NWN2 suffers from shadows flickering on ATI cards
(fglrx driver)
Product: Wine
Version: 1.3.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: NightNord(a)gmail.com
CC: wine-bugs(a)winehq.org
Created an attachment (id=31069)
--> (http://bugs.winehq.org/attachment.cgi?id=31069)
Character close view
This strange effect persists with any possible configurations (including those
in gfxoptions debug menu). It's followed with dozens of
fixme:d3d_surface:IWineD3DBaseSurfaceImpl_Blt Filters not supported in software
blit
messages, but I'm not sure, that it's directly related to the filters missing,
but I've tried to comment-out render-target check, so direct opengl
implementation of blit called always - it seems to gone, but this was unstable
and in any following runs I've got completelly black scene, including mini-map
(effects, selections, magic spells and soon - all in place, but all surfaces
are blackened).
I'm attaching screenshot of player's character, close view and far view. You
may see some dotted patterns on characters clack, or on terrain around him.
This effect hard to get screenshoted as it's mostly visible while moving
camera, mouse, character and soon.
It's might be related to other bug, that affects only indoor areas, that I'll
post soon also.
Tested on:
wine-1.3.3
kernel 2.6.35 with 'nopat' kernel option
ati-drivers (fglrx): 10.9, ATI Mobility Radeon HD4520
Wine direct3d configs:
OffscreenRenderingMode=fbo
VideoMemorySize=512
UseGLSL=enabled
Overrides and installed packages:
vcrun2005 and d3dx9 from winetricks (without this game just can't start due to
unimplemented features).
devenum.dll and dxdiagn.dll (without this, game can't find any video device and
refuses to run).
--
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=31121
Bug #: 31121
Summary: Wrong FSF adress in wine-mono licenses
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andreas.bierfert(a)lowlatency.de
Classification: Unclassified
While packaging wine-mono for fedora, rpmlint pointed out that the following
files carry a wrong FSF address:
mono/COPYING.LIB
mono/mcs/LICENSE.GPL
mono/mcs/LICENSE.LGPL
More information on the subject:
http://fedoraproject.org/wiki/Common_Rpmlint_issues#incorrect-fsf-address
--
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=28839
Bug #: 28839
Summary: Modal window + a opened menu => mouse unusable
Product: Wine
Version: 1.3.26
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pixecs(a)yahoo.com
Classification: Unclassified
Created attachment 37034
--> http://bugs.winehq.org/attachment.cgi?id=37034
illustrative picture
os: OpenSUSE 11.4 x86_64
kernel: 2.6.37.6-0.5-desktop
desktop: kde4
wine version: wine-1.3.26-168-g6ee95c7 compiled with
--prefix=/usr --x-libraries=/usr/X11R6/lib --x-includes=/usr/include/X11/
--with-x
wine configured in windowed mode (1024x768)
application: winrar v4.01
WinRAR trial period has expired and in these conditions a modal window "Please
purcase WinRAR license" appears in 2-3 seconds after opening the application.
The problem arises when:
1) i launch the program
2) immediately open a menu (from winrar like File, Options)
3) the license expiration window appear
4) i still have the menu opened
The problem is that after the appearance of modal window i can not use the
mouse on desktop (items or windows from the desktop no longer reacts to mouse)
but the keyboard still works (for example, i can press Alt + Tab).
After pressing Alt + Tab and another window receives the focus the mouse can be
used again.
--
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=27473
Summary: Wine Changing Window Decorations in Conflict with
Window Managers
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: swt(a)techie.net
When running an application under Wine, if the window manager removes the
window decorations, Wine restores them. For example, under Unity, when an
application is maximized, the WM removes the window decorations as the title
bar is merged with the Unity panel. When this happens with a Wine application,
Unity removes the decorations, but Wine puts them back (sometimes only
partially, leading to a confused experience where the decorations exist but are
invisible).
--
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.