Version: 3.5.9 (using KDE 3.5.9) Installed from: Gentoo Packages Compiler: gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2) OS: Linux Been working on this problem with Jeff Mitchell on the amarok list. On a gentoo system kernel version 2.6.23.14 ndas verion 1.1-15 kdelibs version 3.5.9 kde 3.5.59 The kde mediamanager recognizes when the ndas drive is mounted, but doesn't recognize/notify the system when it's unmounted. Jeff isn't sure if it's related to the HAL/hald daemon or the mediamanager, but the drive doesn't show up at all if the hald daemon is running. Output from "dcop kded mediamanager fullList" when ndas device has not yet been mounted: /org/kde/mediamanager/fstab/devndas-02121533-0p1media ndas-02121533-0p1 Hard Disk (ndas-02121533-0p1) true /dev/ndas-02121533-0p1 /media vfat false media/hdd_unmounted --- Output from "dcop kded mediamanager fullList" after ndas device has been mounted: /org/kde/mediamanager/fstab/devndas-02121533-0p1media ndas-02121533-0p1 Hard Disk (ndas-02121533-0p1) true /dev/ndas-02121533-0p1 /media vfat true media/hdd_mounted --- After the device has been mounted once, it's never shown as umounted until after a reboot. However both the mount command and /etc/mtab reflect the proper status of the drive. If the hald daemon has been started, the ndas device doesn't show up in this list whether or not it's been mounted. I found this because the amarok media player has consistently dropped the collection of music I have stored on my ndas drive. The logic it's programmers use compares the songs in the database against the songs on the drive if the mediamanager indicates the drive is mounted. If it doesn't find the songs on the "mounted" drive, it drops them from the database. Since the mediamanager never shows the MG-35 as being unmounted once it has been mounted, it consistently drops my entire collection of several thousand songs. Because the ndas drive isn't the fastest kid on the network, it takes a considerable amount of time to rescan the drive and populate the database. (I've submitted an identical bug report to the ximeta folks.)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!