https://bugs.winehq.org/show_bug.cgi?id=45259
Bug ID: 45259 Summary: Outlook 2007 crashes and enters infinite loop (restart in failed mode) if automatic printing is invoked Product: Wine Version: 3.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: quatze@t-online.de Distribution: ---
Created attachment 61508 --> https://bugs.winehq.org/attachment.cgi?id=61508 Trace of the crash until before restart with +win,+actctx,+msg,+button,+loaddll
I have a setup, which automatically creates PDF printouts of MSG files via cups-pdf and the /p flag of Outlook when being run through wine.
This all worked well until the change from 3.7 to 3.8. It is still present in 3.9.
Instead of just printing and leaving the program, the debugger is started and a window is presented, in which I can choose to report the bug to MS. Regardless of what I do, the program wants to start again and I can choose to start it in safe mode or not. Regardless of what I choose, the program crashes again. So, the setup enters a loop.
Expected behavior: Printing windows opens, Outlook prints and closes successfully.
Trace file has been created with: WINEDEBUG=+win,+actctx,+msg,+button,+loaddll
https://bugs.winehq.org/show_bug.cgi?id=45259
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #1 from Anastasius Focht focht@gmx.net --- Hello marlemion,
are you on ArchLinux?
If yes, then this might be a dupe of bug 45199 (https://bugs.archlinux.org/task/58688)
You could try to create a full relay trace and attach it to this ticket (compress if too large).
--- snip --- $ WINEDEBUG=+seh,+relay,+ole,+variant wine ./foobar.exe >>log.txt 2>&1 --- snip ---
Regards
https://bugs.winehq.org/show_bug.cgi?id=45259
--- Comment #2 from marlemion quatze@t-online.de --- Hi Anastasius,
1) Yes, I am on Arch
2) I would like to, but when I run the command with said debug flags, it succeeds! This is very weird. It also happens with MS word, by the way.
Maybe there is a race condition somewhere and switching on the debug flags slows down the process and helps finding the right code path?
Should I try another combination of debig flags?