Saved files named incorrectly

[Tangbravo221]

GM,

Describe the bug
Single file all of sudden (probably after a background update of Chrome), started saving files as:
(example): 85896719-4f70-42ca-938d-4e42aa9abc3f.htm

To Reproduce
Simply save any file and it happens.

Expected behavior
The file should be save with the template in the file name option.
%if-empty<{page-title}|No title> ({date-locale} {time-locale}).{filename-extension}
or whatever: (I had simply {page-title}.{filename-extension}

Environment

• OS: Windows 10 Enterprise
• Browser: I have Chrome Version 138.0.7204.169 (Official Build) (64-bit) (also happens in the latest Brave, BUT NOT IN FIREFOX (also latest)
• Version: see above

In windows 10, in chromium based browsers, single file all of sudden (probably after a background update of Chrome), started saving files as: (example) 85896719-4f70-42ca-938d-4e42aa9abc3f.htm

I have Chrome Version 138.0.7204.169 (Official Build) (64-bit) (also happens in the latest Brave, BUT NOT IN FIREFOX (also latest)

Additional context
Does not happen in FIREFOX, only in chromium based browsers (Chrome and Brave)
I've checked the known issues and the FAQ.
I've reset settings in single file
Restarted chrome
Uninstalled single file and restarted my computer.
Imported settings from the firefox single file settings export json.

None of these attempts worked. No idea what else to try.

Any suggestions?

Thanks,

Alfred

[Blackdos]

Hi,

have the same Problem with Chrome 138.0.7204.169 (Offizieller Build) (64-Bit), but with Edge 138.0.3351.109 (Offizielles Build) (64-Bit) works the extension still.
OS Windows 11

Thanks
Peter

[Tangbravo221]

Seems to be a chromium based issue....

[Abel31041]

Hi,
have the same Problem with Chrome 138.0.7204.184 (64-Bit)
OS Windows 11
Thanks

[MitaZ]

Have you guys installed and enabled the IDM Integration Module extension? If enabled, trying to disable IDM's extension might solve this issue. I disabled IDM after seeing this issue #1770 , and everything has been normal since then.

I don't know why the IDM plugin used to work with SingleFile, but it didn't work recently, maybe an update Chrome broke something @Blackdos @Abel-Trans

[Blackdos]

Yes, I have IDM Integration running, anbd yes,if I disable IDM, SingleFile works fine. But, ich have the same IDM Extension running in Edge now 139.0.3405.86 and there Singelfile works with active IDM Int. Mod.
So for me it seems, there must be a specific Chrome problem, wich is not related to the chromium base of the two browsers.

Chrome 139.0.7258.67 with IDM 6.42.42.2
Edge 139.0.3405.86 with IDM 6.42.32

Is there any further information we can send to help solve the problem? Not using IDM is not the solution...

[MitaZ]

Yes, I have IDM Integration running, anbd yes,if I disable IDM, SingleFile works fine. But, ich have the same IDM Extension running in Edge now 139.0.3405.86 and there Singelfile works with active IDM Int. Mod. So for me it seems, there must be a specific Chrome problem, wich is not related to the chromium base of the two browsers.

@Blackdos Same here, my SingleFile extension is not affected in Edge browser even if IDM Integration Module extension is installed.

Microsoft Edge: 139.0.3405.86 (Official build) (64-bit) 
IDM Integration Module Version6.42.32

In the other two browsers based on Chrome 130 and 138 kernel, the operation of SingleFile was interfered with by IDM.

I guess it is either related to the Edge browser, they may have done some compatibility processing, or it is related to the version of the IDM extension (the possibility is very low, because it seems that IDM has not updated their extension recently)

This also explains why this problem only affects browsers on Windows platforms. I have an identical browser configuration on macOS Sequoia 15.6 (24G84), but SingleFile works fine because there is no IDM on macOS.😂

More details may require the author to dig out. After disabling the IDM extension, at least everything works normally for now.

[radiant-tangent]

I'm on a Mac (Sequoia 15.6) running edge (139.0.3405.86) and SingleFile (1.22.81) and it is the "Video DownloadHelper" extension (10.0.125.2) that is causing the issue for me. After I disabled it, things are named correctly. I don't see the issue in chrome on the same machine because VDH is version 9.5.02.

Tested on Windows 11 Home computer (Build 10.0.26100) and see the same problem with Edge and VDH 10.

SingleFile is working fine in Firefox across all browsers and OSs; however VDH is 9.5.02.

So, it seems we've narrowed it down to extension issues. I know VDH's refactor from v9 to v10 was a big one. I wonder if it and the IDM extension are both doing the same thing to interfere with SingleFile renaming.

[radiant-tangent]

This also works around the issue:
Turn off Misc > "Save File in Background" in SingleFile Settings

In Known Issues https://github.com/gildas-lormeau/SingleFile/blob/master/known-issues.md
Related to Chromium Bug https://issues.chromium.org/issues/41418926

[Blackdos]

This also works around the issue: Turn off Misc > "Save File in Background" in SingleFile Settings

Indeed, that works.....