https://bugs.winehq.org/show_bug.cgi?id=41835
Bug ID: 41835 Summary: lg dvd firmware updater crashes Product: Wine Version: 1.8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: oswald.buddenhagen@gmx.de Distribution: Debian
Created attachment 56254 --> https://bugs.winehq.org/attachment.cgi?id=56254 crash dump
encouraged by some success stories relating to similar procedures, i tried updating the firmware of my dvd-rw drive with the updater from http://www.lg.com/us/support-product/lg-GH22NS30 (i tried both the 2.00 and 1.03 versions). however, the program crashes at startup.
the crash is in the application itself, but it's undoubtedly the result of some inaccuracy in wine. i tried both 1.8.5 and 1.9.x.
https://bugs.winehq.org/show_bug.cgi?id=41835
Oleg Kuznetsov oleg.kuznetsov@metamint.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |oleg.kuznetsov@metamint.ru
--- Comment #1 from Oleg Kuznetsov oleg.kuznetsov@metamint.ru --- (In reply to Oswald Buddenhagen from comment #0)
however, the program crashes at startup.
the crash is in the application itself, but it's undoubtedly the result of some inaccuracy in wine. i tried both 1.8.5 and 1.9.x.
Do you mean by "startup"? Because with wine-4.9 it shows error that I don't have the required ATAPI device (which is true) and exits without any crashes. Could you re-test with the latest version of wine?
https://bugs.winehq.org/show_bug.cgi?id=41835
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net URL| |https://web.archive.org/web | |/20190525112224/http://gscs | |-b2c.lge.com/downloadFile?f | |ileId=KRSWD000002542-b1-a1. | |zip Summary|lg dvd firmware updater |LG DVD firmware updater for |crashes |GH22NS30 ver. 2.0 crashes | |on startup Keywords| |download
--- Comment #2 from Anastasius Focht focht@gmx.net --- Hello folks,
if you can reproduce it, please specify exactly *when* does it crash ("clicked X") and provide a debug trace (https://wiki.winehq.org/FAQ#How_do_I_get_a_debug_trace.3F)
I have a notebook with DVD drive and tricked the firmware updater to ignore the model until it asks if the firmware should be really flashed.
--- snip --- $ winedbg --gdb ./GH22NS30_2.00.exe -q <<< "b *0x004081da"$'\n'cont$'\n'"set $ps=$ps&~0x40"$'\n'cont$'\n' --- snip ---
Gdb proxy mode ftw. Have a conditional branch go to desired location (clearing ZF). Patching the opcode would work too, just to show alternative solution.
NOTE: it still needs a removable drive present to have this nifty hack to work.
Your description make it sound it crashes without any interaction at all which I can't confirm. Even with old Wine 1.8 I still get asked "Do your want to start F/W reflash?"
Stable link using Internet Archive:
https://web.archive.org/web/20190525112224/http://gscs-b2c.lge.com/downloadF...
$ sha1sum GH22NS30_200(ew).zip 14daf5982850fc30773397c11898cabf874c7880 GH22NS30_200(ew).zip
$ du -sh GH22NS30_200(ew).zip 996K GH22NS30_200(ew).zip
$ wine --version wine-1.8-3-gc1ceb3ee5a
$ wine --version wine-4.9
Regards
https://bugs.winehq.org/show_bug.cgi?id=41835
Oswald Buddenhagen oswald.buddenhagen@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Oswald Buddenhagen oswald.buddenhagen@gmx.de --- "at startup" is generally understood to mean "before any interaction". ;)
anyway, the problem is gone with wine 4.0 and the program appears to do something (at 4% progress, it gets stuck and then aborts with a somewhat unhelpful error message, but the drive firmware is actually already at the target state, so whatever).
https://bugs.winehq.org/show_bug.cgi?id=41835
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.10.
-
wine-bugs＠winehq.org