Bug 275175 - kfmclient icon is not getting removed from task manager in kde 4.7beta1
Summary: kfmclient icon is not getting removed from task manager in kde 4.7beta1
Status: RESOLVED DUPLICATE of bug 278724
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-taskbar (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-08 04:18 UTC by Mohd Asif Ali Rizwaan
Modified: 2011-08-03 17:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mohd Asif Ali Rizwaan 2011-06-08 04:18:11 UTC 
Version:           unspecified (using Devel) 
OS:                Linux

the new "Show a Launcher for <appname> When it is not running" is a very good feature; but, the default Launcher pinned on taskbar kfmclient is automatically getting 'pinned again' after re-login.

other launchers are not bothering. The kfmclient launcher is coming back after logging in again to kde4.7beta1.

Reproducible: Always

Steps to Reproduce:
1. create new user (or mv .kde(4) to .kde.old)
2. login using the new user 
3. we can see '...' 'dolphin' 'kfmclient' icons on panel/ taskbar
4. right-click on kfmclient launcher, and choose 'remove'
5. logout

6. re-login with the last username
7. kfmclient is back again


Actual Results:  
kfmclient launcher is not removed from configuration files. though konqueror is removed (if added)

Expected Results:  
kfmclient icon should be removed on removal and should not comeback on re-login.

OS: Linux (x86_64) release 2.6.39-ARCH
Compiler: gcc
Comment 1 Mohd Asif Ali Rizwaan 2011-06-08 04:20:49 UTC 
the dolphin launcher is also not getting removed on re-login; which means the removal-settings of default launchers are not stored to configuration files.
Comment 2 Vic 2011-07-31 10:05:30 UTC 
I get the same behavior, also on an arch system
Upgrade with existing settings is not affected
Comment 3 Christoph Feck 2011-08-03 17:36:57 UTC 

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