http://bugs.winehq.org/show_bug.cgi?id=14604
Summary: Fire Fight: Unhandled page fault crash upon startup
Product: Wine
Version: 1.1.1
Platform: PC
URL: http://files.filefront.com/ffsw10exe/;6981503;/fileinfo.
html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: drakh(a)spamcop.net
Fire Fight shareware version 1.0 crashes with an unhandled page fault upon
running the game's setup/launcher application "LOADER.EXE". The application's
runtime log ends with the error "unable to hook keyboard [Kbd::init]".
--
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=14275
Summary: Kontakt 3 fails at startup
Product: Wine
Version: 1.1.0
Platform: PC
URL: http://www.native-instruments.com/index.php?id=kontakt3
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: skore(a)skore.de
Created an attachment (id=14566)
--> (http://bugs.winehq.org/attachment.cgi?id=14566)
An error trace from a Kontakt 3 startup
I will attach an error trace which should be of most help, but have to add
here, that I actually tested the demo version of Kontakt 3 before buying it.
Back then, there were some quirks, but it was starting. I think the wine
version might have been something like 0.9.59. However, when I try to start the
demo version with 1.0 or 1.1, it fails.
--
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=19644
Summary: Grim Fandango 1.01:crash at startup
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: t0p0linik(a)yahoo.it
Created an attachment (id=22926)
--> (http://bugs.winehq.org/attachment.cgi?id=22926)
wine log for the crash of GF 1.01
The subject explains the issue, i'm still unable to install the game due to bug
18223 but i'm running a working copy of an old successful install.
Wine log is attached.
--
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=17229
Summary: TGB Dual crashes when opening files
Product: Wine
Version: 1.1.14
Platform: PC
URL: http://appdb.winehq.org/objectManager.php?sClass=applica
tion&iId=6468
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: madewokherd(a)gmail.com
TGB Dual crashes when attempting to open any file. To reproduce, select the
first item in the left-most menu and choose a file (it does not have to be a
rom).
--
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=18064
Summary: Lotus Notes 8.5 Installer aborts
Product: Wine
Version: unspecified
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dunerkahl(a)yahoo.de
Created an attachment (id=20464)
--> (http://bugs.winehq.org/attachment.cgi?id=20464)
winedebug +msi trace
Lotus Notes 8.5 doesn't install, the installer aborts with following MSI error:
err:msi:ITERATE_Actions Execution halted, action
L"SetDefaultProps.5F3129E8_3AD4_4346_AEE6_A314E2DE64D9" returned 1603
I've added a backtrace with debug channel 'msi' enabled.
--
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=20568
Summary: Exception EExternalException...
Product: Wine
Version: 1.1.32
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P5
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hormold(a)gmail.com
Created an attachment (id=24535)
--> (http://bugs.winehq.org/attachment.cgi?id=24535)
log
I can't start Natura Sound Therapy 3.0 (Ubuntu 8.04 Hardy).
Error message box:
"Exception EExternalException in module ntdll.dll at 0002CC48.
External extension in C0000025.
"
Please HELP!
Sorry for my bad english...
--
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=20336
Summary: GetDriveTypeW exposes partially uninitialized out
parameter iosb in NtDeviceIoControlFile ?
Product: Wine
Version: 1.1.31
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: download, patch
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Building the chromium unit test suite and then running
valgrind --trace-children=all --track-origins=yes wine base_unittests.exe
--gtest_filter=FileUtilTest.CreateShortcutTest
sometimes yields the error
Syscall param writev(vector[...]) points to uninitialised byte(s)
at writev (writev.c:46)
by wine_server_call (server.c:214)
by NTDLL_wait_for_multiple_objects (sync.c:1122)
by NtWaitForMultipleObjects (sync.c:1166)
by NtWaitForSingleObject (sync.c:1175)
by server_ioctl_file (file.c:1252)
by NtDeviceIoControlFile (file.c:1318)
by DeviceIoControl (file.c:2379)
by get_mountmgr_drive_type (volume.c:203)
by GetDriveTypeW (volume.c:1381)
by IShellLinkW_fnSetPath (shelllink.c:2155)
...
Address 0x7f21f248 is on thread 1's stack
Uninitialised value was created by a stack allocation
at DeviceIoControl (file.c:2335)
and sometimes the error
Syscall param writev(vector[...]) points to uninitialised byte(s)
at writev (writev.c:46)
by wine_server_call (server.c:214)
by NTDLL_wait_for_multiple_objects (sync.c:1122)
by wait_suspend (exception.c:85)
by usr1_handler (signal_i386.c:1993)
by ??? (in /lib32/libpthread-2.9.so)
Address 0x7ffdae08 is on thread 1's stack
Uninitialised value was created by a stack allocation
at DeviceIoControl (file.c:2335)
The stack allocation in question is
IO_STATUS_BLOCK iosb;
in kernel32/file.c in DeviceIoControl(). Setting its fields
to known values before the call to NtDeviceIoControlFile()
shows that the undefined field is iosb.Information.
Setting that field before the call gets rid of the valgrind error.
I can't quite follow how ioctl's work, but:
the IOCTL_MOUNTMGR_QUERY_UNIX_DRIVE ioctl seems
to follow the call-once-to-get-buffer-size paradigm.
Its reply is a struct mountmgr_unix_drive plus
(if there is room) two nul-terminated strings.
The first field of that struct is the total size needed
to hold the entire reply. If you call without a
big enough buffer, it fills in the size and returns
STATUS_MORE_ENTRIES. It puts 0 in the Information field
of the iosb in this case.
GetDriveTypeW happens to not care about the two strings,
so it only calls once with a small buffer.
Now, server_ioctl_file only copies the Information field
of the iosb if it gets STATUS_SUCCESS. So it leaves
Information undefined in the STATUS_MORE_ENTRIES case.
MSDN says that Information is set to zero on failure,
so if server_ioctl_file isn't going to copy that field,
maybe it should set it to zero. And in fact, setting
it to zero in the non-STATUS_SUCCESS case also gets
rid of the valgrind error.
I have no idea what Information is used for, or what's
really going on here, so I'll just attach the patch
to clear Information in the non-SUCCESS case and
hope somebody who knows what's going on can comment.
--
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=9667
Summary: Grim Fandango hangs if X in 24bpp mode
Product: Wine
Version: 0.9.45.
Platform: PC
URL: http://www.grimfandango.net/?page=demo
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-x11driver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: a.hurst(a)shef.ac.uk
Grim Fandango works well if X is started with 16-bit colour depth.
If started with 24-bit colour, it hangs before the intro video (disc 1) or the
game engine start (disc 2).
--
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=19151
Summary: Spotify crashes in the mittle of a song and give me a
pop-up fault message
Product: Wine
Version: 1.1.24
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tobias.bjork(a)gmail.com
Created an attachment (id=22140)
--> (http://bugs.winehq.org/attachment.cgi?id=22140)
Screen shot, pop-up message
I use:
Ubuntu 9.04 - the Jaunty Jackalope
Spotify 0.9.17
Spotify crash with different time interwalls (sometimes I can listen for hours
and sometimes just a couple of songs). No matter if I start wine & spotify
using the Applications"-menu or if I start it in a console. A pop-up message
appears that suggest to visit your site and learn how to use the application or
to create a bug report
I attach a screen shot and the fault message from the console
--
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.