Bug 180993 - "Could not find requested component" error when adding new objects to plasma dashboard
Summary: "Could not find requested component" error when adding new objects to plasma ...
Status: RESOLVED DUPLICATE of bug 177083
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-16 18:01 UTC by enrico
Modified: 2009-01-16 19:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description enrico 2009-01-16 18:01:40 UTC
Version:           kde 4.2 rc2 (using Devel)
OS:                Linux
Installed from:    Compiled sources

Steps to reproduce:

- right click on dashboard and unblock objects;
- right click on dashboard and select add objects;
- a list of available objects appear: choose one and click on "add object" button.

Expected behavior:

object is correctly added.

bug description:

"This object can't be created for the following reason: Could not find requested component" error appears in new widgets at the place of added component when adding new objects to plasma dashboard.

I suspect that old objects are present and listed in "Add objects" menu but they are no more compatible. They should not be listed then, and they should be someway automatically uninstalled when updating to plasma version that
Comment 1 Aaron J. Seigo 2009-01-16 19:31:33 UTC
"They should not be listed then, and they should be
someway automatically uninstalled when updating to plasma version that"

we have users who feel the exact opposite and the entries shoudl be ignored until later so that if the user updates/upgrades the widget it can start working again instantly.

the real solution here is to actually keep your installation in order.

consider the notice as a friendly reminder.

*** This bug has been marked as a duplicate of bug 177083 ***