https://bugs.winehq.org/show_bug.cgi?id=43337
Bug ID: 43337
Summary: Conditional command with parentheses not working.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: distjubo(a)gmail.com
Distribution: ---
If a conditional command contains parentheses, it fails to execute properly.
Example 1:
Command:
echo C:\Program Files (x86)\
Output:
C:\Program Files (x86)\
Example 2:
Command:
if ""=="" echo C:\Program Files (x86)\
Example 2 fails to execute. On Windows, the output of Example 1 and Example 2
are identical, but wine complains about not having found the command "x86".
--
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=44063
Bug ID: 44063
Summary: Parentheses cause cmd.exe failing to recognize '2>&1'
Product: Wine
Version: 2.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhasse(a)gmail.com
Distribution: ---
On Windows
cmd.exe /C "(echo foo) 2>&1"
works (only outputs "foo"), while on wine it results in:
foo
Can't recognize '2' as an internal or external command, or batch script.
and a non-zero exit code. Removing the parenthesis would work:
wine cmd.exe /C "echo foo 2>&1"
I need them though, since I want to do stuff like this:
wine cmd.exe /C "(echo foo && echo bar) 2>&1"
Maybe related: https://bugs.winehq.org/show_bug.cgi?id=43337
--
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=21806
Summary: Star Wars Empire at War: Demo crashes during battles
Product: Wine
Version: 1.1.39
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gaming4jc2(a)yahoo.com
Created an attachment (id=26385)
--> (http://bugs.winehq.org/attachment.cgi?id=26385)
Tutorial 1 debugs, pagefaults, backtraces...
This seems to affect the game any time you are going into battle. At the
loading screen the game will issue a exception.
You have two choices, retry or cancel. I've provided a backtrace log that
results from each selection - as well as the game's built debugger log.
For anyone wishing to confirm, just try Tutorial 1. It will crash in under
2mins. The other tutorials may crash too, but not nearly as often since there's
not many battles to load. I was using the Demo CD I got in a promo.
--
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=42698
Bug ID: 42698
Summary: FL Studio 12.4 setup does not show cursor
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: seanaubin(a)gmail.com
Distribution: ---
Running Linux Kernel 4.4.0 on Linux Mint 18 and installing FL Studio 12.4, the
cursor does not display during the install.
--
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=46734
Bug ID: 46734
Summary: EditPad Pro 7: Cannot read/capture host (Linux)
application's stdout/stderr to display in its message
panel
Product: Wine
Version: 2.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: clay_dakota(a)yahoo.com
Distribution: ---
Created attachment 63726
--> https://bugs.winehq.org/attachment.cgi?id=63726
Python script to write "Hello World" to stdout.
Distribution: Linux Mint 17.3 ; 32-bit ; Trusty ; MATE Desktop
AppDB App: EditPad Pro 7
AppDB Entry: #8392
Wine Ver w/o Bug: 2.18 (devel) & 2.04 (stable)
Wine Ver w/ Bug: 2.19 (devel) & 3.04 (stable) & 4.0 (stable)
Steps to reproduce:
* Download EditPad Pro free trial version 7.6.5 and install
- URL: http://download.jgsoft.com/editpad/SetupEditPadProDemo.exe
* Install Wine 2.18 (devel)
* Run EditPad Pro (EPP) from Wine
- Executable: EditPadPro7.exe
* From the EPP menu, go to Tools -> Configure Tools
* Import the EPP Tool configuration file
- Attachment: RunWithPython.ini
* Open the Python source file
- Attachment: hello.py
* From the EPP menu, go to Tools -> Run w/ Python
* Will see the Python script's output in EPP's message panel as expected
- See attachment: EPP_Wine2.18_WithoutBug.png
* See Wine 2.18's terminal output file to see that the output did not go to
the terminal as expected
- Attachment: Con_Wine2.18_WithoutBug.out
* Install Wine 2.19 (devel)
* Run EditPad Pro (EPP) from Wine
- Executable: EditPadPro7.exe
* Open the Python source file
- Attachment: hello.py
* From the EPP menu, go to Tools -> Run w/ Python
* Will not see the Python script's output in EPP's message panel
- See attachment: EPP_Wine2.19_WithBug.png
* See Wine 2.19's terminal output file to see that the output went to the
terminal instead of EPP's message panel
- Attachment: Con_Wine2.19_WithBug.out
Note: This bug *may* be related to bug 23596. However, bug 23596 is reported
against Wine version: 1.2-rc7.
--
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=44245
Bug ID: 44245
Summary: Gray screen on OnePlus 3 / 3T
Product: Wine
Version: 3.0-rc3
Hardware: arm
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sasha01945(a)gmail.com
Created attachment 60040
--> https://bugs.winehq.org/attachment.cgi?id=60040
Gray screen on OnePlus 3T
After running Win3.0 RC3, first unpacking, then writes "Setting up windows
environment".
After that, the gray screen (as in the screenshot).
Android version: 8.0.0
OhygenOS version: OP3T_0.2_Open_19
--
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=46419
Bug ID: 46419
Summary: Multiple installers draw bottom text not as 3d
disabled text
Product: Wine
Version: 4.0-rc3
Hardware: x86
OS: Linux
Status: NEW
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 63185
--> https://bugs.winehq.org/attachment.cgi?id=63185
Screenshot wine
This is a very minor and subtle bug, on windows only really visible when the
old classic theme is used.
In all NSIS installers, the bottom line text should be rendered as 3d disabled
text, see screenshots.
As a sidenote, wine can draw 3d disabled text, it's just that for some reason
it is not applied here.
--
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=42895
Bug ID: 42895
Summary: HeroesofMight and Magic II: Gold - possible problems
Product: Wine
Version: 2.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: trufanovan(a)gmail.com
Distribution: ---
Created attachment 58029
--> https://bugs.winehq.org/attachment.cgi?id=58029
Save game
Hi,
As far as i can see HoMM2 has platinum support. I have a big doubts in that.
Just tried 2 game distributives:
1. Game in russian freezes on start screen. No menu labels highlighted when
user moves a mouse over it.
2. Same build but in english - freezes on campaign screen when user may choose
award. Can't start the game.
3. Another distributive (english) - after you win any campaign level the screen
is black and you must gues whee to click to start another level. Or press
Enter.
Attached is the save game at end of first level to reproduce no 3.
NVIDIA 378.13
GeForce GT 635M
Kubuntu 17.04
wine-stable 2.0.1~zesty
--
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=50288
Bug ID: 50288
Summary: Warcraft 3: Crashing on Wayland (mutter/gnome)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: thesleort(a)gmail.com
Distribution: ---
Created attachment 68856
--> https://bugs.winehq.org/attachment.cgi?id=68856
Wayland cinematics bug
I just installed Warcraft 3 (cd version) and I am mostly unable to play
Warcraft 3 on Wayland, but not in X11.
There are two errors. Both only occurs in Wayland and are fixable by playing
the game in X11 first. Both bugs happens on all my laptops (Ubuntu 20.10) and
my Vega 56 machine (Ubuntu 20.04 LTS)
Error 1:
The game will not start, since it plays a intro-video in the beginning the
first time it is launched. This can be circumvented by launching the game in
X11 first and then launching it in Wayland afterwards, since it is not shown in
launches afterwards.
This error occurs every time a video/cinematic is played in the game, so it
also happens when starting the Human campaign. Again the fix is to play in X11
first, since it follows the same "mechanic" as the intro video when launching
the game.
Error 2:
This error appears to happen when the game is forcefully shut down and then
trying to launch it again. Not entirely sure why, but in the logs it appears as
if it is not able to initialize some output. It also will not "reset" itself by
doing wineserver -k. Instead I have to log out of the current session and then
I can launch the game again.
---
I have installed gstreamer1.0-plugins-*:386 packages, which are required to
reach the cinematic bug. Otherwise wine will complain that gstreamer is not
installed. When i386 packages of gstreamer are installed it reaches the
aforementioned cinematic bug.
Also X11 is not able to playback the cinematics in-game, however, in contrast
to Wayland it recovers and I am able to advance further in the game.
---
sha1sum Warcraft\ III.exe
a4c13b9a075548347a4c63d0a292b1a500ba34b7 Warcraft III.exe
---
My current computer:
Wine version: wine-staging 6.0-rc1 (from winehq repos)
Ubuntu 20.10
CPU: Intel i5-6200U (4) @ 2.800GHz
GPU: Intel Skylake GT2 [HD Graphics]
$ glxinfo | grep OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 520 (SKL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.2.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.2.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
--
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=42270
Bug ID: 42270
Summary: Settlers 4 Gold - Hardware Rendering mode not working
Product: Wine
Version: 2.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bronsonmathews(a)gmail.com
Distribution: ---
Created attachment 56975
--> https://bugs.winehq.org/attachment.cgi?id=56975
cmd log
The game runs ok in software mode. So this is a pretty low priority bug.
Settlers 4 Gold (Gog version) - changing the settings landscape engine, and
object engine from software to hardware does not work.
Attached command line output...
--
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.