MantisBT - Doomseeker |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0003759 | Doomseeker | [All Projects] Bug | public | 2020-01-31 04:39 | 2021-08-10 05:48 |
|
| Reporter | haxmurderer | |
| Assigned To | Zalewa | |
| Priority | high | Severity | block | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | Microsoft | OS | Windows | OS Version | 10 |
| Product Version | 1.3 | |
| Target Version | 1.3.2 | Fixed in Version | 1.3.2 | |
|
| Summary | 0003759: Auto-Updated installer fails to launch - Entry Point Not Found |
| Description | It seems like the latest release is broken and won't install via the auto-updater.
I'm currently on Doomseeker 1.3-190727-0915, and I'm getting a critical error when I try to run the new installer downloaded by the auto-updater. It says "The procedure entry point blah blah blah could not be located in the dynamic link library .... doomseeker-update-pkg--updater.exe".
See the steps to reproduce. |
| Steps To Reproduce | Run Doomseeker 1.3-190727-0915.
Wait for the notification that a new update is available.
Click "Download & Install" and wait for it to download.
Click "Restart & Install Now".
Boom - you'll get the error message in the screenshot, and the installer will fail to run. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  2020-01-30 23_35_04-Clipboard.png (9,797) 2020-01-31 04:39
https://zandronum.com/tracker/file_download.php?file_id=2562&type=bug
|
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2020-01-31 04:39 | haxmurderer | New Issue | |
| 2020-01-31 04:39 | haxmurderer | File Added: 2020-01-30 23_35_04-Clipboard.png | |
| 2020-01-31 07:17 | Zalewa | Note Added: 0021177 | |
| 2020-01-31 12:47 | WubTheCaptain | Assigned To | => Zalewa |
| 2020-01-31 12:47 | WubTheCaptain | Status | new => feedback |
| 2020-01-31 14:44 | haxmurderer | Note Added: 0021179 | |
| 2020-01-31 14:44 | haxmurderer | Status | feedback => assigned |
| 2020-01-31 16:35 | Zalewa | Note Added: 0021180 | |
| 2020-08-02 08:12 | Zalewa | Note Added: 0021522 | |
| 2020-08-02 08:12 | Zalewa | Status | assigned => needs review |
| 2020-08-02 12:27 | WubTheCaptain | Status | needs review => needs testing |
| 2020-08-02 12:28 | WubTheCaptain | Target Version | => 1.3.3 |
| 2021-08-07 16:48 | Blzut3 | Fixed in Version | => 1.3.2 |
| 2021-08-07 16:48 | Blzut3 | Target Version | 1.3.3 => 1.3.2 |
| 2021-08-08 10:34 | Zalewa | Status | needs testing => resolved |
| 2021-08-08 10:34 | Zalewa | Resolution | open => fixed |
| 2021-08-10 05:48 | WubTheCaptain | Status | resolved => closed |
|
Notes |
|
|
(0021177)
|
|
Zalewa
|
|
2020-01-31 07:17
|
|
|
Workaround: try copying libgcc_s_dw2-1.dll and libstdc++-6.dll from Doomseeker's directory to C:\Users\Albert\AppData\Local\doomseeker\updates and tell me if it worked. |
|
|
|
|
Zalewa: I copied those DLLs and it seems to get further. I see the updater.exe in the "updates" directory now, but I get this different error message.
I used Dependency Walker to discover that it also needed libwinpthread-1.dll. If I copy that DLL over to the "updates" directory too, it works! |
|
|
|
(0021180)
|
|
Zalewa
|
|
2020-01-31 16:35
|
|
|
updater.exe needs to be statically linked. I'm afraid there's no real hotfix aside from this workaround for anyone else that may get this problem. |
|
|
|
(0021522)
|
|
Zalewa
|
|
2020-08-02 08:12
|
|
|