https://bugs.kde.org/show_bug.cgi?id=363105
--- Comment #7 from Marco Z <23n...@gmail.com> --- (In reply to Myriam Schweingruber from comment #6) > That might be the root of the problem, then. If you are using external media > for your collection you always need to make sure it is mounted before Amarok > starts. > Another source of the slowdown can be a too large playlist containing music > from external sources: since all the tracks in the loaded playlist are > checked for availability, this slows down the whole startup process. > The option "watch folders for change" is dependent on a fast access to the > collection, but external media like NFS shares are not as fast as local > collections are. I fear there is nothing we can do about this. Hi Myriam, the NFS share is always mounted at boot over a Gigabit link and it's available when Amarok starts, this problem started to happen after a while though; disabling the inotify is not a problem, I can trigger the update manually when I add files, the collection is pretty big indeed, 638G on NFS and 44G local, all FLAC. I raised a bug as I couldn't find any precise reason for this in the output, once it hangs, waiting for some time doesn't seem to improve. It's not slowing down, it's becoming at all non responsive; usually I kill it after 5-15 mins. The ticket can be closed for me, or set to very low prio if you wish to sort it out, I'm available to test. -- You are receiving this mail because: You are watching all bug changes.
