https://bugs.winehq.org/show_bug.cgi?id=46676
Bug ID: 46676
Summary: Serial port enumeration (get device description) on
Mac OS/X 10.9, 10.13
Product: Wine
Version: 4.0
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)hinner.info
Created attachment 63628
--> https://bugs.winehq.org/attachment.cgi?id=63628
suspected problematic function
Tested on: Mac OS/X 10.9, 10.13
WineBottler (Wine 1.8) works fine; Wine 4.0 (from .pkg) does not work
Our application is trying to enumerate serial ports by using setupapi
functions. I have not checked where exactly is the problem as debugging on OS/X
is a bit difficult for me, however suspected function is attached (it's goal is
to get device description).
The affected apps are http://obdtester.com/ficom , http://obdtester.com/bimcom
, http://obdtester.com/fcom ;
I have tried to create symlink in dosdevices (required for WineBottler to get
it working), one OS/X 10.13 my link got deleted everytime I ran the app; on
OS/X 10.9 link persisted, but not possible to enumerate any serial port(s).
I can provide login for download by personal e-mail (not to be disclosed).
I have talked about this on wine mailing list a long time ago, it would be
super easy if Wine-enabled application can have a way to load system native .so
to talk directly to the host system, I have many examples of device drivers
that would be super easy to implement. FYI I have already written
"winegate.dll.so" which solves this real world problem, but it was rejected for
submission to Wine because of "Wine must be 100% transparent" ideology.
--
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=10051
Summary: Parallax SX Key IDE cannot detect serial port under WINE
Product: Wine
Version: 0.9.46.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-setupapi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ultimatedevr(a)yahoo.com
Created an attachment (id=8599)
--> (http://bugs.winehq.org/attachment.cgi?id=8599)
Result of running SXKey.exe in wine with the +setupapi debug flag.
I am trying to run the Parallax SX Key IDE through WINE, however the IDE does
not detect any of my serial ports. I have symlinked them to ~/.wine/dosdevices/
and added them to my registry, however the IDE still cannot detect my serial
ports.
I am currently running WINE v.0.9.46 (the same problem exists in the CVS
version as well).
(BTW, I have heard of others getting this to work, yet others who couldn't:
http://forums.parallax.com/forums/default.aspx?f=15&m=217429&g=221692)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=23326
Summary: Cannot change printer settings, Family Tree 7
Product: Wine
Version: 1.2-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jamesl(a)bestweb.net
Created an attachment (id=29072)
--> (http://bugs.winehq.org/attachment.cgi?id=29072)
FTW7 print dialogue, compare Wine to XP
Cannot select printer/change print settings with Family Tree Maker 7. Dialogue
box comes up, drop-down boxes are working, but radio buttons for switching
between "default printer" and an alternate printer are not selectable. Have
compared the print dialogue between Wine vs a native install under Windows XP
(SP3) and notice some text from the Windows install does not show up under
Wine.
Also tried the same thing with the "free" version of FTM2005se available at
http://past.familytreemaker.com/download/starter.aspx and found it's behavior
is the same. So I will describe steps from there, since it would be eaier for
someone to get that to test against.
STEPS TO RECREATE:
1: Set up wine profile with "WINEPREFIX=/home/jelabarre/wine-apps/ftw2005
winecfg"; set winver to "Windows XP", point the Documents directory under
Desktop Integration to my own Documents directory
2: install FTW2005 by running
"WINEPREFIX=/home/jelabaWINEPREFIX=/home/jelabarre/wine-apps/ftw2005 wine
./FamilyTreeMaker2005se.exe", accept all defaults.
3: open FTW 2005 from "Wine" menu entry on Gnome menu. Selected "Buy Later"
from popup window (does not affect outcome, as same print problem occurrs in a
regular retail version of FTM7)
4: create new file, or use existing file (same result either way)
5: select "File | Print Setup", then try to select radio button for either
"Default Printer" or "Specific Printer". Neither can be selected
6: try selecting a "specific printer" from drop-down box. Printer can be
selected, but radio buttons still not functional.
7: after selecting a printer other than the default (such as print-to-PDF) and
then try printing. Output will still go to the Linux default printer, no edits
of the print settings will take effect.
The "Family Archive Viewer v6.0" at
http://familytreemaker.genealogy.com/abtffiv.html and "Family Archive Viewer
v11.0" at http://www.genealogy.com/abtffiv.html are other variants that
exhibits this behavior.
Have attached sample screenshots of Wine vs WinXP versions of the print
dialogue.
--
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=50778
Bug ID: 50778
Summary: TortoiseMerge closes before showing a window
Product: Wine
Version: 6.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lexlexlex(a)gmail.com
Distribution: ---
Created attachment 69576
--> https://bugs.winehq.org/attachment.cgi?id=69576
Terminal log for TortoiseMerge startup and subsequent closing with wine
Steps to reproduce:
1. Install TortoiseSVN in a 64-bit wine prefix.
2. Try to run TortoiseMerge.exe with the wine prefix mentioned in step 1. For
example, run "wine TortoiseMerge.exe" from a terminal if the default wine
prefix was used.
Current behavior:
TortoiseMerge closes before showing a window. No TortoiseMerge window appears.
Expected behavior:
TortoiseMerge is expected to start, allowing the user to compare and merge
files in a windowed GUI.
Additional information:
A download for the current version of the TortoiseSVN installer as of this
report is at
https://osdn.net/projects/tortoisesvn/storage/1.14.1/Application/TortoiseSV…
A log showing terminal output when trying to run "wine TortoiseMerge.exe" is
attached.
Opinion:
This is one of 2 bugs preventing using TortoiseSVN fully in wine. The other is
50756. If these 2 bugs are fixed, TortoiseSVN could be used fully, easing the
transition of users whose jobs rely on SVN to Linux. Currently some companies
still use SVN and I've tried all the free SVN clients for Linux, and none of
them come close to the level of convenience and intuitiveness that TortoiseSVN
provides. I have nemo actions ready to enable full usage in of TortoiseSVN in
Linux if these 2 bugs are fixed. This would help me personally tremendously,
as digging through old revisions in alternate SVN branches is part of my job
and extremely difficult with any SVN client other than TortoiseSVN using
TortoiseMerge. Thanks for reading this.
--
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=51212
Bug ID: 51212
Summary: i want to install itunes, it installed through wine
but giving some error while to launch the program
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: robinssgraphics(a)gmail.com
Distribution: ---
Created attachment 70086
--> https://bugs.winehq.org/attachment.cgi?id=70086
i want to install itunes, it installed through wine but giving some error while
to launch the program
i want to install itunes, it installed through wine but giving some error while
to launch the program
--
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=53850
Bug ID: 53850
Summary: Mery, TeraPad : When using Japanese input method (IM),
undetermined strings are not displayed (regression)
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: su_zu_me(a)hotmail.com
Distribution: ---
Created attachment 73380
--> https://bugs.winehq.org/attachment.cgi?id=73380
input after "そうか" ("souka"), but not displayed
Mery and TeraPad are text editors.
When using input method (IM) to input Japanese characters, undetermined strings
are not displayed.
Candidates are displayed.
Conversions are done successfully.
It occurs with Wine 7.13 or later.
Undetermined strings are displayed inline with Wine 7.12 or earlier, after
several conversion after starting the application.
note:
Right after starting the application, undetermined string is not displayed
with all tested version of Wine, but it should be another bug.
Application:
Mery (x86) Version 2.6.7
Download site:
https://forest.watch.impress.co.jp/library/software/mery/
SHA1:
edef7350aeed6bab083612e2d316607561f5f31c MerySetup-2.6.7.exe
tested Wine version:
6.0.3 (Ubuntu 6.0.3~repack-1)
7.11
7.12
7.13
7.15
7.19
Application:
TeraPad Version 1.09
Download site:
-
SHA1:
3ff8f3741ce82dcea54a385cea484b861007c260 tpad109.zip
tested Wine version:
6.0.3 (Ubuntu 6.0.3~repack-1)
7.11
7.12
7.13
7.15
7.19
Application:
TeraPad Version 1.10
Download site:
https://tera-net.com/library/tpad.html
SHA1:
ae28027af722c3ea7f6431d04c65582d16c60832 tpad110.exe
tested Wine version:
7.12
7.19
terminal output: N/A
OS:
Ubuntu 22.04.1 LTS (amd64)
Display server:
Wayland
Input Method Framework:
IBus
Input Method Engine:
Mozc
installed Wine:
winehq-devel
--
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=53247
Bug ID: 53247
Summary: user32:sysparams - test_dpi_context() fails on Windows
10 1909+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:sysparams - test_dpi_context() fails on Windows 10 1909+:
sysparams.c:3813: Test failed: got 0
sysparams.c:3814: Test failed: wrong value -1
https://test.winehq.org/data/patterns.html#user32:sysparams
These traces could include a bit more information rather than leaving most of
it to the source line number.
--
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=54015
Bug ID: 54015
Summary: Accessing shared memory from Linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: berarma(a)hotmail.com
Distribution: ---
Some Windows games and applications share some internals through shared memory
with external tools. Shared memory is preferred over sockets because it adds no
overhead with no latency.
It's mostly used in driving and flying simulators to provide visual overlays,
data on additional displays, telemetry, rig movement, etc. from external tools.
There's also scientific apps using it for similar purposes or general
inter-process communication.
It's common to use tagged shared memory blocks that external tools can then
access using the already known tag.
Here's an example from a Python application for rFactor 2:
self._rf2_tele = mmap.mmap(0, ctypes.sizeof(rF2Telemetry),
f"$rFactor2SMMP_Telemetry${input_pid}")
self._rf2_scor = mmap.mmap(0, ctypes.sizeof(rF2Scoring),
f"$rFactor2SMMP_Scoring${input_pid}")
self._rf2_ext = mmap.mmap(0, ctypes.sizeof(rF2Extended),
f"$rFactor2SMMP_Extended${input_pid}")
self._rf2_ffb = mmap.mmap(0, ctypes.sizeof(rF2ForceFeedback),
"$rFactor2SMMP_ForceFeedback$")
Allowing these shared memory blocks to be accessed from Linux would allow us to
port some of these tools or even implement or own.
Then these tools could access resources or hardware that isn't available from
inside the Wine prefix. Some of these tools also fail to run on Wine.
Since I guess Wine is already using Linux shared memory mechanism to implement
Windows shared memory, the blocks are already available at /dev/shm but they
use generic names that can't be associated to the tag used on Windows.
Having these shared memory blocks created in the prefix directory with a name
containing the tag used on creation would allow us to use it from our native
applications. Or any other way to find them using the tags used on Windows.
Thanks for your attention.
--
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=52838
Bug ID: 52838
Summary: MachStudio Pro renders wrong
Product: Wine
Version: 7.6
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: svyatpro(a)gmail.com
Any project is being rendered wrong in MachStudio Pro. The problem is in Wine's
D2D1.DLL. When using native Vista's d2d1.dll (7.0.6002.18107 809kb) this issue
does not appear.
Steps to repro:
1. Run MachStudio Pro
2. Open a project for example by this path \Program Files\StudioGPU\MachStudio
Pro\Data\assets\SGPU_MTL_BALL.mab
Uploaded two screenshots: Wine's d2d1.dll and native d2d1.dll from Vista.
Free GPU MachStudio Pro download link:
https://download.cnet.com/MachStudio-Pro/3000-6677_4-75498419.html
--
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=30155
Bug #: 30155
Summary: secdrv.sys from SafeDisc v2.05.030 does not work
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: stefan(a)codeweavers.com
Classification: Unclassified
Created attachment 39336
--> http://bugs.winehq.org/attachment.cgi?id=39336
service,relay,winedevice,ntoskrnl log
SafeDisc 2.05.030 does not work out of the box. The user-visible symptom is
that the application exits with exit code 0 without any output. This affects
for example the Command and Conquer Red Alert 2 installer, which is safedisc
protected for some reason.
The problem seems to be related to the specific secdrv.sys version. If I take a
secdrv.sys from a newer safedisc version(e.g. 2.40.010 from the RA2 Yuri's
revenge expansion) and put it in C:\windows\system32\drivers, the installer
works.
ProtectId says:
Scanning -> D:\Setup\Setup.exe
File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 1308863 (013F8BFh)
Byte(s)
-> File has 733375 (0B30BFh) bytes of appended data starting at offset 08C800h
[File Heuristics] -> Flag : 00000000000000000100000000100111 (0x00004027)
[!] Safedisc v2.05.030 detected !
[i] Appended data contents....
[.] o: 0x0008C828 / t: <0x00000001> <0x00000000> <0x00000001> / s: 00194947
byte(s) -> ~de7bc4.tmp
[.] o: 0x000BC1D2 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00030208
byte(s) -> clcd32.dll
[.] o: 0x000C37F9 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00006784
byte(s) -> clcd16.dll
[.] o: 0x000C529D / t: <0x00000001> <0x00000000> <0x0000044D> / s: 00067584
byte(s) -> mcp.dll
[.] o: 0x000D5AC5 / t: <0x00000001> <0x00000000> <0x00000000> / s: 00327220
byte(s) -> ~df394b.tmp
[.] o: 0x00125920 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00034304
byte(s) -> drvmgt.dll
[.] o: 0x0012DF47 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00018768
byte(s) -> secdrv.sys
[.] o: 0x001328BF / t: <0x00000001> <0x00000000> <0x00000000> / s: 00053248
byte(s) -> ~ef7194.tmp
[CompilerDetect] -> Visual C++ 6.0
- Scan Took : 0.640 Second(s)
The md5sum of the broken secdrv.sys is XXX. The md5sum of the working 2.40.010
driver is f376a1580204e47f37a721e1cbc5582a.
I am attaching a +relay,+service,+winedevice+ntoskrnl log of a failed run of
the setup tool.
--
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.