![]() Not sure if this is the correct place to ask, but i cannot find the ![]() > are generated a short time after every commit. > Just re-download and install from Unstable installer packages > Those are commit references for the repo, they're of no use to you On Sat, at 8:54 PM William Woollard Ok, thanks for the clarification. Looks like that has fixed some of the things ! awesome job. > Triage notifications on the go with GitHub Mobile for iOS > Reply to this email directly, view it on GitHub > You are receiving this because you were mentioned. > latest one, remove the db files and rescan, and see if anything has changed? > The unstable Windows builds are working again. Once again I reallyĪppreciate all the effort going into this thing. It is, it may be tomorrow before I report the results. * Ignoring invalid metadata for file*Īnd it looks like this is going to take a while, so depending on how long ![]() The indexing reported a new error for many files that i have not seen yet. Working so far, side note: I like the debug categories in the right click. ![]() Apparently the 32-bit Unstable package is easier to install on Windows 10 at the moment, we haven't tested 11 yet, so this would be appreciated if you are able to test this installed the 64bit version of the dev client on windows 11 and it's However there are some unrelated issues with PyInstaller that is currently blocking master release to Stable, and may prevent you from installing the Unstable package. If possible please verify that the problem you are having is resolved (or at least reported in more detail with the improved Debug error logging) in the Unstable branch, because Nicotine+ 3.2.0 will be released soon. There have been several improvements to the handling of these issues with share scanner in 3.2.0.dev1. There is the problem that I think may have been addressed already where file names that are too long or something will give an error. If you delete your whole profile then Nicotine+ will go to factory defaults. This will force a rebuild of your shares from scratch. Is there something else I need to do to fully remove at least the share settings?ĭelete all the files/folders ending in *.db in your. Screenshots, logs, stacktraces or relevant information. Steps to reproduce the bugīrowse my nicotine share with a QT client Additional context To be able to share files and have them configured correctly or in some cases show up at all. is there something else I need to do to fully remove at least the share settings? any help is appreciated. I did try to uninstall and reinstall, but it seems to have saved some of the settings as my queue and info are still intact. Also there is the problem that I think may have been addressed already where file names that are too long or something will give an error. I also have some other issues with some folders showing up as empty even though there are files in them, and I think that is both on nicotine and QT. if that makes sense, if not have a screen shots. The first problem I have is that some sub-folders are shared on the same level as their root folder when viewed with soulseekQT but not with nicotine. Operating System/Distribution: Windows 11 Describe the bug
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |