http://bugs.winehq.org/show_bug.cgi?id=23478
Summary: moneysoft accounts programs do not close files when
they should
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andygibbs1(a)compuserve.com
I am trying to use two linked accounting programs that are from Moneysoft. I've
used them on windoze for years and they are the last thing keeping locked to
that os!
SORRY IF THIS SOUNDS LONG WINDED! So far I have tried the two packages, Money
Manager and Final Accounts on two machines and had the same problem. Machine 1
is an old evo 800 running xubuntu with wine 1.1.31. The second is an HP wx6200
workstation, 2 cpu's with dual cores and 4gb running fedora 13 and wine 1.1.38
loaded from the fedora repository.
When running the programs it should be possible to jump from one years data
file to say the last year's and by using "file-open" and selecting the other
year. when doing that the program should automatically close and release the
first file, and its not. In the file to open selection box is a list of the
possible files and under normal operation with a file open, clicking on the
"file"-"open" will show the list and have "open" next to the one in use. This
still happens, but if you select another and look at it then go back to the
"file"-"open" selection it shows that one as being open and the last as being
"in use".
The help says this could be if its on a network and only one operator can use
it at a time, so the file must be tagged in some way and that tag is not being
released.
ANY IDEAS PLEASE?
--
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=39572
Bug ID: 39572
Summary: Fallout 4: won't start
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: eighthkeepa(a)gmail.com
Distribution: ---
Created attachment 52726
--> https://bugs.winehq.org/attachment.cgi?id=52726
Game's startup.
Fallout 4 won't start
Steam-version of Fallout 4 won't start because of DX11, which is not
implemented in wine yet. Hovewer, it seems like game is trying to load some
resources in background, so it's possible that dx11 is the only problem, which
prevents from running it with wine.
Devs set DX11 as default renderer, without any possibility to choose other
dx-versions from settings, which is quite unfortunate.
See the backtrace below.
WINE version: 1.7.43 (64bit) (also tried to start the game on version 1.7.54,
but failed)
PC Specs: i7-4770, nvidia GTX 650Ti, 16RAM.
--
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=33170
Bug #: 33170
Summary: Sid mayers Alpha Centauri crashes at start
Product: Wine
Version: 1.5.25
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: macmolder(a)gmail.com
Classification: Unclassified
Created attachment 43881
--> http://bugs.winehq.org/attachment.cgi?id=43881
Backtrace of crash
Crashes immediatelly on the start
--
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.
http://bugs.winehq.org/show_bug.cgi?id=28890
Bug #: 28890
Summary: Kanon sometimes freezes after a choice is made
Product: Wine
Version: 1.3.30
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winebugzilla.kyoo(a)xoxy.net
Classification: Unclassified
Created attachment 37117
--> http://bugs.winehq.org/attachment.cgi?id=37117
Wine output when running kanon. Last lines appear with freeze.
Kanon http://appdb.winehq.org/objectManager.php?sClass=version&iId=12764 will
sometimes freeze after a choice is made. The next dialog bit is shown, but
when the user clicks to advance, the freeze happens. Attached is the command
line output, the last few lines of which only appear when the freeze happens.
"err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 002f, blocked by 0029, retrying (60 sec)" will repeat indefinitely
until I kill the program.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=24539
Summary: Dystopia 1.3 renders a black menu background when
launched in -dxlevel 90 mode
Product: Wine
Version: 1.3.3
Platform: x86
URL: http://store.steampowered.com/app/17580/
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
Created an attachment (id=30968)
--> (http://bugs.winehq.org/attachment.cgi?id=30968)
Dystopia 1.3 debug output
With wine-1.3.3-234-g57a6404, launching Dystopia yields a completely black
background in the menu, rather than some sort of graphical drawing. Launching
the game in -dxlevel 81 and lower makes the background appear, however.
Note that I've disabled mmdevapi, which is visible in the log, due to another
issue with Dystopia for a separate bug report, and Dystopia is freely available
for owners of Half-Life 2, in case testing is warranted.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=19698
Summary: Hearts of Iron III Demo crashes due to unhandled page
fault on write access
Product: Wine
Version: 1.1.27
Platform: PC
URL: http://www.paradoxplaza.com//index.php?option=com_cont
ent&task=view&id=442&Itemid=234
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: daniel.spies(a)fuceekay.com
Created an attachment (id=22997)
--> (http://bugs.winehq.org/attachment.cgi?id=22997)
Crashlog (page fault)
Hearts of Iron III Demo crashes due to unhandled page fault on write access
after some minutes or up to two hours of gameplay. It's not caused by a special
action in game. I cannot test this on the full version, I don't have one yet.
See the crash log attached.
Tested on
- Kubuntu 9.04 x86_64
- ATi hd2600xt
Demo download:
http://www.hoi3.com/index.php?option=com_content&view=article&id=123:demo-d…
--
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=38304
Bug ID: 38304
Summary: Genesis Rising crashes when loading a saved game
Product: Wine
Version: 1.7.29
Hardware: x86
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: matellanesivan(a)gmail.com
Regression SHA1: 5077d8c1371fe3e8e263119a6cc05d0e9766cdba
Distribution: ---
Created attachment 51138
--> https://bugs.winehq.org/attachment.cgi?id=51138
terminal output
The game has an auto-save feature, it saves games between each mission (no
manual save available).
Saving the game works properly, but the game crashes when I try to load a
previously saved game.
Native msvcr80.dll is a workaround (winetricks vcrun2005).
Loading a saved game used to work in Wine 1.7.28, this is a regression
introduced by
5077d8c1371fe3e8e263119a6cc05d0e9766cdba is the first bad commit
commit 5077d8c1371fe3e8e263119a6cc05d0e9766cdba
Author: Iván Matellanes <matellanesivan(a)gmail.com>
Date: Wed Oct 15 16:47:07 2014 +0200
msvcrt: Added _fseeki64_nolock implementation.
wine-1.7.39-173-gf6a341c
--
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=35008
Bug #: 35008
Summary: Dragon NaturallySpeaking 12.0
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: l_rivers(a)efn.org
Classification: Unclassified
Created attachment 46656
--> http://bugs.winehq.org/attachment.cgi?id=46656
backtrace
Greetings. I run ubuntu 13.10 on a ThinkPad-T61 with 2.9 GIB memory, an Intel
Core 2 Duo CPU T770(a)2.40GHz*2 and a Graphics Quadro NVS 140/PCie/SSE2 with OS
type 32-Bit all on a 154.2 GB Disk.
My goal is to get Dragon NaturallySpeaking 12.0 going! WINE installs the
Windows-XP version no-problem,... but maybe one little SNAFU. I launch my
Dragon NaturallySpeaking and get a failure with this error message:
"Cannot find the file 'C.\windows\speech.dll"
Please advise
Leo
PS: These bugs don't look like mine.
15708 nor P2 Linu wine-bugs(a)winehq.org UNCO ---
Dragon NaturallySpeaking 7 install fails with negative amount of memory
reported
32142 nor P2 Linu wine-bugs(a)winehq.org UNCO ---
Ability to run Nuance Dragon Naturally Speaking 11.5 broke with wine 1.5.13
34939 nor P2 Linu wine-bugs(a)winehq.org UNCO ---
Dragon NaturallySpeaking does not install in 64-bit version
--
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.
http://bugs.winehq.org/show_bug.cgi?id=34788
Bug #: 34788
Summary: Incorrect behaviour when maximizing undecorated
windows
Product: Wine
Version: 1.7.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: medasaro(a)comcast.net
Classification: Unclassified
Created attachment 46390
--> http://bugs.winehq.org/attachment.cgi?id=46390
This image compares a maximized Notepad window in Wine and XP
When a window is maximized in Microsoft Windows, the grey border around the
window goes away. However, when undecorated windows (or skinned windows like
iTunes) are maximized in wine, the grey border remains.
Steps to reproduce:
1) Open winecfg and deselect the 'Allow the window manager to decorate the
windows' option in the 'Graphics' tab.
2) Close winecfg.
3) Open notepad
4) Maximize the notepad window
5) Note that there is still a grey border around the edges of the entire window
which is not present when running the application in windows.
Please see the attached screenshot
--
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.
http://bugs.winehq.org/show_bug.cgi?id=33686
Bug #: 33686
Summary: Diablo III: Audio cuts out after a while of game play
Product: Wine
Version: 1.5.31
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winealsa.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kdt3rd(a)gmail.com
Classification: Unclassified
After a semi-random amount of time playing the game, the audio all of a sudden
stops outputting anything. I am not running pulse or any sound daemon, just
using alsa with the output device hard-specified in winecfg.
After trying to trace with the Audio wiki-recommended WINEDEBUG settings, I
didn't get very far trying to isolate the problem, so I modified the TRACE in
dlls/winealsa.drv/mmdevdrv.c, and when the audio cuts out, it looks like the
AudioClient_GetCurrentPadding is called in-between or just slightly one (wrong)
side of alsa_write_data, which causes a larger number to be returned than
'normal'. At this point, a lot of the
AudioRenderClient_(GetBuffer|ReleaseBuffer) calls start requesting 0 frames.
But more importantly, something about that sequence getting out of the normal
thread sequence triggers the pad stored in 'in_alsa' in alsa_write_data to
become larger than max_period * 3 size. This means that write_limit ends up
stuck at 0, so it leaves the alsa_write_data function early and no audio is
output...
I write this bug because it seems like the code that is implementing the
comment about keeping 3 ALSA/MMDevAPI periods in the ALSA buffer is either
flawed, or more likely, I don't understand all the pieces, so I'm not sure how
to make a patch to appropriately fix the issue. Any hints on potential patches
are appreciated.
--
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.