https://bugs.winehq.org/show_bug.cgi?id=47902
Bug ID: 47902
Summary: CheckForWinetestUpdate systematically claims to have
created jobs
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
CheckForWinetestUpdate.pl ends with the following lines:
LogMsg "Submitted jobs\n";
exit $Rc;
So whenever cron runs it this line appears in the TestBot log, even if the
WineTest binaries have not been updated and no job was created. So while this
allows making sure the script is still running as expected, the message is
misleading. It would be better if it exited either with a message saying there
was no update or which jobs got created.
--
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=47878
Bug ID: 47878
Summary: VirtualProtect across page boundaries does not work
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: c3210606(a)urhen.com
Distribution: ---
Official VirtualProtect documentation states:
The size of the region whose access protection attributes are to be changed, in
bytes. The region of affected pages includes all pages containing one or more
bytes in the range from the lpAddress parameter to (lpAddress+dwSize). This
means that a 2-byte range straddling a page boundary causes the protection
attributes of both pages to be changed.
This however is not replicated in Wine as only the first page will have its
protection changed and any pages after that resulting from the dwSize crossing
the boundary will not be affected.
--
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=47835
Bug ID: 47835
Summary: `-funroll-loops` breaks wine, "wine: Unhandled page
fault on write access to 0x00000000 at address ..."
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zegentzy(a)protonmail.com
Distribution: ---
As the name implies, compiling with `-funroll-loops` breaks wine. Every part of
it, from winedbg, to wine, to wineboot. Tested against both the latest wine on
git, wine 4.15, and wine 4.15. GCC 9.1.0. Arch Linux.
This is `winedbg`, for example:
```
wine: created the configuration directory '/home/gentz/.wine'
000b:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
000b:fixme:winediag:start_process Wine Staging 4.16 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0012:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0014:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
wine: Unhandled page fault on write access to 0x00000000 at address
00006BB2783C2DB9 (thread 0014), starting debugger...
0014:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 19 80" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
0000634EEE5AADB9 (thread 0012), starting debugger...
0012:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 17 88" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
000062C321ACADB9 (thread 0010), starting debugger...
0010:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 15 84" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
^C0009:err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xea872929
```
Here is `winecfg`:
```
winecfg
wine: created the configuration directory '/home/gentz/.wine'
000b:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
000b:fixme:winediag:start_process Wine Staging 4.16 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0012:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0014:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
wine: Unhandled page fault on write access to 0x00000000 at address
000060CC8A44ADB9 (thread 0012), starting debugger...
0012:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 17 80" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
00006628B5FD2DB9 (thread 0014), starting debugger...
0014:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 19 88" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
^C0009:err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xe16b1929
```
I'm marking this as minor, as the workaround is trivial: just don't build with
`funroll-loops`, but hopefully someone looks into it. I did some searching, and
couldn't find this already reported, but feel free to close if it's a dupe,
sorry!
--
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=47892
Bug ID: 47892
Summary: Cinebench crashes just after finishing benchmark
Product: Wine
Version: 4.12.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gnarlin(a)gmail.com
Distribution: ---
Created attachment 65382
--> https://bugs.winehq.org/attachment.cgi?id=65382
Wine running cinebench r15 console output crashinfo
Cinebench crashes just after finishing benchmark just before it can display the
results.
--
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=46102
Bug ID: 46102
Summary: Wine cannot recognize Turkish keyboard layout
Product: Wine
Version: 3.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yurnerolinux(a)yandex.com
Distribution: ---
I noticed that in some games , both on plain Wine ( i'm using staging ) and
both on Proton.
On Fallout: New Vegas , you can't type "i" when Turkish keyboard layout
selected. Game ( or Wine probably , since game doesn't know about it ) just
shows it as " when you pressed "i" button. Same behaviour is also going on with
Skyrim.
When i set my keyboard layout to English thorugh my system , "i" starts to work
again.
Another example is Deus EX: Human Revolution - Director's Cut on Proton. I
realized i can't open up tab menu ( tab key ) when my keyboard set to Turkish.
If i set my keyboard English again , it starts to work.
My keyboard layout is Turkish Q keyboard.
--
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=47757
Gijs Vermeulen <gijsvrm(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|STAGED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Gijs Vermeulen <gijsvrm(a)gmail.com> ---
This has been removed from staging now. Marking this as a dupe of bug 47758.
*** This bug has been marked as a duplicate of bug 47758 ***
--
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=47830
Bug ID: 47830
Summary: Exact Audio Copy (EAC) does not run with latest
development release
Product: Wine
Version: 4.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stefan(a)konink.de
Distribution: ---
Created attachment 65336
--> https://bugs.winehq.org/attachment.cgi?id=65336
Problem running EAC with mono-only installation
I ran Exact Audio Copy using a stock Ubuntu wine package, from the 4.0.x
branch. In this installation I stumbled on the issue that the EAC plugins were
not recognized. This issue is said to be fixed in #43270. I have manually
compiled Wine 4.17 for 32bit, which let to the output in the attachment.
After winetricks dotnet20 I was able to run EAC.exe, including the plugins that
were previously missing, this resulted in not able to retrieve information
about CDs. But this seems to be a side effect of the plugins "working". When
selecting Build-in freedb engine under Metadata options, information was
retrieved. The second attachment shows the problem using the CUETools plugin.
I have reproduced the steps with winehq-devel (4.17~disco):
Download: https://www.fosshub.com/Exact-Audio-Copy-DE.html?dwl=eac-1.3.exe
Run: wine eac-1.3.exe
Validate the output in output.txt after starting the application.
Run: winetricks dotnet2
Run: cd ~/.wine/drive_c/Program\ Files\ \(x86\)/Exact\ Audio\ Copy/
Run: wine EAC.exe
Cancel the CD-rom detection. Insert a common audio CD. Alt-G, specify e-mail.
Another Alt-G. Validate the output in output-networking.txt after starting the
application.
--
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=45508
Bug ID: 45508
Summary: wine staging and gallium patches
Product: Wine-staging
Version: unspecified
Hardware: x86
URL: https://github.com/sarnex/wine-d3d9-patches
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hasculdr(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Hello. It's possible to add this patches:
https://github.com/sarnex/wine-d3d9-patches
to wine-staging project? Thanks.
--
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=47845
Bug ID: 47845
Summary: Bug to x86_64
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: haasesaah(a)gmail.com
Distribution: ---
My original architecture was x64 but as I like play some games in x86 I did
convert with add-apt-repository ppa: architecture i386 to turn over x86_64 and
after that I had trouble within ever runnig up the games at x86 architecture.
Well, I thought the x86_64 architecture would support both. As x86 and x64.
Sorry about my barely english typewriting. Thank you so very much.
--
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=21312
Summary: Sony Vegas Movie Studio Platinum 9.0b: Serious issues
making video production impossible
Product: Wine
Version: 1.1.35
Platform: x86-64
URL: http://www.softpedia.com/get/Multimedia/Video/Video-Ed
itors/Sony-Vegas-Movie-Studio-Platinum.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gaming4jc2(a)yahoo.com
Created an attachment (id=25649)
--> (http://bugs.winehq.org/attachment.cgi?id=25649)
Numerous FixMes and some Errs...
Well, I finally got it installed using winetrick's dontnet20 and wmp9 as
suggested on my previous bug report for not being able to install it.
It only works on Windows Vista and above compatibility modes, so the log
attached was using Windows 7 which seems best.
I'm not sure where to start on this bug report.
Sony Vegas Movie Studio 9.0b Platinum has several serious issues, all of which
we should be able to be determined from the short log attached.
I'll list them below:
* No plug-ins were found. (This includes the Media Generator, Transitions, and
Video FX tabs making them totally unusable) This effects the majority of the
application and the "Video Event FX..." window, making the program somewhat
useless.
* The Audio "Track FX..." and "Apply Non-Real Time Event FX..." windows are
both totally unusable since nothing can be clicked in them. The audio plugins
there are at least detected, just borked.
* Video Preview Window doesn't show anything, and occasionally flickers a
different color only when rendering. Terminal cycles a never ending
"fixme:msvideo:DrawDibDraw" bug when attempting to play the movie. This also
effects the "Video Event Pan/Crop..." window, making it nearly impossible to do
animation effects since determining your current location in the window is
simply a black screen.
* All icons have a black rectangle around them (trivial and probably just a
simple alpha transparency bug)
Note: Keyword download can be added since Sony Vegas Movie Studio has a free
trial. I made this log using the retail version, but it's using the same exe as
the one on the softpedia link provided.
--
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.