Michael Allan

I’m using Gentoo. I see that XFE lost its maintainer. https://bugs.gentoo.org/847253 Nowhere to go from here, I think. Not for a minor bug. Thanks for answering, though.

It’s also repeatable (as above) if I delete ~/.config/xfe/xferc and let it default to an unaltered copy of the global configuration file /usr/share/xfe/xferc (attached).

This is repeatable for me. (1) Change Edit|Preferences|Modes to ‘Start in the last visited folder’. (2) Move in the Folders tree to directory ~/tmp/. (3) Select File|Quit. (4) Verify that no other instance of XFE was running. (5) Verify that file ~/.config/xfe/xferc contains startdir_mode=2, as opposed to the usual 0. (6) Start XFE. It starts in directory ~/, not the expected ~/tmp/. In case it matters, I notice that file ~/.config/xfe/xferc (attached) contains two entries for lastdir: the first...

Turns out my bug title is a red herring (sorry). What causes the bug has nothing to do with NFS. Rather it’s a missing icon file. (1) In ~/.config/xfe/xferc under [FILETYPES], add this line: foo=<txteditor>,<txtviewer>,<txteditor>;Foo file;;foo_16x16.png;; (2) In XFE, view a directory that contains a file named test.foo. XFE segfaults because foo_16x16.png does not exist. 1.43.2 could handle a missing icon file, 1.44 cannot.

Configuration item `startdir_mode` is ignored

Segfault on viewing an NFS mounted subdirectory