Bug 181014 - google gadgets added twice
Summary: google gadgets added twice
Status: RESOLVED DUPLICATE of bug 162599
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-16 21:44 UTC by sts
Modified: 2009-06-25 23:06 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description sts 2009-01-16 21:44:00 UTC 
Version:           4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 77.1" (using 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 77.1", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.7-9-default

I have added the Virtual Flower Pot from google gadgets. If I click twice on "Add" I get this gadget also twice in my list :(
And I have no option to remove one of the pot..
Comment 1 Jakub Grandys 2009-02-08 12:36:10 UTC 
Same here. You can delete gadgets by deleteing related dirs in ~/.kde4/share/apps/plasma/plasmoids/ggl-*
Comment 2 Jonas Vejlin 2009-06-24 20:34:08 UTC 
#0 did you trie what #1 suggested
Comment 3 Aaron J. Seigo 2009-06-24 22:35:27 UTC 
you can remove one of them by mousing over the pot an clicking it's close button.
Comment 4 sts 2009-06-25 20:24:45 UTC 
It's fixed in KDE 4.3Beta2? I can't see any option in my "add plasmoid" list to remove a google gadget.
Comment 5 Aaron J. Seigo 2009-06-25 23:06:25 UTC 
ah! you want to remove the installation, not an actual widget on the desktop.

ok, so:

* there is another report with uninstallation of widgets as a feature request (which we should get with the current GSoC project).

* that you can install a widget more than once with GG is a bug in the GG browser and should be reported to their project.

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