https://bugs.winehq.org/show_bug.cgi?id=47539
Bug ID: 47539
Summary: Consider switching from Bugzilla to Gitlab
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lorendias(a)gmail.com
CC: austinenglish(a)gmail.com
Distribution: ---
Other open source projects such-as Gnome, GIMP, etc... have benefited from
switching to Gitlab -- a more modernized collaborative self hosted tool.
I searched a bit and was surprised that I couldn't find a similar discussion
for WineHQ.
I suggest doing some research and considering the benefits of switching --
easier identification of bugs via screenshots or screen-casts can be included
on inline posts. Communications have better Text Markup and can be upvoted or
have reactions. Version control and patches are really straight forward.
I feel that Gnome is a good example of a project benefited as it really it made
it easier for the larger community to coordinate, communicate, and participate.
I think that Gitlab's style is average of what current day developers
expectation as it mirrors tooling already commonly in use -- GitHub in many
ways.
https://gitlab.gnome.org/explore/projects/starred
And now that GitHub is owned by Microsoft and built into VS Code and Microsoft
Coding tooling I think it would be easier to encourage developers to
participate by having familiar tools.
--
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=47643
Bug ID: 47643
Summary: Windows Registry no longer supporting Path Key
Product: Wine
Version: 4.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shagooserver(a)gmail.com
Distribution: ---
Certainly, 1 year ago modifying HKEY_CURRENT_USER>Environment by adding a Path
key caused Wine to follow that path when looking for a exe file. It appears
this is no longer the case as the exact same modification to the Windows
registry results in a file not found message.
--
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=47461
Bug ID: 47461
Summary: XInput: XBox 360 gamepads no longer detected (since
wine 4.7)
Product: Wine
Version: 4.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: felixhaedicke(a)web.de
Distribution: ---
Since Wine 4.7, all my applications which use the XInput API for accessing
gamepads cannot find my Xbox 360 Wireless Controllers any more.
Checked with the following applications:
* Blur
* Cemu - http://cemu.info/
* XInputTest - https://github.com/chrizonix/XInputTest
Messages in wine-4.7 with XInputTest (very similar with other applications):
WINEDEBUG=+xinput wine XInputTest_1000_Samples.exe
001f:fixme:setupapi:SetupDiBuildDriverInfoList : stub 0x113b18, 0xc7f4c8, 2
001f:err:plugplay:install_device_driver Failed to build compatible driver list,
error 0x78.
0009:trace:xinput:XInputGetState (index 0, state 00641A08)!
0009:trace:xinput:XInputGetState (index 0, state 00641A08)!
Error! Player 1 - XBOX 360 Controller Not Found!
And in wine-4.11:
WINEDEBUG=+xinput,+setuapi wine XInputTest_1000_Samples.exe
001e:err:setupapi:open_driver_key Failed to open driver key, error 2.
001e:err:setupapi:open_driver_key Failed to open driver key, error 2.
001f:err:setupapi:SetupDiSelectBestCompatDrv No compatible drivers were
enumerated for device
L"SDLJOY\\VID_045E&PID_02A1&IG_0\\256&030000005E040000A102000000010000&0&0".
001f:err:plugplay:install_device_driver Install function 0x17 failed, error
0xe0000228.
0009:trace:xinput:XInputGetState (index 0, state 00641A08)!
0009:trace:xinput:XInputGetState (index 0, state 00641A08)!
Error! Player 1 - XBOX 360 Controller Not Found!
Press Enter Key To Exit
And in wine-4.6 (which works fine):
WINEDEBUG=+xinput,+setuapi wine XInputTest_1000_Samples.exe
0009:trace:xinput:XInputGetState (index 0, state 0x531a08)!
0009:trace:xinput:HID_find_gamepads Found gamepad 0
L"\\\\?\\HID#VID_045E&PID_02A1&IG_1#256&030000005E040000A102000000010000&0#{4D1E55B2-F16F-11CF-88CB-001111000030}"
Ready! Waiting for 0009:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0032FC8C 1
C) semi-stub
0009:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0032FA7C 1 C) semi-stub
1000 Samples (Move Left Stick)0009:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr
(0032FC6C 1 C) semi-stub
0009:trace:xinput:XInputGetState (index 0, state 0x531a08)!
0009:trace:xinput:XInputGetState (index 0, state 0x531a08)!
0009:trace:xinput:XInputGetState (index 0, state 0x531a08)!
0009:trace:xinput:XInputGetState (index 0, state 0x531a08)!
0009:trace:xinput:XInputGetState (index 0, state 0x531a08)!
0009:trace:xinput:XInputGetState (index 0, state 0x531a08)!
0009:trace:xinput:XInputGetState (index 0, state 0x531a08)!
...
Tested with unmodified Wine builds.
--
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=47695
Bug ID: 47695
Summary: Colony prospector (Steam) need unimplemented function
msvcrt.dll._ftol2_sse
Product: Wine
Version: 4.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: mc2374(a)mclink.it
Distribution: Other
PC System with Rosa Linux Fresh 2016.1 x86_64, wine 32bit 4.14 (+ Staging &
latest dxvk), mesa 19.1.4
The game Colony prospector, available on Steam, won't run; it starts and near
immediately closes, while in the error output the two lines reported below
appear a few times:
*************
wine: Call from 0x7bc8f9f9 to unimplemented function msvcrt.dll._ftol2_sse,
aborting
************
I cannot say for sure that this is the only reason for the game starting
failure, but it is involved...
--
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=47388
Bug ID: 47388
Summary: “Page fault on read access to 0x00000000 in 32-bit
code” in multiple games
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BabylonAS(a)yandex.ru
Distribution: ---
Created attachment 64723
--> https://bugs.winehq.org/attachment.cgi?id=64723
Wing Commander: Prophecy crash backtrace
Hello everyone.
I’ve attempted to install some Windows-only games on my ThinkPad X31 (32-bit)
running Debian 10 (while technically it is not released yet, I’ve switched to
use the “testing” repositories, which are used to prepare the tenth version’s
release) using Wine 4.0. So far I tried the first Galactic Civilizations (with
the expansion, Altarian Prophecy), Civilization III (with both expansions, Play
the World and Conquests), Sid Meier’s Alpha Centauri (with the expansion, Alien
Crossfire) and Wing Commander: Prophecy. All games (except Alpha Centauri,
which has been bought digitally on GOG.com which only provides a Windows
version) have been installed from compact discs, and might not be the latest
versions.
All of them succumbed to a “Page fault on read access to 0x00000000 in 32-bit
code” or similar error upon launching. GalCiv’s map editor (introduced with
Altarian Prophecy) also did crash, and Alpha Centauri’s GOG installer did
trigger the error as well (but it didn’t led to fatal consequences). Wherever I
took a look at the backtrace, I saw a failure of the assembler instruction
“movl 0x0(%eax),%ecx” (the registers and the 0x0 part can vary). By this point
I’ve only saved backtraces for two of the crashes, specifically of Wing
Commander: Prophecy and Alpha Centauri (with Alien Crossfire).
I’ve seen a bunch of other bug reports involving “movl 0x0(%eax),%ecx” or
similar cases, but they appear to refer to old versions of Wine and not be
updated in a long time. Only https://bugs.winehq.org/show_bug.cgi?id=40334 with
a similar “page fault on read access to 0x00000000” seems to be recent, but it
is a crash of 64-bit code and doesn’t disclose the exact failing instruction.
--
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=47348
Bug ID: 47348
Summary: Winecfg doesn't work after update from 4.9 to 4.10
Product: Wine-staging
Version: 4.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chillabis(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 64683
--> https://bugs.winehq.org/attachment.cgi?id=64683
Winecfg_paste_from_terminal
I'm using Ubuntu 18.04 LTS and just updated from wine 4.9 to 4.10 and now
winecfg doesn't 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=47829
Bug ID: 47829
Summary: taxpool book-keeping software crashes when trying to
create eür-anlage
Product: Wine
Version: 3.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: murxs(a)web.de
Distribution: ---
Created attachment 65335
--> https://bugs.winehq.org/attachment.cgi?id=65335
Im Programm tp-buchhalter.exe traten schwerwiegende Fehler auf...
Wine version: wine-3.0 (Ubuntu 3.0-1ubuntu1)
The software im working with is tp-buchhalter, recently installed with pol.
Most functions seem to work as usual but if i try to create the eür-Anlage i
get the error notice in the attachement. There used to be a free version but i
cant find it anymore (https://www.taxpool.net/bestellen.html, its the version
Taxpool-Buchhalter EÜR) Thanks for help
--
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=47504
Bug ID: 47504
Summary: vkd3d-git + vulkan-headers >= 1.1.113
Product: vkd3d
Version: 1.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: ---
Hello Josef,
I updated vulkan-loaders on Gentoo to vulkan 1.1.114 and vkd3d-git still
crashes during compilation because headers is too old.
----
checking whether VK_HEADER_VERSION >= 113... no
configure: error: Vulkan headers are too old, 1.1.113 is required.
----
when i check headers version on my system :
----
odelpasso@gentoo-desktop ~/Bureau $ ls /usr/share/doc/vulkan*
/usr/share/doc/vulkan-headers-1.1.114:
README.md.bz2
/usr/share/doc/vulkan-loader-1.1.114:
README.md.bz2
----
How vulkan headers version is checked ?
--
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=46628
Bug ID: 46628
Summary: Resident Evil 2 crash at loading
Product: Wine-staging
Version: 4.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahmed.com(a)protonmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63527
--> https://bugs.winehq.org/attachment.cgi?id=63527
Resident Evil 2.log
Resident Evil 2 crashes at loading. This problem is not related to mfplat.dll,
because mfplat issue happens after starting the game, and I already fixed the
same issue with Resident Evil 7 Biohazard, and it runs well.
System info:
Manjaro Linux 18.02
Kernel 4.19.20-1
Mesa-git 19.1
Wine-staging 4.1.1
DXVK 0.96
--
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=47449
Bug ID: 47449
Summary: Nin Online: Black Textures
Product: Wine
Version: 4.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: dx8vb
Assignee: wine-bugs(a)winehq.org
Reporter: hellator(a)gmail.com
Distribution: ---
This bug happens in multiple distributions and versions of Wine.
1. Install GDIPlus (Windows 7+)
2. Install Dx8vb DirectX8.1
3. Install DotNet40
4. Install CoreFonts
https://www.ninonline.org/index.php
This game has black texture bugs. It also does not transfer DirectX8 API calls
to DirectX9 the same way it does in Windows.
https://github.com/crosire/d3d8to9/https://i.imgur.com/QXcMtzv.png
The texture bugs are black and do not use transparency (opacity) in some
sprites and tiles on game map. It does not affect the GUI I think.
--
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.