Bug 348514 - Device Notifier missing KDE 4 actions
Summary: Device Notifier missing KDE 4 actions
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Disks & Devices widget (show other bugs)
Version: 5.3.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-31 18:55 UTC by Fred Wells
Modified: 2021-01-03 04:34 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred Wells 2015-05-31 18:55:40 UTC
Plasma 5 uses /usr/share/solid/actions for device actions.  Few, IF ANY, applications have yet to update from using /usr/share/kde4/apps/solid/actions, which is understandable since they must continue to support the more prominent KDE4.  Thus, the onus falls to KDE development (having created the problem) to bridge this gap IMO.

Reproducible: Always

Steps to Reproduce:
1. Insert/plug device
2. Observe the missing device actions

Actual Results:  
The only available action is to open with file manager.

Expected Results:  
All available device actions should be listed.

While there are workarounds, such as copying or linking /usr/share/kde4/apps/solid/actions to $HOME/.local/share/solid/actions , none of them are suitable for the casual, non-technical user.
Comment 1 Eric S 2016-01-27 03:49:03 UTC
Maybe this is distro-specific but all my actions from kde4 are in /usr/share/apps/solid/actions.

It seems to me one solution or workaround might be distros handled this. KDE ought to highlight the need for this to the distros in some info prominently provided to them when they get the Plasma 5 sources.
Comment 2 altosch 2016-02-05 08:57:29 UTC
Affects me either. Kubuntu 15.10, Plasma 5.5.3.

Here is some information:

http://askubuntu.com/questions/617138/how-can-i-get-the-plasma-5-device-notifier-to-give-me-appropriate-options-for-dv/617235#617235

In short:
  1. copy /usr/share/kde4/apps/solid/actions/ to ~/.local/share/solid/actions/
  2. run kbuildsycoca5 --noincremental
  3. restart Plasma (logout, login)

The solution works but the problem is you have to copy the old actions to the new ones repeatedly. Plasma should handle this.
Comment 3 Justin Zobel 2020-11-19 02:05:00 UTC
I've just tested this on Plasmashell 5.20.2 and I can't replicate the issue.

The only items in kde4/apps/solid/actions are vlc ones and they are also replicated into /usr/share/solid/actions/

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 4 Bug Janitor Service 2020-12-04 04:33:58 UTC
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!
Comment 5 Kevin Kofler 2020-12-04 13:14:00 UTC
Well, the problem is technically still there, but I suppose it is much less important these days now that most KDE applications have been ported to Qt5/KF5 and that most third-party applications have updated their Plasma integration to use the Plasma 5 directories.

This would have been an important compatibility issue to address when it was filed 5 years ago, but the inaction has turned it more or less moot.

I am not removing the NEEDINFO status (neither to close the bug immediately nor to set it back to REPORTED) because I am not the original submitter. Given the above situation, I am not going to object to the automatic closure if the submitter does not respond.
Comment 6 Bug Janitor Service 2020-12-19 04:34:56 UTC
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!
Comment 7 Bug Janitor Service 2021-01-03 04:34:24 UTC
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!