https://bugs.winehq.org/show_bug.cgi?id=51418
Bug ID: 51418
Summary: fotoBiz X - Fatal error on startup
Product: Wine
Version: 6.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 70272
--> https://bugs.winehq.org/attachment.cgi?id=70272
Backtrace (6.11)
Hello everyone,
I am revisting an old application where the installer has been fixed and now
works but unfortunately I am running into a different problem. Backtrace is
attached.
--
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=51464
Bug ID: 51464
Summary: Pagefault error caused by qt5webenginecore
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: shadowbranch(a)gmail.com
Distribution: ---
Created attachment 70305
--> https://bugs.winehq.org/attachment.cgi?id=70305
Backtrace from Pagefault
Running the latest Kaseya Live Connect 9.5.0.24. When connecting to server
program crashes with pagefault error.
--
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=47412
Bug ID: 47412
Summary: Kaseya Live Connect: crashes on first run after
install
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: registry
Assignee: wine-bugs(a)winehq.org
Reporter: alero5752(a)hotmail.com
Distribution: ---
Created attachment 64760
--> https://bugs.winehq.org/attachment.cgi?id=64760
Progam Error details
Hello,
Linux noob here. My company recently upgraded our Kaseya VSA version to 9.5.0.2
and ever since this was completed it broke my Kaseya Live Connect app
compatibility within Wine. I've attached the log to review and also a link to
the EXE file for the application below. This is the very latest version of
Kaseya. When attempting to launch the program, it stops and displays an error,
(The program QtWebEngineProcess.exe has encountered a serious problem and needs
to close. We are sorry for the inconvenience).
https://drive.google.com/file/d/1StEVxsaQFKTVX8pb6htmo8r_4R14btJz/view?usp=…
--
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=34377
Bug #: 34377
Summary: Paint Shop Pro X5 Installer fails
Product: Wine
Version: 1.6
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: maikwagner(a)yahoo.com
Classification: Unclassified
Created attachment 45757
--> http://bugs.winehq.org/attachment.cgi?id=45757
Backtrace
Hello everyone,
I have been testing "Paint Shop Pro X5" from Corel but I am having problems to
get it to install correctly. Please find my backtrace attached and please let
me know should you require further information.
--
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=12732
Summary: Nota Bene crashes on install
Product: Wine
Version: CVS/GIT
Platform: PC
URL: https://www.notabene.com/download/demos/nbdemo80.exe
OS/Version: Linux
Status: NEW
Keywords: download, Installer, win16
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Testing for bug 11023 I found that nota bene will no longer install. I'll start
the regression test...
--
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=50433
Bug ID: 50433
Summary: 'MsiBreak' custom action debugging aid should use
custom action's name from 'CustomAction' table
(currently uses 'Target' field)
Product: Wine
Version: 6.0-rc4
Hardware: x86-64
OS: Linux
Status: NEW
Severity: trivial
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
I always have to remember that Wine uses 'Target' field/name from the
'CustomAction' table instead of the custom action's name when debugging custom
actions. Fooled me quite a number of times in these 13 years.
I'm aware that very few people might be concerned/affected with this
inconsistency but still.
https://docs.microsoft.com/en-us/windows/win32/msi/debugging-custom-actions
I requested the installer debugging aid in 2007 in bug 8243 ("Feature: Add
MsiBreak to aid debugging custom actions"):
https://source.winehq.org/git/wine.git/commitdiff/60e95ee6e8ea4a4f43a6c170c…
("msi: Add handling for MsiBreak.")
My follow-up comment https://bugs.winehq.org/show_bug.cgi?id=8243#c7 was
ignored. Maybe because I didn't bother to create a follow-up bug and/or didn't
complain loud enough ;-)
--- quote ---
Please fix the evaluation to use "action" msi_custom_action_info member instead
of "target" to make it feature compatible with Windows MSI server.
--- quote ---
Some example (from bug 21987):
--- snip ---
...
01b0:trace:msi:ACTION_CustomAction Handling custom action
L"CreateAdobePDFPrinter" (c41 L"AdobeIsf" L"SetupAdobePDFPrinter")
...
01b0:trace:msi:HANDLE_CustomType1 Calling function L"SetupAdobePDFPrinter" from
L"C:\\users\\focht\\Temp\\msi48b7.tmp"
...
02f8:Ret PE DLL (proc=0160618A,module=01600000
L"msi48b7.tmp",reason=PROCESS_ATTACH,res=00000000) retval=1
...
02f8:Ret KERNEL32.LoadLibraryW() retval=01600000 ret=100210f6
02f8:Call KERNEL32.GetProcAddress(01600000,0016df28 "SetupAdobePDFPrinter")
ret=1002110a
02f8:Ret KERNEL32.GetProcAddress() retval=01602bea ret=1002110a
...
--- snip ---
To have this work for Wine 'MsiBreak=SetupAdobePDFPrinter' is needed but
'MsiBreak=CreateAdobePDFPrinter' would be correct.
$ wine --version
wine-6.0-rc4
Regards
--
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=50869
Bug ID: 50869
Summary: Regressions caused by new start.exe behaviour in Wine
6.5 (stdout redirect, killing inferior, wine start
/unix)
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)robbertvanderhelm.nl
Distribution: ---
I noticed a few regressions and new weird behaviours after updating to Wine 6.5
with regards to launching applications now that everything gets launched
through
start.exe:
1. When launching Winelib applications all STDOUT output gets lost. I tested
this with a simple C++ file compiled with wineg++ that tries to print some
text using both `printf()` and `std::cout`. Printing to STDERR using
`std::cerr` still works fine.
2. When spawning a Wine child process from another application, you can no
longer kill that child process by raising SIGINT or SIGKILL for the pid of
the child. In Wine 6.5 this now kills the start.exe process, but it leaves
the inferior process running in the background. To reproduce this, run `wine
notepad&` in `fish` (bash seems to kill the child process by itself), use
`ps -aux | grep notepad` or `jobs` to find the pid of the process just named
`notepad`, and then run `kill -SIGKINT <pid>` (or with SIGKILL). Even though
the process launched using `wine notepad&` has exited, Notepad is still
running in the background.
3. (duplicate of bug 50867, but I still wanted to mention it here for
completeness' sake) Launching binaries with Wine from the GUI by clicking on
them (using the bundled wine.desktop) no longer works. This uses
`wine start /unix`, which was already reported to no longer work as of Wine
6.5 in the other issue because `ShellExecuteEx` cannot find the file.
4. And lastly, as discovered by @stefand, `wine https://google.com` now
launches
the regular system browser. This is probably not really a bug as much as a
consequence of the start.exe change, but I just wanted to mention it.
Please let me know if I should split this up into separate tickets.
--
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=50352
Bug ID: 50352
Summary: Maximum sockets per process is set very low
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: skreech(a)skree.ch
Distribution: ---
Created attachment 68942
--> https://bugs.winehq.org/attachment.cgi?id=68942
TWGS warning at startup
Within wine-5.22/dlls/ws2_32/socket.c, the maximum number of sockets per
process is set and used like so:
> #define WS_MAX_SOCKETS_PER_PROCESS 128 /* reasonable guess */
and:
> lpWSAData->iMaxSockets = WS_MAX_SOCKETS_PER_PROCESS;
This became relevant when I ran the TradeWars 2002 game server (TWGS) under a
maximum license allowing 100 simultaneous players. On startup, it logs a
message warning that the OS's number of sockets per process is limited to 128,
therefore no more than 63 players will be able to connect. This makes sense,
since two sockets are required per player connection, and one SysOp connection
is reserved.
Changing WS_MAX_SOCKETS_PER_PROCESS to 1024 and recompiling WINE results in
TWGS not experiencing this limit and not giving the warning.
Also, I tested TWGS under ReactOS and did not experience limit nor warning.
Peeking into their socket.c, I notice that their limit is set to 32767, or 0,
depending:
https://github.com/reactos/reactos/search?q=iMaxSockets
It seems likely that WS_MAX_SOCKETS_PER_PROCESS should be set to 32767 here if
any value is being set, given that the underlying OS should be the one imposing
its own limits or lack of limit.
--
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=44202
Bug ID: 44202
Summary: undname.c fails to parse symbols with rvalue-reference
semantics '&&'
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shulgaaa(a)gmail.com
Distribution: ---
For example, the symbol
??4QDnsDomainNameRecord@@QAEAAV0@$$QAV0@@Z
should be de-mangled as:
public: class QDnsDomainNameRecord & __thiscall
QDnsDomainNameRecord::operator=(class QDnsDomainNameRecord &&)
undname returns NULL
--
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=51900
Bug ID: 51900
Summary: regression: REAPER scrollbars flash between themed and
non-themed
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: uxtheme
Assignee: wine-bugs(a)winehq.org
Reporter: s_chriscollins(a)hotmail.com
Distribution: ---
Created attachment 70847
--> https://bugs.winehq.org/attachment.cgi?id=70847
video showing the bug
Starting with Wine 6.13, scrollbars in REAPER will flash between themed and
non-themed graphics when the mouse cursor passes over or interacts with them.
The attached video shows the behavior in Wine 6.12 (correct) followed by Wine
6.13 (glitchy).
A regression test pinpoints the following commit as the culprit:
-------------------------------------------------------------------
commit 883878e550d263fd9caedd4ba5ee8c142407c010
Author: Zhiyi Zhang <zzhang(a)codeweavers.com>
Date: Tue Jul 20 21:12:15 2021 +0800
uxtheme: Support scroll bar state tracking in non-client areas.
Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
dlls/user32/controls.h | 3 +++
dlls/user32/defwnd.c | 11 +++++++++++
dlls/user32/nonclient.c | 33 +++++++++++++++++++++++++++++++++
dlls/user32/scroll.c | 37 ++++++++++++++++++++++++++++++++++---
4 files changed, 81 insertions(+), 3 deletions(-)
-------------------------------------------------------------------
This bug is still present in master as of today (10/18/21) and can be
reproduced in a VirtualBox VM. REAPER can be downloaded for free from:
http://reaper.fm/
--
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=50370
Bug ID: 50370
Summary: Gothic 1 doesn't start correctly when screen
resolution of the game matches display resolution
Product: Wine
Version: 5.13
Hardware: x86-64
URL: https://www.fileplanet.com/archive/p-5260/Gothic-Demo-
English
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: f90d607c67768f19e36d9d74b498594252faa3fd
Distribution: ---
I'm starting Gothic 1 v1.08k using in-game resolution 1440x900 which matches my
native display resolution.
The game does start up because I can hear the sound of the intro movie, but no
visible window is created (the screen is black).
This used to work up until
commit f90d607c67768f19e36d9d74b498594252faa3fd
ddraw: Use the WINED3D_SWAPCHAIN_NO_WINDOW_CHANGES flag.
Reverting that commit on top of 6.0-rc3 fixes the problem for me.
To reproduce the problem in the demo:
1. Before starting the game modify GOTHIC.INI located in the Program
Files/Piranha Bytes/Gothic 1 Demo/system directory.
Look for the section [Video] and change in-game screen resolution there so that
it matches your display resolution:
zVidResFullscreenX=
zVidResFullscreenY=
You also need to set 32-bit color depth (the problem doesn't occur with
16-bit):
zVidResFullscreenBPP=32
2. run gothic.exe
setupg1demo-en.exe
md5sum: 2932bcb79118abadca0d394a7a86c096
wine-6.0-rc3
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 455.46.04
--
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=51619
Bug ID: 51619
Summary: advapi32:registry fails in Wine because a German
timezone name translation is too long
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
advapi32:registry fails in the timezone tests in a German locale:
registry.c:4339: Test failed: L"Aus Central W. Standard Time": expected
L"West-Zentralaustralische Normalzeit", got L"Aus Central W. Standard Time"
registry.c:4357: Test failed: L"Aus Central W. Standard Time": expected
L"West-Zentralaustralische Sommerzeit", got L"Aus Central W. Daylight Time"
https://test.winehq.org/data/patterns.html#advapi32:registry
The reason is that the test compares the localized obtained through the
registry with the one obtained through EnumDynamicTimeZoneInformation(). But
the latter translation must fit into a 32 character buffer: WCHAR
StandardName[32].
However Wine's German translation is too long (36 character including the
trailing '\0'), causing EnumDynamicTimeZoneInformation() to return the
untranslated string instead.
Potential fixes
---------------
1. Only compare the values if they fit in the {Daylight,Standard}Name buffer.
- That means Windows applications will not get a translated timezone name
which is bad.
- This prevents detecting further issues.
- It's unclear if returning an untranslated string is the right thing for
EnumDynamicTimeZoneInformation() to do: I did not find a case (at least
in German where a translation did not fit).
2. Modify EnumDynamicTimeZoneInformation() to return a truncated translation
instead of an untranslated string.
- Windows applications will get a not quite correct timezone name.
- Also we would need evidence that this matches the Windows behavior.
3. Modify the German translation.
- This side-steps the issue and may be the best solution.
- But I doubt one can find a shorter translation that fits, short of
using ellipses which is not great.
Detecting / Preventing recurrences
----------------------------------
1. It would be nice to be able to include a translator warning about this
issue. I'm not sure how to do so in dlls/tzres/tzres.rc.
2. The current tests are insufficient to detect further issues
- To detect every issue they would have to be run in every locale.
- Or going forward, whenever a PO file is modified they would need to be
run in that locale.
- Maybe issues could be detected by calling RegLoadMUIStringW() for every
timezone and locale combination. However it does not take an LCID which
makes this complicated.
3. Write a script checking the PO files.
- This seems like the simplest option to detect issues.
- When to run it? Manually? Automatically from the makefiles?
--
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=51163
Bug ID: 51163
Summary: WinOffice Pro 5.3 stops after splashscreen
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 70031
--> https://bugs.winehq.org/attachment.cgi?id=70031
Console Output (wine 6.8)
Hello everyone,
I came across a forum question where somebody asked how to get the German
accounting application WinOffice Pro 5.3 to run. There is a 60 day trial
version available and I noticed that the application requires mdac27 and jet40
in a 32-Bit prefix to perform a successful installation.
Starting the application works until the splashscreen but then the application
terminates. Console output is attached.
--
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=45916
Bug ID: 45916
Summary: x64dbg does not open executables, nothing happens
Product: Wine
Version: 3.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: jimbo1qaz(a)gmail.com
Distribution: ---
When I File/Open or drag a .exe file into x32dbg (x64dbg 32-bit), the exe does
not load onto the graphs, and Ctrl+G doesn't work. I think the EXE is not
loaded by the debugger at all.
Fixed by ~/bin/winetricks vcrun2013 .
Wine 3.16 on Debian on Virtualbox.
--
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=25257
Summary: Enabling Virtual desktop by default cannot be turned
off for specific applications
Product: Wine
Version: 1.3.7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: zzarko(a)gmail.com
My system is Ubuntu 10.10 and Wine is installed from Ubuntu Wine team's PPA.
Steps to reproduce the problem:
1. Select Default settings in Configure Wine/Applications tab and check
Graphics/Enable virtual desktop
2. Add an application (in my case, Subtitle Workshop) to Applications tab and
uncheck the same option for this application
3. Start the application -> application is started in virtual desktop, despite
the different setting for that application
--
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=52118
Bug ID: 52118
Summary: The 64-bit crypt32:store test crashes due to heap
corruption
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The 64-bit crypt32:store crashes due to heap corruption:
crypt32:store:0224 done (-1073740940) in 0s
Test failed: crash (c0000374)
https://test.winehq.org/data/patterns.html#crypt32:store
The crashes only happen with the 64-bit build. They happen almost
systematically on the TestBot's w864 VM and cw-rx460. It looks like the same
crash happens on the TestBot's Windows 10 1507, 1607 and 2009 VMs.
At least on cw-rx460 the crash happens around the last CertCloseStore(store,
0); call in testRegStoreSavedCerts(). Adding traces changes the crash location
a bit.
Also the test tends to crash every other time. That suggest there is some
cleanup 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=50936
Bug ID: 50936
Summary: Several games (The suicide of Rachel Foster, Far lone
sails & Virginia) crashes after some times with vulkan
rendeder
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
The suicide of Rachel Foster & Virginia just crashes. For Far lone sails it
becomes very slow before crashing.
No backtrace. The console output is pretty silent.
With the GL renderer, Virginia & Far lone sails just works fine and can be
finished from start to end without interruption.
I can't test GL renderer with The suicide of Rachel Foster due to bug
https://bugs.winehq.org/show_bug.cgi?id=50764 which makes the game unplayable.
Setup is wine-6.5-156-g2fcc1d0ecde + Ubuntu 20.10 + GTX1070 + nvidia driver
460.39.
--
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=51990
Bug ID: 51990
Summary: Far Cry - New Dawn, won't open: unimplemented function
ntdll.dll.RtlGetCurrentUmsThread
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: gab.pulcio(a)gmail.com
Distribution: ---
Created attachment 70979
--> https://bugs.winehq.org/attachment.cgi?id=70979
Reason of the bug
Title
--
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=51203
Bug ID: 51203
Summary: Chessbase 11 unable to select list box item after
incorrect window refresh
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dav75uk(a)yahoo.co.uk
Distribution: ---
After search termination (wrong window brought to front - 51202), it is
possible to bring the right window to the front and click on an item from the
search. This displays the game in the window, however, the selected item is not
highlighted, and double clicking (to open the game in a new window - must be
from the selection) opens an old selected item not from the current window.
Workaround is to right click for the menu, and then selection works again (the
window must get focus for selection which it didn't have before (only focus for
clicks)).
This may also relate to the problem of missing scrollbars not being refreshed
(will link report).
--
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=47925
Bug ID: 47925
Summary: Panel in dialog incorrectly drawn
Product: Wine
Version: 4.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dav75uk(a)yahoo.co.uk
Distribution: ---
Created attachment 65425
--> https://bugs.winehq.org/attachment.cgi?id=65425
snapshot of problematic dialog
In Chessbase 11, inputting incorrect security key details results in a dialog.
The panel that rests in it is not correctly drawn. In this case pictured the
white background does not fill the dialog, and sometimes is of different sizes.
Sometimes the message is missing. This happens every time. Using full screen on
a 4K display.
Suggestion of an incorrect (or order of) initialisation issue, 4K/screen size
issue or a data race?
--
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=47990
Bug ID: 47990
Summary: Wine64: Candidate of CJK input method is invisible on
macOS Catalina.
Product: Wine
Version: 4.18
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jactry92(a)gmail.com
Created attachment 65509
--> https://bugs.winehq.org/attachment.cgi?id=65509
WINEDEBUG=+tid,+pid,+imm,+keyboard,+key,+macdrv
Tested with wine-4.18-112-g717109ce79:
1. $ wine64 notepad
2. Switch to Chinese Pinyin input method, and try to type something
You will find that candidate didn't display, though you still can type some
Chinese characters into notepad with the input method.
I didn't see similar on macOS 10.14, so I think this is a Catalina special
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=51775
Bug ID: 51775
Summary: Axiom Verge 2 crashes on startup due to incomplete
sapi implementation
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: sapi
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
This game initializes sapi, even though it doesn't appear to use it at all.
It appears from the .NET backtrace, that
speechsynthesizer.SetOutputTotDefaultAudioDevice is at fault.
After playing around, we can reproduce the crash in a C# application with the
following lines
...
System.Speech.Synthesis.SpeechSynthesizer synth = new SpeechSynthesizer();
synth.SetOutputToDefaultAudioDevice();
...
Function SetOutputToDefaultAudioDevice, requires that basic iteration and a few
registry values are in place.
--
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=38604
Bug ID: 38604
Summary: winedbg: internal crash when valgrinding
ieframe/tests/ie.c with pdb debug symbols
Product: Wine
Version: 1.7.43
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
Created attachment 51499
--> https://bugs.winehq.org/attachment.cgi?id=51499
log
See also bug 38594 for a similar issue, though this one causes winedbg to
crash. Log is attached.
--
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=15679
Summary: cygwin symlinks not working in wine
Product: Wine
Version: 1.1.6
Platform: Other
URL: http://cygwin.com
OS/Version: other
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Surprisingly, cygwin seems to work nowadays,
as long as you do everything inside a wineconsole
running cygwin.bat. (Perhaps cygwin apps should
work outside wineconsole; that would be a separate
bug report.)
However, cygwin's gcc doesn't work unless you
replace certain cygwin symlinks with unix ones, e.g.
$ cd .wine/drive_c/cygwin/usr/i686-pc-cygwin/bin
$ for a in *; do ln -sf ../../../bin/$a; done
Likewise, /bin/vi doesn't work, as it's a symlink to vim.exe.
In fact, cygwin's ls -l doesn't even recognize cygwin's symlinks as such:
$ ls -l vi
-rw-r--r-- 1 dank mkpasswd 18 Oct 19 05:53 vi
$ cat vi
!<symlink>vim.exe
So either they're not being created right, or they're
not being recognized properly by cygwin for some reason,
or both.
--
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.