https://bugs.winehq.org/show_bug.cgi?id=50348
Bug ID: 50348
Summary: MFMEv20 Emulator crashes on start
Product: Wine
Version: 6.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adec2011.ac(a)gmail.com
Distribution: ---
Created attachment 68935
--> https://bugs.winehq.org/attachment.cgi?id=68935
Log file for crash
MFMEv20 crashes on start. Log file 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=46330
Bug ID: 46330
Summary: [Feature Request] Enable winelib on ppc64el
Product: Wine
Version: unspecified
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: tpearson(a)raptorengineering.com
Distribution: ---
With the resurgence in POWER hardware support and interest centering around the
POWER8/POWER9 chips, it would be great to get winelib support for the ppc64el
architecture. This would allow Windows open source applications to be used on
these powerful machines (e.g. FEMM, SQLYog, etc.).
--
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=52430
Bug ID: 52430
Summary: Ubi Connect Launcher forever shows a black window
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blue-t(a)web.de
Distribution: ---
Created attachment 71690
--> https://bugs.winehq.org/attachment.cgi?id=71690
Console Log
When you try to run the Ubi Connect Launcher, it never finishes the start
sequence. Instead of showing the "Ubisoft Connect" Text alongside a logo inside
a frame with small status updates in the lower left corner before displaying
news and installed games, it just shows an empty black window that never
vanishes and never gets content.
On the console variuous notes about shaders are repeated.
The AppDB says using corefonts via winetricks should make it boot, but it
doesn't.
The Card is an amd rtx480 on a Kubuntu 21.10.
--
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=46694
Bug ID: 46694
Summary: widl crashes in dlls/atl during build on ppc64el
Product: Wine
Version: 4.2
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tpearson(a)raptorengineering.com
Distribution: ---
Created attachment 63657
--> https://bugs.winehq.org/attachment.cgi?id=63657
Backtrace
Building on ppc64el fails with a segmentation fault in widl while attempting to
build dlls/atl. Backtrace 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=52612
Bug ID: 52612
Summary: Build Error on macOS 12.2.1 with M1 mac
Product: Wine
Version: 7.3
Hardware: arm
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: syurin.nagatuki(a)gmail.com
Created attachment 71939
--> https://bugs.winehq.org/attachment.cgi?id=71939
log
Build Error on macOS 12.2.1 with M1 Mac
Error Message :
clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see
invocation)
Apple clang version 13.0.0 (clang-1300.0.29.30)
Target: arm64-apple-darwin21.3.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
clang: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg:
/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/cmslut-db7957.c
clang: note: diagnostic msg:
/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/cmslut-db7957.sh
clang: note: diagnostic msg: Crash backtrace is located in
clang: note: diagnostic msg:
/Users/syurin/Library/Logs/DiagnosticReports/clang_<YYYY-MM-DD-HHMMSS>_<hostname>.crash
clang: note: diagnostic msg: (choose the .crash file that corresponds to your
crash)
clang: note: diagnostic msg:
********************
make: *** [libs/lcms2/src/cmslut.o] Error 254
--
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=45385
Bug ID: 45385
Summary: Wrong state of virtual keys after cycling windows.
Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every
key can be affected.
Product: Wine
Version: 3.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: johnfound(a)asm32.info
Distribution: ---
I noticed that the state of the keys sometimes sticks in pressed state.
This happens when cycling windows with some shortcut key combination.
For example if cycling with Alt+Tab, on pressing Alt, the program gets
WM_KEYDOWN and the state of the VK_MENU becomes pressed. But after cycling
windows, the program does not get WM_KEYUP because the window is not focused
and VK_MENU (and the respective VK_LMENU or VK_RMENU) remain in pressed state.
When cycling back to the program window, the window get focused only after
releasing Alt key, so it does not get this event as well.
If cycling windows with another shortcut key combination (for example
Alt+Shift+Tab - for backward cycling) both VK_MENU and VK_SHIFT keys stick.
In the same time, GetAsyncKeyState returns the proper state of the keys.
Note1: The problem is obviously in the wineserver code, because it handles the
key state tables for the different threads.
Note2: The effect happens only sometimes. It seems the code for proper
processing is already there, but some racing conditions have place.
Note3: There is some probability that the effect is in result of my application
code, but it never happens on real Windows, so I considered it a bug.
Note4: I tried to workaround this problem by reading the whole table by
GetAsyncKeyState and setting it then with SetKeyboardState on WM_ACTIVATE
message of the main window. This workaround actually works, but is too ugly
IMO.
The same trick on WM_ACTIVATEAPP does not work.
--
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=52737
Bug ID: 52737
Summary: winecfg not open
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jayjameshlw(a)gmail.com
Distribution: ---
archkubi@GnuChanOS ~> winecfg
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
0120:err:winediag:nodrv_CreateWindow Application tried to create a window, but
no driver could be loaded.
0120:err:winediag:nodrv_CreateWindow The explorer process failed to start.
--
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=52735
Bug ID: 52735
Summary: Wine does not launch GUI apps
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bihag37553(a)flowminer.com
Distribution: ---
Wine versions above wine 7.0rc2 don't work for me on intel+nvidia setup on
manjaro linux kernel 5.17.0-1 and I have also tried kernel 5.16. I'm using
nvidia drivers version 510.60.02
When I launch wine, I get the following error:
00f4:err:winediag:nodrv_CreateWindow Application tried to create a window, but
no driver could be loaded.
00f4:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
I have tried deleting the wine prefix and using wine-staging but couldn't fix
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.
http://bugs.winehq.org/show_bug.cgi?id=33058
Bug #: 33058
Summary: Visual Basic 6 crashes when object browser is clicked
Product: Wine
Version: 1.5.24
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: german_ant_82(a)yahoo.com
Classification: Unclassified
Regression SHA1: Visual Basic 6 crashes when object browser button is
clicked
Created attachment 43703
--> http://bugs.winehq.org/attachment.cgi?id=43703
Backtrace
Visual Basic 6 IDE crashes when object browser is clicked
--
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.