http://bugs.winehq.org/show_bug.cgi?id=4254
------- Additional Comments From wawrzek(a)gmail.com 2006-13-01 12:40 -------
I tried once more.
This time installation process freeze. The last lines of
WINEDEBUG=relay wine ./setup.exe
000b:Call
ntdll.NtQueryInformationFile(00000074,7f9ecfb0,7f9ecfb8,00000008,0000000e)
ret=7fc7743f
000b:Ret ntdll.NtQueryInformationFile() retval=00000000 ret=7fc7743f
000b:Call
ntdll.NtSetInformationFile(00000074,7f9ecfb0,7f9ecfa8,00000008,00000014)
ret=7fc77462
000b:Ret ntdll.NtSetInformationFile() retval=00000000 ret=7fc77462
000b:Ret kernel32.SetEndOfFile() retval=00000001 ret=7f6dd9ae
000b:Call
kernel32.CreateFileMappingA(00000074,00000000,00000004,00000000,00000000,00000000)
ret=7f6dd9c1
000b:Call
ntdll.NtCreateSection(7f9ecd1c,000f0007,7f9ecd30,7f9ecd20,00000004,08000000,00000074)
ret=7fcaef77
000b:Ret ntdll.NtCreateSection() retval=00000000 ret=7fcaef77
000b:Call ntdll.RtlNtStatusToDosError(00000000) ret=7fcaef8b
000b:Ret ntdll.RtlNtStatusToDosError() retval=00000000 ret=7fcaef8b
000b:Ret kernel32.CreateFileMappingA() retval=00000084 ret=7f6dd9c1
000b:Call kernel32.MapViewOfFile(00000084,00000002,00000000,00000000,00008c00)
ret=7f6dd32a
000b:Call
ntdll.NtMapViewOfSection(00000084,ffffffff,7f9ecf74,00000000,00000000,7f9ecf50,7f9ecf70,00000001,00000000,00000004)
ret=7fcaf19b
000b:Ret ntdll.NtMapViewOfSection() retval=00000000 ret=7fcaf19b
000b:Ret kernel32.MapViewOfFile() retval=7c0e0000 ret=7f6dd32a
000b:Call ntdll.RtlAllocateHeap(7fd30000,00000000,00000040) ret=7f6e63c1
000b:Ret ntdll.RtlAllocateHeap() retval=7fe373c8 ret=7f6e63c1
I have very similar sitation with another Paradox game Victoria. It freezes in
the same way, morover, the last line of dubug are neraly the same, the only
different is this line:
< 000b:Ret ntdll.RtlAllocateHeap() retval=7fe373c8 ret=7f6e63c1
---
> 000b:Ret ntdll.RtlAllocateHeap() retval=7fe32920 ret=7f6e63c1
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4297
Summary: err:keyboard:X11DRV_ToUnicodeEx
Product: Wine
Version: 0.9.5.
Platform: Other
URL: ftp://ftp.westwood.com/pub/redalert/previews/demo
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-x11driver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alex(a)thehandofagony.com
When playing the demo of Command & Conquer: Red Alert, several messages like
this apear on the console
err:keyboard:X11DRV_ToUnicodeEx (virtKey=0,scanCode=0,keycode=8,state=0)
err:keyboard:X11DRV_ToUnicodeEx Please report: no char for keysym 0000 (No
Name) :
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4296
------- Additional Comments From marcus(a)jet.franken.de 2006-13-01 11:29 -------
what app is this?
can you run with
WINEDEBUG=+relay,+seh wine foo.exe
and check the last instructions,
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4296
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |regression
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3549
burnus(a)gmx.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From burnus(a)gmx.de 2006-13-01 11:15 -------
Works fine.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=4296
Summary: Printing crashes wine (stack overflow)
Product: Wine
Version: 20050930
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: junkmail(a)eighteyes.com
When trying to print from an application in wine, wine crashes with a stack
overflow message. Printing used to work a few versions ago (can't remember which
version, though).
When setting up the printer, it displays CUPSs list of printers.
Here are the last few error messages (the rest are similar):
The memory could not be read fromAn privileged instruction was executed at
address 7fb33ae0The instruction at 7ffc0d2b referenced memory at 00000006
The memory could not be read fromAn privileged instruction was executed at
address 7fb33330The instruction at 7ffc0d2b referenced memory at 00000006
The memory could not be read fromAn privileged instruction was executed at
address 7fb32b80The instruction at 7ffc0d2b referenced memory at 00000006
The memory could not be read fromAn privileged instruction was executed at
address 7fb323d0The instruction at 7ffc0d2b referenced memory at 00000006
The memory could not be read fromerr:seh:setup_exception stack overflow 504
bytes in thread 0009 eip b7e0389e esp 7fb30e08 stack 0x7fb30000-0x7fc30000
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4263
------- Additional Comments From alex(a)thehandofagony.com 2006-13-01 10:06 -------
I apologize for my last comment; there are no changes, I simply forgot to run
'cvswine' instead of 'wine'.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4263
------- Additional Comments From alex(a)thehandofagony.com 2006-13-01 10:05 -------
With current CVS it behaves like Wine 0.9.4 and 0.9.5 again; freezing when
InstallShield is preparing the installation wizard.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4268
------- Additional Comments From michal.okresa(a)ifne.sk 2006-13-01 09:43 -------
Hello,
we are trying to find solution for the ISS printing. We are using 'alien' test
machine mentioned by the bug reporter Peto. So, on this machine is installed
wine 20050310 - original Debian Sarge installation. For printing tests we are
using: "virtual printer" configured in CUPS as: Device URI:
socket://localhost:12000, name: to_file. Print requests is handled via simple
port listener in Perl. Additional printers are scx4100 and xerox_230.
The printer 'xerox_230' is default.
When we tried to print on the 'xerox_230' from ISS, this messages are shown in logs:
trace:winspool:GetDefaultPrinterW L"xerox_230,WINEPS,LPR:xerox_230"
trace:winspool:GetDefaultPrinterA 0x0000000a/0x00000104:L"xerox_230"
trace:winspool:OpenPrinterW (printerName: L" xerox_230", pDefault (nil))
trace:winspool:OpenPrinterW Can't find printer L" xerox_230" in registry
As you can see, printer name is " xerox_230" not "xerox_230". This name(with
space) is also in customized print dialog (Wine 200504 -dosen'print, but printer
visible -screenshot), but NOT in the default system dialog for printers
configuration. winspool driver uses correct name:
trace:winspool:OpenPrinterW (printerName: L"xerox_230", pDefault (nil))
We tried to make simple workaround by defining the printer ' xerox_230' in the
wine's registry (keys are copy of 'xerox_230'). Now logs is different:
trace:winspool:GetDefaultPrinterW L"xerox_230,WINEPS,LPR:xerox_230"
trace:winspool:GetDefaultPrinterA 0x0000000a/0x00000104:L"xerox_230"
trace:winspool:OpenPrinterW (printerName: L" xerox_230", pDefault (nil))
trace:winspool:DocumentPropertiesA (0x10042,0x1, xerox_230,(nil),(nil),0)
trace:winspool:OpenPrinterW (printerName: L" xerox_230", pDefault (nil))
trace:winspool:GetPrinterDataExA (0x2, "PrinterDriverData", "PPD File" (nil),
(nil), 00000000, 0x406bc094)
warn:winspool:GetPrinterDataExA Can't open subkey "PrinterDriverData"
err:psdrv:PSDRV_FindPrinterInfo Error 2 getting PPD file name for printer '
xerox_230'
trace:winspool:ClosePrinter Handle 0x2
trace:winspool:DocumentPropertiesA (0x10042,0x1, xerox_230,0x489c0b18,(nil),2)
trace:winspool:OpenPrinterW (printerName: L" xerox_230", pDefault (nil))
trace:winspool:GetPrinterDataExA (0x2, "PrinterDriverData", "PPD File" (nil),
(nil), 00000000, 0x406bc094)
warn:winspool:GetPrinterDataExA Can't open subkey "PrinterDriverData"
err:psdrv:PSDRV_FindPrinterInfo Error 2 getting PPD file name for printer '
xerox_230'
Missing PPD file, ok so we added [ppd] section to the wine's config:
[ppd]
"generic" = "/tmp/generic.ppd"
Next tests was made on 'to_file' as default printer, because we have no local
access to the xerox_230.
Printing from wine's notepad is always succesful without errors. Command:
WINEDEBUG="+winspool" wine "c:\\windows\\notepad.exe". Also when we changed
printer in the system dialog, no error messages was generated.
Now ISS/VFP9 is able to print without errors in logs, but output are only lines
without text. When we tried to change printer in ISS, no action was made and no
errors or warning was in logs -- printer is still cups default.
When we tried to change windows type for ISS from 'nt40' to 'winxp' or
'win2000', no printers are available in the ISS customized print dialog and this
line is repeated in logs:
fixme:commdlg:PrintDlgExA stub
System dialog for printer configuration works fine from ISS application.
Best regards
--
Michal Okresa
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.