https://bugs.winehq.org/show_bug.cgi?id=44614
Bug ID: 44614 Summary: DynEd: crash after log in Product: Wine Version: 3.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: alberto.piccioni@gmail.com Distribution: ---
Created attachment 60603 --> https://bugs.winehq.org/attachment.cgi?id=60603 tis is the error file generate by Wine
DynEd start on wine, than when is logged in, it stop. The message is someting as: The program Launchs.exe have found an error.
https://bugs.winehq.org/show_bug.cgi?id=44614
--- Comment #1 from Anastasius Focht focht@gmx.net --- *** Bug 44615 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=44614
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|DynEd: crash after log in |DynEd (English Language | |Learning software) crashes | |after login CC| |focht@gmx.net Keywords| |download URL| |http://download.dyned.com/s | |oftwareupdates/courses2/STU | |DENT_EU1.EXE
--- Comment #2 from Anastasius Focht focht@gmx.net --- Hello,
it seems there is no way to reproduce unless there is valid login.
Regards
https://bugs.winehq.org/show_bug.cgi?id=44614
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #3 from Fabian Maurer dark.shadow4@web.de --- Can you provide a full log, including backtrace?
https://bugs.winehq.org/show_bug.cgi?id=44614
--- Comment #4 from Alberto Piccioni alberto.piccioni@gmail.com --- (In reply to Anastasius Focht from comment #2)
Hello,
it seems there is no way to reproduce unless there is valid login.
Regards
ThanK you for the Answer.
The log in is ok. User name and password: ok.
But when the program DynEd ask me to choose a lesson, it stop and the message is included in the file I send you.
Regard
Alberto
https://bugs.winehq.org/show_bug.cgi?id=44614
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- No, he meant that we can't test it without a login. And we don't have a login.
https://bugs.winehq.org/show_bug.cgi?id=44614
--- Comment #6 from Wylda wylda@volny.cz --- *** Bug 44615 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=44614
--- Comment #7 from Anastasius Focht focht@gmx.net --- Hello Alberto,
you could generate a full trace log and attach it to the ticket (with the risk of login data being embedded, unless you filter for it).
--- snip --- # "cd" to "C:\Program Files (x86)\DynEd" directory before ... $ WINEDEBUG=+seh,+relay wine ./Launchw.exe >>log.txt 2>&1 --- snip ---
When the crash dialog appears, press "close" button.
Check if the log file contains credentials and filter/replace them via 'sed' (app might use API that shows password in clear text via parameters).
If the log file is too large (very likely), compress it (bzip2 log.txt) before attaching to the ticket.
Alternatively you can send me valid login data via email (hover over commenter name to see email address) and let me investigate. Might be the better/faster option overall. Non-disclosure/privacy is assured from my side.
Regards
https://bugs.winehq.org/show_bug.cgi?id=44614
--- Comment #8 from Alberto Piccioni alberto.piccioni@gmail.com --- (In reply to Anastasius Focht from comment #7)
Hello Alberto,
you could generate a full trace log and attach it to the ticket (with the risk of login data being embedded, unless you filter for it).
--- snip --- # "cd" to "C:\Program Files (x86)\DynEd" directory before ... $ WINEDEBUG=+seh,+relay wine ./Launchw.exe >>log.txt 2>&1 --- snip ---
When the crash dialog appears, press "close" button.
Check if the log file contains credentials and filter/replace them via 'sed' (app might use API that shows password in clear text via parameters).
If the log file is too large (very likely), compress it (bzip2 log.txt) before attaching to the ticket.
Alternatively you can send me valid login data via email (hover over commenter name to see email address) and let me investigate. Might be the better/faster option overall. Non-disclosure/privacy is assured from my side.
Regards
Ok. I'm sending you an email con focht@gmx.net.
Than you very much.