https://bugs.winehq.org/show_bug.cgi?id=40773
Bug ID: 40773
Summary: Strider crashes on launch
Product: Wine
Version: 1.9.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: strider(a)strycore.com
Distribution: ---
Created attachment 54672
--> https://bugs.winehq.org/attachment.cgi?id=54672
Backtrace produced when running with 1.9.12
I have been testing this game for the past few months on every Wine release to
test progress made on the DirectX11 implementation. Now that the API is
starting to be more complete and some DirectX11 games now work, I believe this
is a good time to start tracking this issue.
--
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=43108
Bug ID: 43108
Summary: Strider displays a black screen on launch
Product: Wine
Version: 2.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: strider(a)strycore.com
Distribution: ---
Created attachment 58302
--> https://bugs.winehq.org/attachment.cgi?id=58302
Output with WINEDEBUG=+tid,+d3d11,+d3d
When opening the game on Steam, the game displays a black screen. the
background music can be heard and the game menu responds to key presses.
Judging from the debugging output, it seems that a lot of texture/color formats
are still missing.
--
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=8692
--- Comment #20 from winetest(a)luukku.com ---
(In reply to winetest from comment #19)
> Still valid wine 2.5.
I think this is actually fixed in wine-staging. Could it be?
I am not native german speaker, but after installing the software I picked
Eigenschaften and it shows in english properties.
The size of directories seems to be always (unknown), but I can't see this
issue with wine-staging 2.9.
--
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=40575
Bug ID: 40575
Summary: vconnect-Stand fail to run with cadencii
Product: Wine-staging
Version: 1.9.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: n296869(a)rtrtr.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 54414
--> https://bugs.winehq.org/attachment.cgi?id=54414
vconnect-STAND fatal error backtrace in .txt format
vconnect-STAND.exe is a synthesizer engine of cadencii program, fail to work
with cadencii.
--
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=43085
Bug ID: 43085
Summary: TIM message manager window unresponsive partly
Product: Wine
Version: 2.8
Hardware: x86
URL: http://dldir1.qq.com/qqfile/qq/TIM1.1.0/20837/TIM1.1.0
.exe
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lilydjwg(a)gmail.com
Distribution: ---
Created attachment 58267
--> https://bugs.winehq.org/attachment.cgi?id=58267
The problematic window
This is another window-related issue with TIM, similar to the one in bug 43009.
TIM is a cleaner version of QQ, successor of QQ Lite.
download and install it:
http://dldir1.qq.com/qqfile/qq/TIM1.1.0/20837/TIM1.1.0.exe
ecb6934f7cea33b1458308495fd965a274c6ba2a TIM1.1.0.exe
winetricks riched20 so you can input your QQ number.
login in, then click "消息记录" near the bottom-right corner. The window will
expand to the right, showing history messages. Then click again to unexpand it.
Now, the top bar and the left buddy list will become unresponsive. The top bar
even doesn't update itself. A screenshot by scrot shows these unresponsive part
as black.
Minimizing then restoring won't help. However, cover the window with another
window then it's back to normal.
My window manager is Awesome 3.4.
Tested with wine 2.8, wine-staging 2.8.
--
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=43103
Bug ID: 43103
Summary: unixfs unable to find file when wine run in a network
namespace
Product: Wine
Version: 2.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: lucianposton(a)gmail.com
Distribution: ---
If I run wine within a network namespace, wine is unable to find a file,
exiting with an error, wine: cannot find L"unix\\home\\user\\GameDir\\game.exe"
To repro the bug, the prefix must be setup such that:
1) "$WINEPREFIX/drive_c/Program Files/GameDir" is a symlink to a directory in
$HOME, outside of the prefix but on the same partition, and
2) the prefix's registry has been modified with the regedit described at
https://github.com/wine-mirror/wine/blob/252051cb1b3f0fc4aade128370fb3e38d9…
. This appears to cause the following behavior to change in wine:
https://github.com/wine-mirror/wine/blob/252051cb1b3f0fc4aade128370fb3e38d9…
If I start wine using
cd "$WINEPREFIX/drive_c/Program Files/GameDir" ; wine game.exe
it behaves fine. wine is able to find game.exe.
However, if I start wine within a namespace,
cd "$WINEPREFIX/drive_c/Program Files/GameDir" ; ip netns exec
MyNetworkNamespace wine game.exe
wine exits with the error:
wine: cannot find L"unix\\home\\user\\GameDir\\game.exe"
I expect both to succeed (or both fail, if that's the expect behavior when the
regedit in #2 is performed).
*Ancillary notes on setting up a network namespace*
I setup the network namespace using macvlan, which requires your kernel to have
CONFIG_MACVLAN (if it is compiled as a module, load it). Then you can create a
network namespace and a virtual network interface within the namespace as
follows:
REAL_IFACE=eth0 # set this to your real network interface from ifconfig
NETNS=MyNetworkNamespace # set this to whatever you want to name your namespace
NETNS_IFACE=vlaneth0 # set this to whatever you want to name your new virtual
interface inside the namespace
ip netns add "${NETNS}"
ip link add link "${REAL_IFACE}" name "${NETNS_IFACE}" type macvlan
ip link set "${NETNS_IFACE}" netns "${NETNS}"
ip netns exec "${NETNS}" ip link set "${NETNS_IFACE}" up
# Now give the new interface an ip. I use dhcpcd, but you can use your favorite
dhcp client (or set the ip directly)
ip netns exec "${NETNS}" dhcpcd "${NETNS_IFACE}"
# The interface should now have an ip, which we can verify by running ifconfig
inside the namespace
ip netns exec "${NETNS}" ifconfig
ip netns exec "${NETNS}" wine game.exe
# Note you can use sudo -u to avoid running wine as root in the above command.
--
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=31776
Bug #: 31776
Summary: Get WineTestBot working with libvirt
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
WineTestBot currently controls VMware VMs using VIX. However we need to switch
away from VMware. So the goal is to replace it with a combination of QEmu/KVM
and libvirt to provide a layer of abstraction.
See:
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.
https://bugs.winehq.org/show_bug.cgi?id=43090
Bug ID: 43090
Summary: Myst crashes when linking to Myst in intro
Product: Wine
Version: 2.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: anowlcalledjosh(a)gmail.com
Distribution: ---
Created attachment 58273
--> https://bugs.winehq.org/attachment.cgi?id=58273
Terminal output + backtrace after clicking linking panel
Myst crashes after clicking the linking panel in the intro.
To reproduce:
- Launch Myst
- Skip the intro videos (press space or click inside the window) to work around
bug 43087
- Click on the linking panel in the Myst book, and wait for the linking sound
to play once
Clicking either "Show Details" or "Close" in Wine's popup usually causes a
hang, the only way to exit Myst at this point is ctrl-C.
Interestingly, running Myst on one core (with "taskset -c 0 wine MYST.EXE")
then skipping the intro videos quickly enough* seems to inconsistently avoid
this crash, allowing the player to link to Myst (although the game usually
crashes soon after).
*if the Brøderbund logo is visible or the sound effect starts playing, you were
probably too slow.
Ubuntu 16.04.2 x86_64, 32-bit Windows 95 wineprefix.
--
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=43087
Bug ID: 43087
Summary: Myst hangs when Myst linking book is clicked in intro
Product: Wine
Version: 2.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: anowlcalledjosh(a)gmail.com
Distribution: ---
Created attachment 58271
--> https://bugs.winehq.org/attachment.cgi?id=58271
Terminal output
Clicking the Myst linking book in the intro (when it's sitting on the floor)
causes Myst to hang forever. The audio continues to play, although the cursor
disappears when it's inside the Myst window.
Trying to close the window doesn't close Myst; only ctrl-C in the terminal it
was launched from, or waiting for Wine to pop up the "Waiting for Program"
window, works.
Ubuntu 16.04.2 x86_64, 32-bit wineprefix in Windows 95 mode.
--
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.