https://bugs.winehq.org/show_bug.cgi?id=38214
Bug ID: 38214
Summary: Load Game function of Airport Tycoon 3 is broken.
Product: Wine
Version: 0.9.4.
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 2001kraft(a)gmail.com
Created attachment 51005
--> https://bugs.winehq.org/attachment.cgi?id=51005
at3 bug report
Was using Airport Tycoon 3 and running directly using Wine. Then clicked
"Load". Then clicked on one of my saves, the app crashed. Same happens with any
save, meaning that the "Load" function is broken.
--
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=41644
Bug ID: 41644
Summary: Civilization v1.2: crashes on startup
Product: Wine
Version: 1.9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: K_ThaaL(a)bk.ru
Distribution: ---
Created attachment 56018
--> https://bugs.winehq.org/attachment.cgi?id=56018
trace generated by wine
Wine crashes right after the first frame of game intro is shown.
Created a new 32bit wine prefix for this game.
Tried windows versions XP and 3.1 - behavior is the same in both cases.
Using virtual desktop and disallowing window decorations did not help.
No other options tried.
Ubuntu 16.04 LTS is used with Wine installed from winehq repository.
Problem is detected on 1.9.21 and 1.9.22.
--
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=45391
Bug ID: 45391
Summary: winehq.org is distributing compiled LGPL code packages
but withholding their sources
Product: Packaging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: forestcode(a)ixio.org
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
The source code tarballs and package build scripts for winehq's ubuntu and
debian packages are not published. They are not where they are supposed to be
according to the official debian/ubuntu sources.list file (the deb-src entry
that gets created when someone follows the official apt-add-repository
instructions), they don't seem to be referenced anywhere else obvious, and
nobody at the wine project has been forthcoming about how to get them.
[1][2][3]
So, winehq.org is distributing binary packages without making their sources
available. This makes it impossible for the people using those packages to
audit the code, reproduce the packages, test patches on known-good packaged
versions, or port them to different OS releases (the latter leading to issues
like bug 45085).
>From what I can tell, this is also likely an LGPL violation:
"4. You may copy and distribute the Library (or a portion or derivative of it,
under Section 2) in object code or executable form under the terms of Sections
1 and 2 above provided that you accompany it with the complete corresponding
machine-readable source code"
What will it take to remedy this situation?
[1] Notice the absence of an answer in this thread:
https://www.winehq.org/pipermail/wine-devel/2018-May/127507.html
[2] Nobody had an answer for me on the two occasions when I asked on
#winehackers irc this week.
[3] Nobody responded when I emailed the package maintainers listed at
https://wiki.winehq.org/Download
--
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=42908
Bug ID: 42908
Summary: Monopoly (2000) crashes on launch
Product: Wine
Version: 2.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Created attachment 58049
--> https://bugs.winehq.org/attachment.cgi?id=58049
backtrace
Crashes trying to read 0x0000000. 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=45936
Bug ID: 45936
Summary: IW4x crashes on keyboard input
Product: Wine-staging
Version: 3.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: huematrix(a)mailinator.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 62464
--> https://bugs.winehq.org/attachment.cgi?id=62464
Log
Upon pressing a key in IW4x (A Call of Duty: Modern Warfare 2 client), the
program crashes. Full log below.
--
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=48560
Bug ID: 48560
Summary: Default color scheme
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: depositmail(a)mail.ru
Distribution: ---
Created attachment 66374
--> https://bugs.winehq.org/attachment.cgi?id=66374
Breeze color scheme
Good afternoon!
Is it possible to make the default "Breeze" color scheme in Wine?
(Files are attached).
Link to the resource:
https://store.kde.org/p/1259774/
--
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=39415
Bug ID: 39415
Summary: Make configuration settings accessible through the
website
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: ---
Currently the way to change a configuration setting is to send a patch to
wine-patches and have Alexandre apply it. This is the case for instance for all
the VM host configuration settings ($MaxRevertingVMs,
$MaxRevertsWhileRunningVMs, etc.), but also $JobPurgeDays, $RegistrationQ, etc.
This is not very practical and prevents experimentation or quickly adjusting
the settings when a problem arises.
Instead these should be stored in a Parameters table and be accessible through
an administrator-only section of the website.
--
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=39416
Bug ID: 39416
Summary: Many settings should be per VM host
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: ---
The following global settings should in fact be customizable on a per VM host
basis:
* $MaxRevertingVMs - Hosts with SSDs may be able to handle multiple reverts in
parallel.
* $MaxRevertsWhileRunningVMs - Again this may depend on disk speed and QEmu
version.
* $MaxActiveVMs - Depends on disk and CPU speed, number of cores, etc.
* $SuiteTimeout & $SingleTimeout - Might need to be adjusted based on the CPU
speed.
* $BuildTimeout & $ReconfigTimeout - Might need to be adjusted based on the CPU
speed. Fortunately we can currently only have one build VM so that's not too
much of an issue.
One way to do so would be to introduce a VMHosts table storing the settings for
each VM host (see the schema attachment of bug 39412). VMs (VMInstances really)
would then be linked to the relevant VM host so to indicate which set of
constraints apply.
Note that this would be different from the handling of the truly global
settings described in bug 39415.
--
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=34666
Bug #: 34666
Summary: In The Adventures Of Lomax some graphic elements
flicker, disappear or are garbled
Product: Wine
Version: 1.7.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winebugs140(a)gmail.com
Classification: Unclassified
Created attachment 46209
--> http://bugs.winehq.org/attachment.cgi?id=46209
Lomax Log
For example there is no transition between the main game screen and the next
one. I mean, the black screen is displayed instead of a transition.
The screen where you see Lomax and Evil Ed standing next to each other is
garbled.
When you begin the game the text message 'Let's go' flickers. There is also
flickering when you press the space key to change your hat.
The issues can be reproduced in the demo (check out the link).
Tested with:
Windows Vista (without Wine), GeForce 9600M GS--the program works fine here
Ubuntu 13.04, GeForce 9600M GS (NVIDIA driver 313)
--
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=47833
Bug ID: 47833
Summary: FindFirstFileExW seems to be missing
FILE_OPEN_FOR_BACKUP_INTENT flag to NtOpenFile
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: qsniyg(a)mail.com
Distribution: ---
When running USVFS (through ModOrganizer 2), its hooked version of NtOpenFile
checks for the FILE_OPEN_FOR_BACKUP_INTENT flag to see if the function calling
it is FindFirstFileExW.
Under Windows, this apparently works as expected, but wine doesn't pass the
flag, causing USVFS to fail injecting directory listings. Adding the flag
allows USVFS to work properly.
I haven't tested this under windows, so I have no way to verify if the flag
only gets set for some arguments sent to FindFirstFileExW and not others, but
since USVFS has been known to work for many different programs, I would
personally assume that the flag is always set.
--
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.