On 10/1/2022 8:36 PM, bad sector wrote:
-----------------------------
gftp
gFTP Warning: Skipping line 86 in config file: enable_ipv6
gFTP Warning: Skipping line 238 in config file: resolve_symlinks
gFTP Warning: Skipping line 257 in config file: http_proxy_host
gFTP Warning: Skipping line 260 in config file: http_proxy_port
gFTP Warning: Skipping line 263 in config file: http_proxy_username
gFTP Warning: Skipping line 266 in config file: http_proxy_password
gFTP Warning: Skipping line 269 in config file: use_http11
Illegal instruction (core dumped)
-----------------------------
The above comes if using a common .gftp folder
(including gftprc) with other installed distros,
a method I'm adopting to serve my multi-OS box.
If I rename that common .gftp folder (which works just
fine with my six other distros) thus forcing regeneration
then none of the above instructions are in the new file
......but I still can't launch:
-----------------------------
gftp
Illegal instruction (core dumped)
-----------------------------
I'd like to get gftp to work first using it's
own Ubuntu-Studio .gftp folder before tinkering
with a common one.
NB. Filezilla loads OK but gftp is my favorite
--
Saturdays are UbuntuStudio days
Ubuntu 22.04.1 LTS (Jammy Jellyfish),Kernel=5.15.0-43-lowlatency
on x86_64,DM=sddm,DE=KDE,ST=x11,grub2,GPT,BIOS-boot https://i.imgur.com/QKljk7F.png
U2204
First problem, is sudo apt install gftp does the wrong thing.
It installs gftp-common and not all four packages.
You would start by visiting synaptic and tending to that part.
I expect you already have sorted that part, as what mine (gftp-common)
was reporting was
Error: Can't find gFTP binaries
After all four packages are installed, typing
gftp
brings up "gFTP 2.9.1b" GUI window, with a two-pane view, local
file system on the left, remote file system on the right.
Typing
gftp-text
brings up ftp> prompt and I just type "quit" into that. No crash.
There is a .gftp directory in my home.
bookmarks 3091 bytes
gftp.log 36 bytes
gftprc 8703 bytes 293 lines, "ascii text"
Try "file gftprc" and see if it is "ascii text" or not.
The package was written in 1998, or started at that point,
it does not use vala, it is written in C. It has mention of
UTF-8 in it, which means someone other than the original
author of the code likely added that.
Does it support UTF-8 in the gftprc file ? Dunno.
Use a hex editor and examine your gftprc file carefully
for 8 bit items that don't belong. The reason I suggest that,
is given the age of the application, parts of it likely started
as ASCII-only. And it might be intolerant of some edits
done by some clever text editor on one of your other OSes.
Make sure there is a newline at the end of the file, in
case it is intolerant.
The UTF-8 support is likely on the remote-facing or local
file system front, when handling file names there. In my
travels, I've seen absolutely dogs-breakfast filenaming,
with every punctuation and special character under the
sun in it. The only thing missing was a smiley emoji
for the joke they were playing. It might have been
Hungarian. You do need good character handling, for
the real world.
Whereas the RC file may not have received any UTF-8 support.
It depends on whether it was localized or not, so other
languages in the RC could be supported.
But at least it did not crash in a way suggesting
a "bad build". The build seems OK here.
Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)
