Custom Query (8105 matches)


Show under each result:

Results (316 - 318 of 8105)

Ticket Resolution Summary Owner Reporter
#12167 fixed The Associated Command Failed Jones

Whenever I right click and choose "Edit" menu for a file, for instance a txt file, although the file will open up in my Macbook Textedit app as usual, an error message following will popup says "Opening Failed.... 'file path' could not be opened: The Associated Command Failed".

File extension included txt php htm html etc.. Although I didn't setup any filetype association under the setting menu, it shouldn't behave like that. Also the filetype association command is not working too I had tried. It only happens in this latest app version for Mac.

#12166 wontfix Integer Overflows when Processing Directory Listing Bill

There are integer overflows in enging/directorylistingparser.cpp and interface/remotelistview.cpp, when converting from the string received to int64_t. A number higher than the max of int64_t as the size returned in a directory listing will be improperly parsed and produce nonsensical results, such as a negative file size.

This happens on lines 220, 2644, and 2665 in directorylistingparser and 782 in remotelistview (not an exhaustive list).

Since this value is not used, other than displayed to the user, I do not think this can be exploited, nor crash the program.

#12165 fixed 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.

P.S. Also posted this on the forum.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.