Summary: | Device actions do not update. | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | illumilore <illumilore> |
Component: | widget-devicenotifier | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | adaptee, asraniel, bcooksley, codestruct, netfalo+kdebugs, p.r.worrall, sergio.callegari, wilderkde |
Priority: | NOR | Keywords: | junior-jobs |
Version: | 4.9.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
illumilore
2011-07-25 19:56:23 UTC
The KCM updates the actions properly, but the Device Notifier does not detect these changes... @Device Notifier maintainer: perhaps we need to agree on a way to write out changes to these files and notify each other of changes? *** Bug 266009 has been marked as a duplicate of this bug. *** I would like to confirm the issue on kubuntu natty with kde 4.7.0 To summarize: 1) Inserting an audio CD pops up the "play audio cd with amarok" but does not pop up the "play audio cd with kscd", meaning that the solid action for kscd is wrong 2) Indeed the action is wrong, since in /usr/share/kde4/apps/solid/actions/kscd-play-audiocd.desktop it is X-KDE-Solid-Predicate=[ StorageVolume.ignored == false AND OpticalDisc.availableContent == 'Audio' ] while solid-hardware clearly shows that the StorageVolume.ignored property should be true and the OpticalDisc.available contain should contain "Audio" rather than being equal to it. But this is not the only issue. 3) When trying to fix the rule from system settings, the fixed rule goes into .local/share/applications/kscd-play-audiocd.desktop from which it is nicely ignored. Furthermore: 4) If I move the kscd actions to ~/.kde/share/apps/solid/actions, then they remain ignored. Furthermore the system settings stops seeing the updated actions. I can confirm this with KDE 4.8.90. Test case: 1. Insert USB Memory Stick 2. Device Notifier offers "Download Photos with Gwenview" and "Open with file manager", both of which work as expected. 3. Use Device Notifier settings to make some changes (e.g. rename the Gwenview action, and change its command string) 4. Re-insert the Memory Stick 5. The changes I made in step 3 have had no effect 6. The changes are still visible via Device Notifier settings This bug is still present in KDE 4.10.4 First I went to device notifier settings/device actions and add to all gwenview related action an extra 's'. Then I plugged the pendrive, extra 's' were missing from the text as described earlier, so I installed plasmaengineexplorer to check the datasource, result was the same, no extra 's', but at least the problem is not in the widget, but I learned that it reads the data from gwenview_importer.desktop. Using locate I find two gwenview_importer.desktop: /home/netfalo/.local/share/applications/gwenview_importer.desktop /usr/share/kde4/apps/solid/actions/gwenview_importer.desktop I opened both of them, and I could find the changes in the first file (in my home folder). After that I deleted the extra 's' from the first one and added it to the second one, plugged my pendrive again I could see there was the extra 's'. So basically if you change, the device actions through KConfig, it will save changes under your home folder, but the widget reads data from /usr. I would gladly help to fixit, however I'm only a beginner with KDE development, so I would need some help how to start Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham |