FZ 3.48.0: "Opening Failed" error message

[mrkgnao]

The following bug has appeared today, immediately after I had upgraded Filezilla to version 3.48.0. It didn't happen with previous versions (I have been using FZ daily for years --- thank you for creating this wonderful tool).

Now, whenever I doubleclick a LOCAL file in order to edit it, I get an error message popup reading "Opening failed: The file '[FILENAME HERE]' could not be opened: The associated command failed" (+ OK button). This is a spurious error message, as the file does open just fine. This happens with every local file I try to edit, forcing me to close this popup on every local file edit (a very common occurrence for me). It does not happen with files on the server.

My relevant settings are:
- File lists -> Double-click action on files -> View/Edit
- File editing -> Default editor -> use custom editor -> "C:\Program Files (x86)\Vim\vim74\gvim.exe"
- File editing -> Always use default editor

Additional observation:
- If instead of double clicking the local file, I right click it and select "Edit" the same error appears. However, if I select "Open" it does not.

[botg]

Cannot reproduce, working fine for me.

What is the full name and path of a local file that fails to open in this manner?

[intuipod]

I'm getting the same error as of yesterday. Same computer & files set-up before the new FZ update and files opened up fine with the exact same set-up and files.

When I "double click" on my local files i get an error message. The file does open, but the error pop-up message must be closed each time a file is opened in this manner in order to continue using FileZilla. I've attached the error message. If I "right click" and use the dropdown to select open the error does not happen. The files are on a local external hard drive. Double clicking has always worked in the past, now it creates this error.

Here are my specs:
FileZilla Pro
-------------

Version: 3.48.0

Build information:
Compiled for: x86_64-apple-darwin19.4.0
Compiled on: x86_64-apple-darwin19.4.0
Build date: 2020-04-29
Compiled with: Apple clang version 11.0.3 (clang-1103.0.32.59)
Compiler flags: -Werror=partial-availability -Wall -g

Linked against:
wxWidgets: 3.0.5
SQLite: 3.31.1
GnuTLS: 3.6.12

Operating system:
Name: Mac OS X (Darwin 19.4.0 x86_64)
Version: 10.15
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm
Settings dir: /Users/---/Library/Containers/org.filezilla-project.filezilla.sandbox/Data/.config/filezilla/

[mrkgnao]

Cannot reproduce, working fine for me.

What is the full name and path of a local file that fails to open in this manner?

Any file. For example, "C:\a.txt".

Note that the file does not "fail to open". It opens just fine, but it results in a spurious error popup that needs to be closed.

[intuipod]

Yes, the file does actually open, as stated, but it creates a pop-up error message. The error message says "Opening Failed" (see previous attachment) but the file does open.

It happens on all file types I've tried including:
.php
.css
.png
.js

[k1e2jebe]

I've been seeing the exact same behavior as everyone else since the last update.

The file does actually open, but it creates a pop-up error message.

filezilla.jpg (81.36 KiB) Viewed 5477 times

filezilla1.jpg (190.87 KiB) Viewed 5477 times

[boco]

@botg: Getting the same error, with FileZilla Free 3.48.0. Using "Edit" actually opens the file, but additionally creates the error message.

FileZilla Pro 3.47.2.1 works correctly.

[botg]

Try re-enabling the "Watch locally edited files and prompt to upload modifications"

[boco]

Re-enabling that setting has two direct results:
1. "Edit" of local files doesn't work anymore if you are not connected to a server.
2. It pops up the dialog window after saving which I do not want. That's the reason I unchecked that option.

[mrkgnao]

Re-enabling the "Watch locally edited files and prompt to upload modifications" has the following effects:
1) It does make the spurious error popup go away, which is good
but it results instead in two popups:
2) After saving an edited file, I get, as expected, a popup asking me whether to upload the file to the server, which in 90%+ of cases I do not want, not yet (hence my having turned it off years ago)
3) After having finished editing the file and having closed it, regardless of whether I did save a new version or not, if I then try to re-open the file, I get a popup informing me that the file is already being edited and whether I want to reopen it, which is, in my case, a pointless popup
so the net effect is worse (two popups instead of one), so I disabling the option again.

But you seem to be right that the spurious error popup is related to this checkbox being off.

[jmingov]

Hi,

Last version is no working as expected.
At least in the 2 windows machines I checked remotely. Something broke in the last update, rolling back to 3.47 and all is working fine again.

Clean install of 3.48 and same error.

Br,
J

[clight77]

Hi
After updating today I have the exact same error as everyone else in this topic.

[Adamski]

Hello Tim! hi guys,
First of all, since its my first post, I must say that Your program, Tim, is great. Good job! I have been using FZ for years and it never failed.
So, now is the first time a little bug with 3.48.0.
I have similar situation as described above. False error message - Notepad ++ opens files for editing - but "error popup" pops up.

Curious that remote files open with no problem or error message. Problem occurs with local files only. (php, html, css). Tried all options concerning editor.
Can WE help you, Tim , with any debugging/ logging messages ?
Second question, how to eventually downgrade?
Best Regards!

[th4n4t0s]

"Edit->Settings->File editing -> Filetype associations" are broken

See: viewtopic.php?f=2&t=52871#p173658 for a fix

[Grath]

Just as an FYI, today's nightly build (05-07-2020) seems to fix all of the file association issues (at least so far as far as I can tell during my testing) so I expect a patch will be released soon.