SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Can you describe how in more detail? Screenshots or screen recordings would help too.
Created attachment 120291 [details] attachment-5115-0.html Hi, my goodness that was quick! I suspect it might be something to do with my MP3 collection being on a separate partition. Have since begun transfering music files to the normal music folder. That seems to have helped. Will report back once the file transfer is complete. It's nearly 50Gb On Fri, 24 May 2019, 21:11 Nate Graham, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=407918 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |nate@kde.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Can you describe how in more detail? Screenshots or screen recordings would > help too. > > -- > You are receiving this mail because: > You reported the bug.
Did you tell Elisa to look in the other partition for music? By default it only looks in ~/Music, but you can add other locations in its settings window, which can be accessed by clicking on the hamburger near in the top-right corner.
On Friday, 24 May 2019 21:32:21 BST you wrote: > https://bugs.kde.org/show_bug.cgi?id=407918 > > --- Comment #3 from Nate Graham <nate@kde.org> --- > Did you tell Elisa to look in the other partition for music? By default it > only looks in ~/Music, but you can add other locations in its settings > window, which can be accessed by clicking on the hamburger near in the > top-right corner. Hello there. OK, I appear to have got things working now. I am sorry if I was perhaps a little too short of patience. This is what happened. I read today on Google Now about your player Elisa. I have been using Clementine for a while now but it has recently begun misbehaving. Hence my eagerness to try something new. I have an old laptop that I have installed Manjaro onto. There are a number of partitions on this single HDD laptop and while one of them contains the working system of Manjaro, until now, my music collection has been located on one of the other partitions. Having downloaded and installed the Elisa via the EUR repositories, I impatiently tried to change the location by doing exactly what your previous mail asked. I clicked on the three horizontal bars to access the configure menu and tried to add a new path. For some reason, it wouldn't allow me to do so. Well actually that is not accurate. I entered the new path, but it failed to scan properly the contents of that path. I have a partition called Multimedia, and a folder called music contains some eight thousand files. The scanning pop up appears for a few seconds and then disappears, but no files appeared in my library on the Elisa. Now however, I have moved some of my music files to the home/name/music folder and they have - after a restart - shown up in the library. Much to my embarrassment, the program appears to be working now. Sorry for being a bit impatient.
Excellent. However it's still a bug that it didn't pick up your music on another partition even after you added that partition as a search path. The software should conform to your needs, not the other way around! What kind of partition is it? Does it happen to be formatted with the NTFS filesystem by any chance?
On Friday, 24 May 2019 21:55:32 BST you wrote: > https://bugs.kde.org/show_bug.cgi?id=407918 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Summary|Installed the program via |Does not find music on > |Aur repositories and tried |other partition when it is > |to get it to analyze my |added to search paths > |collection. Unfortunately | > |it doesn't find my | > |collection. | > > --- Comment #5 from Nate Graham <nate@kde.org> --- > Excellent. However it's still a bug that it didn't pick up your music on > another partition even after you added that partition as a search path. The > software should conform to your needs, not the other way around! > > What kind of partition is it? Does it happen to be formatted with the NTFS > filesystem by any chance? Actually it is ext4 /dev/sda3 mount point /mnt/... Does that help? Everything is working now,
Thanks for the info!
On Friday, 24 May 2019 22:08:02 BST you wrote: > https://bugs.kde.org/show_bug.cgi?id=407918 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > Summary|Does not find music on |Does not find music on > > |other partition when it is |other ext4 partition even > |added to search paths |when added to search paths > > --- Comment #7 from Nate Graham <nate@kde.org> --- > Thanks for the info! you are welcome. thanks for speedy reply.
Got the same problem in my case on a NTFS partition even after removing the Elisa db manually. KDE Frameworks Version: 5.58.0
Created attachment 120545 [details] STDOUT with logging enabled I can also reproduce this with the Elisa nightly flatpak. I have verified that Elisa has been given filesystem permission for the mount point of the partition. If an album exists in both ~/Music and the mount, the album shows up twice in the album listing, but one of them (the one from the mount) is empty. Also, other flatpak apps can access the mount point when given the permissions. (I have a steam library on the same drive.)
I'm also having this same issue on Manjaro, although it didn't use to happen a few months ago. My partition is ext4 and it's mounted on /media and doesn't seem to find any files inside it for some reason. I've tried uninstalling, deleting the elisarc file inside .config and reconfiguring but it won't find any files unless I move them to /home/name/Music. I've also tried to create a symlink inside Music folder and still nothings happens.
At least for ~/Music being a symlink to somewhere else, this is the issue: org.kde.elisa.baloo: rootPaths: ("/home/luca/Music") org.kde.elisa.baloo: LocalBalooFileListing::triggerRefreshOfContent "/mnt/hdd/Music/Monstercat/Monstercat 020 - Altitude/16. Muzzy - Lost Metropolis.mp3" does not match root paths So basically the symlink has to be resolved. After changing the Elisa config to not point to /home/luca/Music but to /mnt/hdd/Music, my music finally appeared. Btw for debugging baloo stuff in elisa, the command 'env QT_LOGGING_RULES="org.kde.elisa.baloo.debug=true" elisa' is quite useful.
That makes sense, because Baloo intentionally does not resolve symlinks. I think the idea is that the location that the symlink points to should itself simply be added to the index instead. Maybe Elisa can take care of resolving the symlink itself and pass the resolved path to Baloo?
Elisa master has the same problem on Neon unstable edition, but with another file system. Elisa does not find tracks located on my secondary partition formatted with ntfs file system.
(In reply to Patrick Silva from comment #14) > Elisa master has the same problem on Neon unstable edition, but with another > file system. > Elisa does not find tracks located on my secondary partition formatted with > ntfs file system. I can't reproduce this problem on Neon unstable edition anymore.
(In reply to Nate Graham from comment #13) > That makes sense, because Baloo intentionally does not resolve symlinks. I > think the idea is that the location that the symlink points to should itself > simply be added to the index instead. > > Maybe Elisa can take care of resolving the symlink itself and pass the > resolved path to Baloo? Should I open a separate issue for the symlinks because with latest git master of elisa, that issue is not fixed?
(In reply to Luca Weiss from comment #16) > (In reply to Nate Graham from comment #13) > > That makes sense, because Baloo intentionally does not resolve symlinks. I > > think the idea is that the location that the symlink points to should itself > > simply be added to the index instead. > > > > Maybe Elisa can take care of resolving the symlink itself and pass the > > resolved path to Baloo? > > Should I open a separate issue for the symlinks because with latest git > master of elisa, that issue is not fixed? Yes please.
(In reply to Patrick Silva from comment #14) > Elisa master has the same problem on Neon unstable edition, but with another > file system. > Elisa does not find tracks located on my secondary partition formatted with > ntfs > file system. This problem is back on Neon unstable edition.
Git commit f980f6e66eb7d3273e73f77cd520cdc4081c545c by Alexander Stippich. Committed on 22/08/2019 at 18:11. Pushed by astippich into branch 'master'. Resolve symlink for file listener Summary: Always resolve symlink so that Baloo indexer works Related: bug 410670 Test Plan: remove actual music folder from search path delete old database create a symlink to your music folder add symlink as search path music is found with patch Reviewers: mgallien, ngraham Reviewed By: ngraham Tags: #elisa Differential Revision: https://phabricator.kde.org/D23240 M +10 -3 src/abstractfile/abstractfilelisting.cpp https://commits.kde.org/elisa/f980f6e66eb7d3273e73f77cd520cdc4081c545c
Still having this issue. Using an NTFS filesystem on an external HD. At the moment i have no way to use Elisa: the only way I can import anything from that HD is by importing a plyalist of an album and very few have one. OS - Manjaro KDE
*** Bug 414196 has been marked as a duplicate of this bug. ***
Here is a merge request intended to fix this issue. It should disable Baloo and allow the plain old filesystem indexer to do the job (might be slow). Please can you test https://invent.kde.org/kde/elisa/merge_requests/40 ?
Fixed in 20.04!
(In reply to Matthieu Gallien from comment #22) > Here is a merge request intended to fix this issue. > It should disable Baloo and allow the plain old filesystem indexer to do the > job (might be slow). > > Please can you test https://invent.kde.org/kde/elisa/merge_requests/40 ? If I get this right, one just needs to add the directory in question to 'folders[$e]' in '~/.config/baloofilerc' or use 'balooctl config' to do that. If that is the case, this points to a deeper usability issue in Baloo, as it does not allow applications to work with it that can be pointed to files outside of $HOME. Brought up that issue in: Bug 415206 - By default cannot be used with Elisa for music files outside $HOME
(In reply to Martin Steigerwald from comment #24) > If I get this right, one just needs to add the directory in question to > 'folders[$e]' in '~/.config/baloofilerc' or use 'balooctl config' to do > that. If that is the case, this points to a deeper usability issue in Baloo, I forgot to add: I got this right. Adding to folder to Baloo indexing resolved the issue for me with Baloo 19.12.0.
Git commit 63e9df2c0f1402c46af9814a4b299bf90d7b7ff2 by Matthieu Gallien. Committed on 18/12/2019 at 16:54. Pushed by mgallien into branch 'release/19.12'. Merge branch 'disactivateBalooWhenNeeded' into release/19.12 https://invent.kde.org/kde/elisa/commit/63e9df2c0f1402c46af9814a4b299bf90d7b7ff2
*** Bug 415739 has been marked as a duplicate of this bug. ***
I am unclear if this bug is still open, but I am having the same issue on my manjaro system. Difference being my music folder is the main partition in the default place (still ext4). Sometimes it scans the music, sometimes it does not. And when it does find them, it is probably gone when I restart the application. It can find them and play them just fine through the internal file browser. I have better luck with the "scan files directly" toggled on, but better only means that I sometimes see the music.