https://bugs.winehq.org/show_bug.cgi?id=39436
Bug ID: 39436
Summary: Gta Vice City - the black screen while playing clip at
the game start
Product: Wine
Version: 1.7.52
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: geeronzero(a)gmail.com
Distribution: ---
Gta Vice City - the black screen while playing clip at the game start. The is
music in it, but no image.
--
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=19816
Summary: Enhancement request: MSVBVM60
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bammzilla(a)astronomy.com.ph
I would like to request that Wine have its own built-in version of MSVBVM60. I
don't know how difficult it would be, but since WinXP has it by default I would
love Wine to have it as well.
--
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=31786
Bug #: 31786
Summary: Run the tests on real hardware
Product: Wine-Testbot
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fgouget(a)codeweavers.com
Classification: Unclassified
It would be very useful to run some tests on real hardware.
* This is the case for all the 3D graphics tests. For these we would even want
to run them on both AMD and NVidia graphics cards(*). Currently they are
essentially ignored by WineTestBot because the virtual graphic cards don't
provide meaningful 3D support.
* It could somewhat be useful for sound tests too, mostly to avoid timing
issues, but also to ensure the results we get are not tainted by bugs in the
emulated sound card. Also emulated sound cards typically don't support MIDI
emulation.
The problem is that it's very important to limit the test duration and to
restore the test environment to a clean state after each test, no matter what
happens, for two reasons:
* Because it's not uncommon for tests to have side effects and for them to
leave the test environment in an unusable state. Granted it happens much more
often with older Windows releases as they are more prone to crashes. However
graphics drivers also tend to be buggy and we would not want the tests to be
tainted by a previous run (though a reboot should take care of most issues).
* But also the Wine TestBot runs anything that gets posted by anonymous users
on wine-patches. That's ok as long as such code is properly confined and not
allowed to run for too long. That supposes thoroughly cleaning up the
environment after a test has run, including anything that could happen at boot
time.
Virtual machines provide a simple solution to both of these issues which is why
the TestBot relies on them heavily.
With QEmu it's possible to let the guest OS access some peripherals directly
via the 'passthrough' mode. This is normally done for network cards. If it
worked for graphics cards that would be a great solution but it's not clear
that it's feasible.
Another option would be to play tricks with Grub scripts: have it boot from a
clean Linux partition (or from the network?), restore the Windows partition
from a clean disk image, reboot into that partition, and back on the clean
partition with the next reboot. That still leaves the issue of forcing a reboot
in case of a freeze or malware taking control of Windows (use a remote
controlled power switch like in data centers?).
(*) We currently have two such machines ready for this:
http://www.winehq.org/pipermail/wine-devel/2012-February/094080.html
--
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=33912
Bug #: 33912
Summary: Remove All Wine Home Content - Button
Product: Wine
Version: 1.6-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: moceap(a)hotmail.com
Classification: Unclassified
This enhancement what I require that a button not remove only .wine folder in
home , also delete all installed-by-wine-application desktop integration files
Such as ::
$HOME/.local/share/mime/packages/wine*
$HOME/.local/share/applications/wine*
And others .
--
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.
https://bugs.winehq.org/show_bug.cgi?id=41668
Bug ID: 41668
Summary: wineboot mishandles user dir symlinks during update
Product: Wine
Version: 1.9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
In a standard wine prefix 'Desktop', 'My Documents', etc. are symlinks to
${HOME}.
As are their localized versions.
I consider the first a wrong choice and and make those normal dirs in the
prefix; as for the second, I turn those into symlinks to their English
counterparts.
Yet...
Upon 'wineboot' at each wine update, while the English dirs stay untouched, the
localized symlinks get reset into ${HOME} symlinks.
If it's WAD, it's a misfeature; otherwise, it's a bug.
--
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=10729
Summary: Clicking things in-game in LEGO Island causes game to
hang
Product: Wine
Version: 0.9.50.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: echidnaman(a)gmail.com
Created an attachment (id=9571)
--> (http://bugs.winehq.org/attachment.cgi?id=9571)
Console log
Once you get in-game in LEGO Island, clicking things will print a few fixme and
then hang indefinitely. A console log is attached, and notes where the fixmes
coinciding to the hang are.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42444
Bug ID: 42444
Summary: Dualshock 3 does not map correctly
Product: Wine
Version: 2.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: haakobja(a)gmail.com
Distribution: ---
Created attachment 57282
--> https://bugs.winehq.org/attachment.cgi?id=57282
DS3 events
Hi,
I've tried using a dualshock 3 controller with wine, but I'm unable to get the
analogous triggers to work. They seem to be mapped as buttons, not analogue
input.
If I use xboxdrv the triggers are mapped correctly, but then force feedback
does not work. Because of this, I think it would help if the wine-mapping was
correct.
I've earlier tried asking on the forum, but it does not seem like anyone know
how to map the controller correctly. I use the controller using events, not the
legacy joystick interface in Linux.
--
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=13616
Summary: Screenserver starts while playing with Joypads
Product: Wine
Version: 1.0-rc2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: trevi55(a)gmail.com
I don't exactly know if this is an issue related to GNOME or wine, but when I
play a game using a joystick - after few minutes - the gnome screensaver starts
so I've to move the mouse to continue...
Shouldn't wine block the screensaver launching if it is getting data from
/dev/input/js*?
--
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.
https://bugs.winehq.org/show_bug.cgi?id=42761
Bug ID: 42761
Summary: add option for full-screen window mode
Product: Wine
Version: 2.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bronsonmathews(a)gmail.com
Distribution: ---
It would be good to have both a fullscreen window mode.
IE the linux window is fullscreen without borders. And the game is scaled to
fit to the window. For playing older low resolution games this would be useful
when you need to switch to the desktop quickly.
And also to have the "Emulate a virtual desktop" mode to allow the game to
resize with that window. Again for the above reasons. Currently if you resize
this window, the game stays in a window within a window. It would be good to
have the game scale to the window size.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=43074
Bug ID: 43074
Summary: Cant run the game "Pathologic Classic HD" from steam
Product: Wine
Version: 2.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: inferrna(a)gmail.com
Distribution: ---
Created attachment 58257
--> https://bugs.winehq.org/attachment.cgi?id=58257
Terminal output
Game starts and main process Game.exe is present, but window not appears.
--
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.