http://bugs.winehq.org/show_bug.cgi?id=10462
Summary: Vokabeltraier 3 ratail storage/space test of
installation crashes
Product: Wine
Version: 0.9.49.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thomas(a)haeber.de
In the installation dialoge of the ratail version of Vokabeltrainer 3 is the
option to calculate the space for installation. If you start this test wine
crashes.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10043
Summary: Babas Chess version 3.6
Product: Wine
Version: 0.9.46.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: test
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mikos(a)esc.net.au
With wine version 0.9.46 all chat produces an "application error" message box
(does not quit application, only stops messages being sent).
Steps to reproduce: type "tell %USERNAME% message" or type in chat window when
playing.
This did NOT occur with wine versions 0.9.45 and previous.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9720
Summary: deadzone regression on eventX input devices
Product: Wine
Version: 0.9.45.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: geraldf2(a)free.fr
I don't know exactly with which Wine version this has been introduced
since I jumped from 0.9.42 to 0.9.45, so this may be in-between.
Previously (e.g with 0.9.42) there was no default deadzone using a
'/dev/input/eventX' input device (joystick/wheel), which was good. It
was similar to the behavior on MS-Windows (at least according to my
experience).
Now with Wine 0.9.45 there is a default deadzone which is really bad,
it effectively render my controller unusable. It is especially bad
with a driving wheel controller (really really bad), but it's bad even
with an analog stick joypad (I started using /dev/input/eventX instead
of /dev/input/js0 just because of that when I used such a pad). To be
honest I wonder why someone would even want a deadzone on his
joystick, it renders any fine control impossible.
If there is a way to turn off the deadzone (except from modifying the
source code) please someone tell me, but if it exists it should be
easily accessible (like in the winecfg utility) and turned off by
default (if only to reflect MS-Windows behavior).
Please tell me if you intend to keep this default deadzone anyway, so
that I know I'll have to edit Wine's source code every time I upgrade,
it's not a problem for me since I already have to do that to get force
feedback working anyway but I would be very sorry for the common folks
that just want to play.
Thanks for reading.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9651
Summary: MsiError 259 when installing LabVIEW
Product: Wine
Version: 0.9.44.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: wine-msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: john_re(a)fastmail.us
NationalInstruments LabView install from cd,
Installer loads, proceeds to about 5% progress, then gets this error:
"Fatal Error. Unhandled MSI Error"
"MsiError 259: <Unable to format error record.>"
Severity - the sw won't install - install fails.
wine 0.9.44 from wine depository. KUbuntu Fiesty 07.04
upon suggestion from wine IRC I did in ~ "mv .wine .wine.old" then redid the
install attempt - still same exact error.
MSI = MS Installer?
Labview xtra 8.2
"NI LabVIEW 8.2"
"Fatal Error. Unhandled MSI Error"
"MsiError 259: <Unable to format error record.>"
"Unhandled MSI Error"
http://www.google.com/search?q=%22Unhandled+MSI+Error%22&ie=utf-8&oe=utf-8&…
"Msi Error 259"
http://www.google.com/search?hl=en&client=firefox-a&rls=com.ubuntu:en-US:of…
Help please. Thanks. :)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10364
Summary: My Horse and Me Demo Installer shows product name wrong
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ead1234(a)hotmail.com
Created an attachment (id=9035)
--> (http://bugs.winehq.org/attachment.cgi?id=9035)
picture of error
In the installation of My Horse and Me Demo, the product name shows up in
brackets as <ifx_product_name> in the dialog box
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10379
Summary: unhandled page fault on first attempt to use help viewer
Product: Wine
Version: 0.9.49.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-shdocvw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rm.riches(a)verizon.net
This appears to be a regression from 0.9.48 to 0.9.49. Symptoms are very
similar to old fixed bug #8077 and not-as-old fixed bug #8851. An unhandled
page fault happens immediately after installing Wine Gecko.
Application is PAF (Personal Ancestral File) 5. Application installation
appeared to go well, and basic application functionality appears okay. Wine
Gecko appears to install, but immediately after installing, or right after
clicking on the yellow question mark "help" icon, an unhandled page fault
happens.
I plan to attach the output with debug channels enabled from bug #8851.
If/when I can make time to do it, I also plan to run a git regression.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8930
James Hawkins <truiken(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #16 from James Hawkins <truiken(a)gmail.com> 2007-11-30 16:52:32 ---
This should be fixed in 0.9.50. Please reopen if that's not the case.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7065
Hans Leidekker <hans(a)it.vu.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hans(a)it.vu.nl
--- Comment #57 from Hans Leidekker <hans(a)it.vu.nl> 2007-11-30 15:10:30 ---
Just to add to the knowledge gathered here, I found that when you
call SetVolumeMountPoint("X:\\", "\\?\Volume{<GUID>}"), registry value
\DosDevices\X: is added to the MountedDevices key:
[HKEY_LOCAL_MACHINE\System\MountedDevices]
\??\Volume{<GUID>} = <...>
\DosDevices\X: = <...>
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=2082
--- Comment #35 from Stefan Dösinger <stefandoesinger(a)gmx.at> 2007-11-30 14:53:52 ---
Regarding the status, that is just a bugzilla category. A new bug is
"UNCONFIRMED", when people confirm it it becomes "NEW". The next step is
"RESOLVED" - with various reasons, e.g. FIXED, WONTFIX, ABANDONED, ..., after
that CLOSED. So "NEW" doesn't mean that the bug isn't older than $DAYS. The
"NEW" is what you mean with confirmed propably.
As far as fixing this bug is concerned, an open source project isn't something
where you can drop in and order something to be done. Possible reasons why this
bug isn't fixed could be
a) None of the developer has personal or commercial interest in the specific
games
b) None of the developers has time to fix it. Remember, many are working on
Wine in their free time.
c) No volunteer got around to fix it yet(as everyone only demands that it gets
fixed)
d) The bug is harder to fix than the simple workaround suggests. There might
even be architectural differences between Windows and X11 which make it
impossible to fix correctly.
In case of this bug, it's a combination of all 3 issues.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=2082
--- Comment #34 from Claudio <sick_soul(a)yahoo.it> 2007-11-30 14:41:58 ---
I had the same issue with Diablo, voting this bug.
The 'render to desktop' workaround worked, but I'd like to say,
the state of the bug is not 'new'.
After three years, why don't you change the state to confirmed,
and eventually start to implement a fix in the main wine?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.