install.sh installs no scripts since commit 380ba21 — category selection broken

[sebzeter]

Hi,

I've encountered a problem with the install.sh script starting from commit 380ba21.

Problem

The install script no longer installs any scripts.

When selecting “Choose script categories to install,” no categories appear, making it impossible to proceed.

Last Working Commit

The last working version is commit 1d0d3c9.

System Info

OS: openSUSE Leap 15.6

Desktop Environment: GNOME

Currently locked to nautilus-scripts version: 13.5.4

Steps to Reproduce

Clone the repo at or after 380ba21

Tested case #1

1. Run install.sh with default predefined options selected — notice that no scripts are installed

Tested case #2

1. Run install.sh

2. Choose “Select script categories to install” — observe that no categories are listed

Let me know if I can provide any logs or test a patch. Thanks for maintaining this project!

[cfgnunes]

Hi, thank you for reporting this issue!

I’ve tested the install script on my machine running openSUSE Leap 15.6 using the latest version of the scripts (v15.2.4), and I was not able to reproduce the error described.

It’s possible that older versions of the scripts had bugs that caused this behavior, especially around the commit you mentioned (380ba21). However, with the latest version, the category selection and installation process appear to be working as expected on my setup.

Could you please try running the script again using the latest version (v15.2.4) and let me know if the issue persists? If it does, feel free to share any logs or additional details that might help with troubleshooting.

Thanks again for taking the time to report this!

[sebzeter]

Hi,

I had already tested the latest version (v15.2.4) before reporting this bug. I'm attaching a screenshot of what I get with the two test cases, using all the versions I've tried since commit 380ba21.

In both cases, no scripts are installed in ~/.local/share/nautilus/scripts/ except:
.
├── common-functions.sh
└── .helper-scripts
├── multiselect-menu.sh
└── unit-tests.sh

How can I help you find where the problem is coming from?

[sebzeter]

I conducted some research on debugging Bash scripts in an effort to provide you with additional information.

An AI suggested running the command bash -x install.sh 2> stderr.log and submitting the file stderr.log, which you will find attached.

stderr.log

[sebzeter]

An (other) AI recommended executing the command bash -x install.sh 2>&1 | tee /tmp/output.log and submitting the resulting output.log file, which is attached.

I hope this information proves helpful.

output.log

[cfgnunes]

Hi @sebzeter,

Thank you so much for all the detailed information, logs, and screenshots — they were incredibly helpful in identifying the issue.

I’ve just pushed a possible fix in the following commit:
98eb374

Could you please test it and let me know if the problem is resolved on your side?

Thanks again for your time and effort in helping improve the project!

[sebzeter]

Hi,

I’ve just tested the fix introduced in commit 98eb374. The scripts do install correctly, but a few issues still persist or have appeared:

• The scripts are installed in ~/.local/share/nautilus/scripts/nautilus-scripts.git/ instead of the expected location: ~/.local/share/nautilus/scripts/ (see attachements: output.log + tree.txt)

• In tested case 2, script selection is still not possible, although the output is slightly different from the original situation: see the line starting with '[*]', just after the one that says "Select the categories (<SPACE> to check):".

  

• The scripts are also copied to ~/.local/share/scripts/nautilus-scripts.git/ instead of the expected location: ~/.local/share/scripts/. Maybe that’s why they don’t appear in Thunar (?)

• After I’ve already run install.sh in GNOME Terminal, trying to re-run the script (e.g. to test case 1 and then case 2) causes the terminal to close abruptly.

Please let me know if you need any more information or testing — I’m just a basic user, but happy to help however I can.

I really appreciate your work; it’s been incredibly useful to me. Thanks again for all the time and effort you put into this project!

Attachements:

output.log
tree.txt

[sebzeter]

Hi @cfgnunes,

I just wanted to follow up on issue #45, which you kindly agreed to take a look at some time ago. I was wondering if you’ve had a chance to review it, or if there’s anything I can do to help (testing, reproducing the bug, etc.).

Thanks again for your work on this project,

Have a great day!

[cfgnunes]

Hi @sebzeter !

Thanks a lot for following up and for your detailed bug report.

I want to let you know that I haven't forgotten about issue #45. I haven't been able to dive into it yet because it requires some careful attention to reproduce the issue properly on my end. My plan is to set up a separate machine with the same OS and file managers you’re using, so I can simulate every step with precision and care.

I’ve been quite busy these past months with some personal matters, but I fully intend to look into this issue with the attention it deserves. One of my goals is to not only fix the bug but also improve the installer overall and reduce redundancy in the codebase, especially regarding how required packages are defined per category.

Thanks again for your patience and for offering to help with testing. I may take you up on that once I’ve set up the environment!

All the best!

[cfgnunes]

Hi @sebzeter,

It seems that the issue might be caused by installing the package inside this directory:

/home/user/.local/share/nautilus/scripts/nautilus-scripts.git

Could you please try the following steps?

1. Remove all the contents of:

/home/user/.local/share/nautilus/

2. Move the installer package directory to a different location (for example: /home/user/Downloads) and then try installing again.

While you run these tests, I’m currently reviewing the installer and the installation script to confirm and improve its handling of such cases.

[cfgnunes]

Hi @sebzeter,

Also, could you test the last commit? cb012c4

Thanks