Created attachment 121629 [details] The error code that appears when you try to open a samba-shared file SUMMARY I'm unable to scan (and therefore add to my library) the music folder located in my local NAS (being cifs-mounted or not) with the Elisa tool (the progress bar advances but it doesn't do anything). Also, if I try to open a file by manually searching it, Elisa displays the attached error, which says "file.aiff is a file, but a folder was expected" I've tried to play the files with VLC and everything works fine. STEPS TO REPRODUCE 1a. Try to add a samba-shared folder to the music library with Elisa 1b. Try to play a file located in a remote samba-shared folder with Elisa, or mount that folder and try to play one of its file OBSERVED RESULT a. Anything has changed b. The attached error appears EXPECTED RESULT a. The album contained in the folder and subfolder should be added to the music library b. The files should play correctly like every audio file located in storage devices like the computer hard disk or a USB pendrive SOFTWARE/OS VERSIONS Linux: Manjaro x64 updated with the latest packages as of 2019-07-19 KDE Plasma Version: latest released as of 2019-07-19 KDE Frameworks Version: latest released as of 2019-07-19 Qt Version: latest released as of 2019-07-19
How are you accessing the Samba shared folder? Locally mounting it? from the smb://server/share path? Some other method?
(In reply to Nate Graham from comment #1) > How are you accessing the Samba shared folder? Locally mounting it? from the > smb://server/share path? Some other method? If in Dolphin I navigate to smb://server/share and I play the diles with Elisa, nothing happens If I mount smb://server/share to /home/jack/music/smb I can see that folder and all of its content in Elisa, but when I try to play an audio file I only get the attached error message
Thank you! If neither of those methods work, that's not good. Ideally both should.
I cannot reproduce when the samba share is mounted. Is this still an issue with latest git?
*** Bug 414547 has been marked as a duplicate of this bug. ***
Can you try again with Elisa 19.12.1? We think we've fixed this now.
(In reply to Nate Graham from comment #6) > Can you try again with Elisa 19.12.1? We think we've fixed this now. Thank you all, I've just tried, here is what I found: RESULTS [smb share mounted on local folder] Working as if the music files are stored in the local drive [file in a non protected smb share > right click > Open with Elisa] Working, see the "smb-free.png" attachment [file in password protected smb share > right click > Open with Elisa] Not working, see the "smb-protected.png" attachment PROBLEMS I have the password of the protected share stored in Dolphin, and when I use it to open the remote folder it behaves normally. Why can't Elisa (and VLC) access to the share using Dolphin? Or its credentials? Or at least prompt the user to enter them? Also, any idea on why I'm getting the message in the "indexer.png" attachment? I've just reinstalled and removed "/home/jack/.cache/elisa/" and "/home/jack/.local/share/elisa/" In both the working cases I still can't: - see the artwork in Elisa - see the files under "recently played"
Created attachment 125182 [details] Elisa log when opening a file from a non protected share
Created attachment 125183 [details] Elisa log when opening a file from a password protected share
Created attachment 125184 [details] Elisa Local Files Indexer error message
It looks like the local file indexer didn't get installed properly, which is possibly a distro packaging issue, or else some kind of local error. That would be throwing off other things. I would recommend getting that fixed and then trying again.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Reinstalling elisa doesn't solve the file indexer problem
I can play file from a samba share with elisa 19.12.2 running "elisa smb://samba-server/path/to/file/song.mp3" in Konsole. Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1
But I can't add a samba share to elisa settings. When I click on "Ok" button to confirm selection, "Configure" window closes and the path is not added.
(In reply to Patrick Silva from comment #15) > But I can't add a samba share to elisa settings. > When I click on "Ok" button to confirm selection, "Configure" window closes > and the path is not added. Elisa is now correctly giving the smb:// url to the audio player and it just works. Indexing the music directly from a samba share would require direct support in Elisa and it is not yet done (would probably require usage of KIO). This could be quite slow if you have a big collection and may require some support for preindexing your music like Amarok could.
*** Bug 422365 has been marked as a duplicate of this bug. ***
*** Bug 424517 has been marked as a duplicate of this bug. ***
*** Bug 393180 has been marked as a duplicate of this bug. ***
*** Bug 436917 has been marked as a duplicate of this bug. ***
*** Bug 447180 has been marked as a duplicate of this bug. ***
I'm not exactly sure if i should report here or at bug 418605 (should i duplicate the comment there as well???)... Anyway, here is my case: I have musics on my phone. I would like to be able, when i am on the network (kde connect'ed, for example...), that elisa would load that musics and let me ear them (stream them from my phone) just like it came from any other hard drive.
*** Bug 462363 has been marked as a duplicate of this bug. ***
*** Bug 467618 has been marked as a duplicate of this bug. ***