Bug 21105 - Installing some Plasma5 Widgets are not showing in the widget panel.
Summary: Installing some Plasma5 Widgets are not showing in the widget panel.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords: IN_ERRATA6
Depends on:
Blocks:
 
Reported: 2017-06-18 05:27 CEST by Stephen Pettin
Modified: 2021-05-17 01:15 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Stephen Pettin 2017-06-18 05:27:32 CEST 
I did a Right-Click on the desktop, Add Widgets, Search for a widget (Event Calendar), chose Install. But now I do not see it listed in the Widget menu/panel.
If I search it again it show the "Event Calendar", the one I chose with Uninstall option now. But it's not showing in the regular Widget panel menu, to install or drag & drop.

Someone mention on IRC KDE channel "does this folder exist? ~/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/ exist? That's where the "installer" should be unzipping to".

Only thing I have related to plasma is this, ".local/share/plasma_notes/". I'm not certain if Mageia6 is using a different location for plasmoids/widgets or not.

I also tried to install widget 'Command Output' but I do not see that either. They show as if they are installed but I can't find them.

Mageia 6 with Plasma5 v5.8.7
Marja Van Waes 2017-06-19 15:22:16 CEST

Assignee: bugsquad => kde
CC: (none) => marja11

katnatek 2017-09-26 00:45:25 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=20645
CC: (none) => j.alberto.vc

katnatek 2018-02-04 00:11:12 CET

Keywords: (none) => IN_ERRATA6

Comment 1 Aurelien Oudelet 2021-05-17 01:15:30 CEST 
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.