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.
http://bugs.winehq.org/show_bug.cgi?id=30256
Bug #: 30256
Summary: Ancients of Ooga: very slow rendering in mid game
Product: Wine
Version: 1.3.22
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
CC: matteo.mystral(a)gmail.com
Classification: Unclassified
Regression SHA1: 002674e49d3343d2ad4670081276e38af867eefe
Created attachment 39520
--> http://bugs.winehq.org/attachment.cgi?id=39520
terminal output
Ancients of Ooga is an indie platformer, developed by NinjaBee.
The demo version of the game is Steam-only:
http://store.steampowered.com/app/91810/
The problem: performance is okay in the menus and during the intro video. As
soon as the video ends and the game is loaded, framerate drops dramatically.
While in the menus I get 50 fps, in mid-game I get 1-2 fps or less. This makes
the game unplayable.
The problem appeared in Wine-1.3.22 and is still present in 1.5.0. Actually,
Wine-1.3.21 is the one and only version being capable of running the game
normally. All previous versions fail to start the game correctly, and all later
versions have the reported performance issue.
When I start a new game I get 30 fps with 1.3.21, and 1-2 fps with 1.3.22.
The result of the regression test:
002674e49d3343d2ad4670081276e38af867eefe is the first bad commit
commit 002674e49d3343d2ad4670081276e38af867eefe
Author: Matteo Bruni <mbruni(a)codeweavers.com>
Date: Mon Jun 6 17:44:43 2011 +0200
wined3d: Fix glDrawBuffers() optimization.
:040000 040000 afbbbb65e869d58ae00b56c627228bd6e9d2d1bb
71478cb542317c0b2e3c1dc2b8155a6ff4dcd44a M dlls
The problem can be reproduced with the Steam demo version (the game needs
native d3dx9_36.dll). Please let me know if you need a log with debug channels
enabled.
Fedora 16
Nvidia 250 / driver 290.10
X.Org X Server 1.11.4
--
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=30924
Bug #: 30924
Summary: Uncapture Mouse in Fullscreen Windows
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: songandsilence27(a)gmail.com
Classification: Unclassified
In winecfg, there is an option, under the Graphics tab to automatically capture
the mouse in fullscreen windows.
When using the emulated virtual desktop, certain programs freezing, crashing,
etc., can cause the mouse to stay within the emulated virtual desktop. Killing
wine or wineserver causes the mouse to stay within the confines of the virtual
desktop, rendering the (actual, X11) desktop useless. The Virtual desktop
window will grey out, becoming unresponsive to any and all input meant to close
it, including keystrokes such as ALT+F4 and clicking the "close" button.
Opening a X11-managed window (e.g., a terminal emulator) inside of the window
area will allow keyboard input, and depending on placement, can free the mouse
from the virtual desktop window, however, mouse clicks are not functioning in
other X11 windows, panels, etc.
Killing and restarting the X server via CTRL+ALT+Bksp or switching to a second
Virtual Console (e.g., tty2) and issuing "pkill X; startx" will temporarily
solve the issue (unless the offending program is run and freezes/crashes
again).
There should be a key combination to release the mouse back to the X11 desktop
environment.
--
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=27706
Summary: [integration] Menu entries generated by wine when
installing apps are not compatible with Linux Mint
menu
Product: Wine
Version: 1.3.23
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine(a)rodrigosilva.com
The command wine generates for menu entries are like this (example):
env WINEPREFIX="/home/rodrigo/.wine" wine C:\\windows\\command\\start.exe /Unix
/home/sb/.wine/dosdevices/c:/users/sb/Start\ Menu/Programs/Microsoft\
Office/Microsoft\ Office\ Word\ 2007.lnk
For some reason they dont work in Linux Mint's main menu (bad parser in
mintmenu?). While this can be considered Mint's fault, its MUCH easier for wine
to solve this, but just double-quoting the last parameter (the path to .lnk
file) and removing escaping-backslashes from it:
So the abve example would turn into this:
env WINEPREFIX="/home/sb/.wine" wine C:\\windows\\command\\start.exe /Unix
"/home/sb/.wine/dosdevices/c:/users/sb/Start Menu/Programs/Microsoft
Office/Microsoft Office Word 2007.lnk"
Its an easy fix that wouldnt break anything for other distros, and would make
Mint work out-of-the-box, So I would be glad to see this "fixed"
References:
http://bugs.launchpad.net/mintmenu/+bug/714848http://forums.linuxmint.com/viewtopic.php?f=47&t=57536
--
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.