https://bugs.winehq.org/show_bug.cgi?id=57024
Bug ID: 57024
Summary: msiexec parses quotes in public properties differently
from Windows
Product: Wine
Version: 9.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: asger(a)tyilo.com
Distribution: ---
Created attachment 76873
--> https://bugs.winehq.org/attachment.cgi?id=76873
test.c
When installing an msi package using msiexec on Windows the following
invocation (using cmd) will result in `MY_PROPERTY` being set to `foo"bar`:
```
msiexec /i my_property.msi /qn MY_PROPERTY="foo""bar"
```
When running it through wine the property is set to `foobar` (without the
double quote).
To test this I have created a test msi, called `my_property.msi`, that when
installed will create the file `my_property.txt` next to `my_property.msi` with
the contents of the `MY_PROPERTY` property. (After that the installation will
fail.)
Furthermore, to ensure that this is not due to shell handling of the arguments,
I have created a c program which invokes msiexec (attached as test.c).
Compiling this test program and running it on Windows results in:
```
C:\test>a.exe C:\\test\\my_property.msi
C:\test>type my_property.txt
foo"bar
```
Doing the same on Linux results in:
```
/tmp/test $ rm -rf ~/.wine
/tmp/test $ export WINEARCH=win64
/tmp/test $ winecfg /v win10
/tmp/test $ wine a.exe Z:\\tmp\\test\\my_property.msi
/tmp/test $ cat my_property.txt
foobar
```
--
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=57126
Bug ID: 57126
Summary: CEF sample application crashes in 64-bit wineprefix
Product: Wine
Version: 9.16
Hardware: x86-64
URL: https://cef-builds.spotifycdn.com/cef_binary_127.3.5%2
Bg114ea2a%2Bchromium-127.0.6533.120_windows32_client.t
ar.bz2
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 77021
--> https://bugs.winehq.org/attachment.cgi?id=77021
Backtrace
Both the 32- and 64-bit versions of the Chromium Embedded Framework sample
application crash in a 64-bit wineprefix, unless using the new WOW64 build.
--
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=18288
Summary: Quicktime 3 creates unusual menus / string value error
Product: Wine
Version: 1.1.20
Platform: PC
URL: http://www.oldversion.com/download/quicktime302.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Created an attachment (id=20819)
--> (http://bugs.winehq.org/attachment.cgi?id=20819)
Wine 1.1.20 +menubuilder
The Quicktime 3.0.2 installer reports an error when attempting to create
program groups and icons:
"String variable is not large enough for string.
Check the string declarations.
Error 401."
The installer then creates an unusual directory structure:
ls -aR /home/test/.local/share/applications/wine/Programs
/home/test/.local/share/applications/wine/Programs:
. .. QuickTime QuickTime 3.0
/home/test/.local/share/applications/wine/Programs/QuickTime:
. .. MoviePlayer.desktop PictureViewer.desktop ReadMe.desktop UnInstall
QuickTime 3.0.desktop
/home/test/.local/share/applications/wine/Programs/QuickTime 3.0:
. .. .desktop
Setup completes successfully.
--
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=52685
Bug ID: 52685
Summary: Crash with openkiosk
OpenKiosk91.3.0-2021-10-28-i686.msi
Product: Wine
Version: 7.0
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: philippereix.csc(a)gmail.com
Distribution: ---
Created attachment 72023
--> https://bugs.winehq.org/attachment.cgi?id=72023
Backtrace of the database application
I installed kubuntu 18.04 (32 bit) on an old pentium 4 3ghz (i386 architecture)
with 4gb ram and the only installable version
OpenKiosk91.3.0-2021-10-28-i686.msi with
Wine 7.0 installed. OpenKiosk is a cross platform kiosk web browser based on
Mozilla Firefox that can be easily installed and used to secure a computer for
use as a public terminal. This is a complete solution for any kiosk
installation. This software is released under the MPL "as is" with no warranty
or support. (https://openkiosk.mozdevgroup.com/)
The OpenKiosk command is: env WINEPREFIX="/home/acsm-borne-pres/.wine" wine
C:\\Program\ Files\\OpenKiosk\\OpenKiosk.exe
and the working folder is: /home/acsm-borne-pres/.wine/dosdevices/c:/Program
Files/OpenKiosk/
OpenKiosk launches well but after 1 to 2 minutes I have this error message with
the detail attached
Can you help me please?
Thanks very much
Philip
--
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=57149
Bug ID: 57149
Summary: Inconsistent keyboard keys handling between
winewayland and winex11
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
I noticed that when I remap keys in KDE (such as "Left Alt is swapped with Left
Win" in keyboard settings), it's not working with winewayland but works as
expected with winex11 (in XWayland mode).
In particular, in Cyberpunk 2077 when I try to bind some action to a key it
detects "Super_L" (aka Win key) as Alt when XWayland / winex11 are used, but
with winewayland it doesn't and detects actual Alt as Alt ignoring KDE's
override.
Not sure if it's something incomplete on KDE's side or winewayland is doing
something strange?
It happens with KDE Plasma 6.1.4.
--
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=32680
Bug #: 32680
Summary: cmd.exe Add support for CMDEXTVERSION, CMDCMDLINE,
HIGHESTNUMANODENUMBER
Product: Wine
Version: 1.5.21
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: cmd
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: us(a)edmeades.me.uk
Classification: Unclassified
%CMDEXTVERSION%
%CMDCMDLINE%
%HIGHESTNUMANODENUMBER%
--
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=57118
Bug ID: 57118
Summary: CEF 32-bit sample application fails in WOW64 mode
Product: Wine
Version: 9.16
Hardware: x86-64
URL: https://cef-builds.spotifycdn.com/cef_binary_127.3.5%2
Bg114ea2a%2Bchromium-127.0.6533.120_windows32_client.t
ar.bz2
OS: Linux
Status: NEW
Keywords: download, source, wow64
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 77010
--> https://bugs.winehq.org/attachment.cgi?id=77010
Wine 9.16 console output
The 32-bit Chromium Embedded Framework sample application immediately fails on
load when Wine is built with --enable-archs=x86_64,i386. The window loads but
the application refuses to do anything further, reporting error
SBOX_FATAL_CLOSEHANDLES. I can't figure out how to disable the sandbox feature
with this sample, or if it is even possible to do so.
No further testing is possible, either having no effect or just showing this
error again.
The 64-bit version does not have 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=57136
Fabian Maurer <dark.shadow4(a)web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dark.shadow4(a)web.de
--
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=57077
Bug ID: 57077
Summary: Micrografx Window Draw 4.0a crashes when backspacing
while editing freeform text object
Product: Wine
Version: 8.10
Hardware: x86-64
URL: https://winworldpc.com/product/micrografx-draw/40
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: arethusa26(a)gmail.com
CC: jacek(a)codeweavers.com
Regression SHA1: 0492108ae8367dfe69d15879b1482876579e7c03
Distribution: ---
Created attachment 76950
--> https://bugs.winehq.org/attachment.cgi?id=76950
Micrografx Window Draw 4.0a winedbg backtrace
With the latest master, Micrografx Window Draw 4.0a crashes when performing the
following steps:
1. Launch the application and create a new blank drawing.
2. Select the text tool (capital A icon) from the left toolbar and click
somewhere in the drawing area to create a new freeform text object.
3. Type some letters in the text object and hit backspace.
The crash does not occur in wine-8.0. Regression testing identified the
following breaking commit:
0492108ae8367dfe69d15879b1482876579e7c03 is the first bad commit
commit 0492108ae8367dfe69d15879b1482876579e7c03
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Mon Aug 1 21:30:30 2022 +0200
win32u: Use syscall interface for all ntuser functions.
--
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=57106
Bug ID: 57106
Summary: configure: prevent using --enable-win64 and
--enable-archs=x86_64,i386 together
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source, wow64
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
I noticed this in bug 57084 (the same user has reported doing the same in bug
57103 and bug 57104).
Testing locally, if both are passed, regardless of order, then
--enable-archs=x86_64,i386 is what takes effect.
However since these aren't meant to be used together, configure should probably
warn/error out if both are passed.
--
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.