Opened 7 years ago
Closed 7 years ago
#11096 closed Bug report (fixed)
When "Messagelog position" is 2, Filezilla does not start
| Reported by: | Annorax | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | Cc: | ||
| Component version: | Operating system type: | Windows | |
| Operating system version: | 7 Professional |
Description
I am running Windows 7 Professional and Filezilla 3.23.0 64 bit. This issue was not present in 3.22.2.2.
When I upgraded versions as mentioned above, I was unable to start Filezilla. The process would not launch yet I could see it in Windows Task Manager taking about 13% CPU. I waited about 10 minutes but nothing happened so I killed the process.
After playing with filezilla.xml, I noticed that this only happens when "Messagelog position" is set to 2 - set to 0 or 1 is fine.
Note:
See TracTickets
for help on using tickets.
Thanks for reporting. Issue has been fixed in 3.23.0.1