http://bugs.winehq.org/show_bug.cgi?id=25139
Summary: Microsoft Flight Simulator X demo displays first-run
license agreement dialog under splash screen
Product: Wine
Version: 1.3.7
Platform: x86
URL: http://www.microsoft.com/games/flightsimulatorx/downlo
ads.html
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
When launching the Flight Simulator X demo for the first time, the game shows a
splash screen and displays a first-run end-user license agreement dialog for
the user to accept. However, the dialog appears under the splash screen, which
entirely covers the window and prevents the user from accepting the license
agreement. The window manager in use is metacity 2.30.1, and launching Flight
Simulator X in a virtual desktop or moving the license agreement dialog through
the window manager suffices as a workaround.
--
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=50009
Bug ID: 50009
Summary: Scrivener installer fails on 5.19
Product: Wine
Version: 5.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: garputhefork(a)gmail.com
Distribution: ---
Created attachment 68418
--> https://bugs.winehq.org/attachment.cgi?id=68418
backtrace of the Scrivener installer
With wine 5.19 (with staging), the Scrivener installer crashes. It worked with
5.18 and 5.16 (both staging) I haven't tried a non-staging build for 5.19. I
tested it in a clean prefix, as well. (Scrivener installer:
https://www.literatureandlatte.com/scrivenerforwindows/beta/Scrivener-29911…)
To my knowledge, nothing changed about the installer. (Scrivener, the
program, works fine on 5.19.)
--
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=48711
Bug ID: 48711
Summary: osu! crashes on dotnet452 when using built-in gdiplus:
System.ArgumentException: Font '?' cannot be found.
Product: Wine
Version: 5.3
Hardware: x86
URL: https://osu.ppy.sh/home/download
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: huupoke12(a)gmail.com
Distribution: ---
Created attachment 66583
--> https://bugs.winehq.org/attachment.cgi?id=66583
Terminal log of the crash on Wine 5.3 with dotnet452 installed
osu! crashes when running after installing dotnet452. I also tried dotnet45,
dotnet472, dotnet48 and it also crashes with the same error. But it doesn't
crash when using dotnet40 (I have created a new WINEPREFIX for each dotnet to
test that). This bug only happens when using default built-in gdiplus, since
installing Windows native gdiplus solved this bug. And I have tried rolling
back to previous Wine version and this bug maybe a regression since Wine 5.1,
the 5.0 release does not have this bug.
--
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=43409
Bug ID: 43409
Summary: Banished won't run on FreeBSD (failed to initialize
the memory allocator!)
Product: Wine
Version: 2.10
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adrien_fernandes2(a)hotmail.com
I'm running FreeBSD 11.0-RELEASE-p1 amd64 and I am using Wine staging 2.10
i386.
When I try to run Banished, I have a little window saying :
A fatal error has occured and the application cannot continue.
Memory: The application failed to initialize the memory allocator!
The only message I have in the terminal, after the usual "consider using
nouveau instead", is :
err:ole:CoUninitialize Mismatched CoUninitialize
I don't know if it is linked to my 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=40233
Bug ID: 40233
Summary: Devil Daggers Refuses to Start
Product: Wine
Version: 1.9.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tristanlshockley(a)gmail.com
Distribution: ---
Created attachment 53778
--> https://bugs.winehq.org/attachment.cgi?id=53778
Devil Dagger Force Close Output
I created a thread in the forums
(https://forum.winehq.org/viewtopic.php?f=8&t=26228) where I was recommended to
create a bug report. To get to this point I needed lib32-openal. After
installing samba a winbind error was removed (see the forum link) but this
doesn't appear to change anything. The game will not start through terminal
because of DRM, you need to run the game through Steam in WINE. When you do so
you will see a black box which will autoclose in about five seconds. Attached
is the text Steam spits out during this time, and if I can figure out how to
post another I will provide an image of the black box.
--
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=40928
Bug ID: 40928
Summary: Sword of the Stars: The Pit Gold Edition (.NET
4.0/XNA) crashes with a SIGSEGV when using wine-mono
Product: Wine
Version: 1.9.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fjfrackiewicz(a)gmail.com
Distribution: ---
Created attachment 55038
--> https://bugs.winehq.org/attachment.cgi?id=55038
Terminal output for Wine-1.9.13-114-gb1930ee Windows XP mode
Windows XP mode, clean 32-bit prefix.
After installing the GOG version of Sword of the Stars: The Pit Gold Edition
and running "wine ThePit.exe" I am greeted with what appears to be a wine-mono
crash.
Wine-mono 4.6.3 is installed.
--
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=40574
Bug ID: 40574
Summary: bbtalk.exe wont start
Product: Wine
Version: 1.9.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: eore26(a)gmail.com
Distribution: ---
Created attachment 54413
--> https://bugs.winehq.org/attachment.cgi?id=54413
Program error detail
Unhandled Exception
--
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=41919
Bug ID: 41919
Summary: Regression : impossible to finish installation of
Indiana Jones The Original Trilogy
Product: Wine
Version: 1.9.24
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fevrier.simon(a)gmail.com
Distribution: Ubuntu
Ubuntu 16.10
It seems the regression appear between Wine 1.7.18 and 1.7.29.
Normally, no problem
Regression : a pop up window say "Insert the disk : 1" but the disk is inserted
Nothing different between versions in the poor logs.
The regression page say to test with the latest code. I will try but I don't
think it will be useful. For a "git bisect" method : too expensive for my
computer, but I will try to have a look at the commits' information.
It doesn't work In wine 1.9.24.
--
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=47801
Bug ID: 47801
Summary: Growing build/wine VM disk usage
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: ---
Created attachment 65291
--> https://bugs.winehq.org/attachment.cgi?id=65291
Evolution of wtbdebian10's revert times
Every time we update and rebuild Wine in these VMs the VM's qcow2 file grows.
The Wine VMs are those where the disk grows fastest, from ~5 GB to 60+ GB in a
matter of weeks. Fortunately it does seem to grow slower after a while.
For instance <6 GB to 32 GB (du) from 2019-09-20 to 2019-09-25 for wtbdebian10.
This may be caused by the way WineRunReconfig handles live snapshots. To
summarize:
* Restore to the current live snapshot.
* Update and rebuild Wine.
* Iff that succeeded, delete the live snapshot and recreate it.
This may cause QEmu to not realize that all the data from the now deleted old
live snapshot can be reclaimed and reused for the next Wine build. But we had
to delete the live snapshot at the last minute because losing it would mean the
VM would be unusable until the TestBot administrator could come and fix it.
However nowadays the TestBot can recreate live snapshots from powered off
snapshots. This means we could delete the live snapshot first, rebuild and
recreate the snapshot at the end. In the unlikely event that something goes
wrong the live snapshot could be recreated from the powered off 'base'...
except in the case of a build error. That case would be unrecoverable unlike in
the current scheme.
A test with this alternative snapshot management should be made to see if it
does actually make a difference in the qcow2 growth (there's really no
guarantee it does).
For these VMs the revert time does seem to degrade a bit with time(*). This may
be related to the qcow2 size and/or accumulation of "phantom snapshots". So the
experiment should be run for a while to see if it makes a difference on this
metric too.
(*) See the Munin graph of wtbdebian10's revert time. The drop in week 38 and
39 correspond to maintenance on the VM where all snapshots were deleted and
virt-sparsify run on its disk.
--
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=48787
Bug ID: 48787
Summary: WineD3D C&C Generals Zero Hour takes a lot time to
load or maximize
Product: vkd3d
Version: 1.1
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: moceap(a)hotmail.com
As you know (C&C Generals Zero Hour) is an old game. And it use DirectX 8.1.
These type of games don't stable in current Windows' versions.
So WineD3D used to valid run them on Windows.
Using: C&C Generals Zero Hour (Last Version 1.04)
Windows 10 (1909)
WineD3D (From Wine 5.4)https://fdossena.com/?p=wined3d/index.frag
Both (Intel and AMD) cards tested
Expected Result: Works fine with high speed.
Actual Result: Very long time on maximize the game after minimize or switch to
another application
Long time on loading the game (Not happen on MS DirectX)
--
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.