Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New installation in Big Sur. Doesn't scan shared folders. #899

Closed
LETRA opened this issue Dec 12, 2020 · 8 comments
Closed

New installation in Big Sur. Doesn't scan shared folders. #899

LETRA opened this issue Dec 12, 2020 · 8 comments
Labels

Comments

@LETRA
Copy link

LETRA commented Dec 12, 2020

Nicotine+ version: 2.2.0
Operating System/Distribution: macOS Big Sur Stable.

Describe the bug

I have installed Nicotine+ and it doesn't scan my disks. I have two external drives and Nicotine does not perform any operation. I have noticed that it does not ask for permissions to access external disks and I have restarted the system but there is no change here.

Expected behavior

Scanning.

Steps to reproduce the bug

Add folders. Restart the app. Wait. Restart the system.

Additional context

Screenshots, logs, stacktraces or relevant information.

Captura de pantalla 2020-12-12 a las 5 47 24

@LETRA LETRA added the bug label Dec 12, 2020
@LETRA LETRA changed the title New installation in Big Sur. Does not scan shared folders. New installation in Big Sur. Doesn't scan shared folders. Dec 12, 2020
@mathiascode
Copy link
Member

Is this only an issue with external disks, or also the main one?

@LETRA
Copy link
Author

LETRA commented Jan 3, 2021

Two external disks, but after several restarts began to scan. Anyway the message did not appear, but other programs do ask for access to external disks, I don't know why. In any case I went back to SoulseekQt because it took Nicotine fifteen or twenty hours to rescan 800.000 files and SoulseekQt checks the changes and adds new files in half an hour.

@mathiascode
Copy link
Member

I'm guessing almost all of those are audio files? Scanning times should definitely not last several hours, not sure if this is a macOS exclusive issue or some other bottleneck. Unfortunately I don't have a proper macOS system to test this.

@foerster-rwth
Copy link

foerster-rwth commented Jan 19, 2021

I'm guessing almost all of those are audio files? Scanning times should definitely not last several hours, not sure if this is a macOS exclusive issue or some other bottleneck. Unfortunately I don't have a proper macOS system to test this.

I was hoping that the new Nicotine+ version would improve scanning times. Unfortunately I've not been able to make v2.1.2 work (on Windows 10 Education). Haven't tried v2.2.0 yet.

Therefore I still run Nicotine+ v1.4.1, and that installation takes -- at the moment -- about 13 hours to scan 200,000 files on the NAS which holds the shares and is accessed via wi-fi. This is with my new router (Linksys ACS 1900 running DD-WRT), with the old router (Fritzbox 6591 Cable) it took considerably less time, about four hours.

@mathiascode
Copy link
Member

I was hoping that the new Nicotine+ version would improve scanning times. Unfortunately I've not been able to make v2.1.2 work (on Windows 10 Education). Haven't tried v2.2.0 yet.

Does Nicotine+ not work at all (e.g. not starting), or is file scanning the problematic part? Scanning times should be better than in 1.4.1, and some improvements were also made to scanning in 2.2.X, but I haven't tested network shares personally.

@mathiascode
Copy link
Member

Feel free to try the latest unstable version of Nicotine+, the scanning process was changed a bit.

@mathiascode
Copy link
Member

Closing for now. If this is still an issue on 3.0.0, feel free to open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants