Bug 121981 - remove from panel config option is not permanent
remove from panel config option is not permanent
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rhn-applet (Show other bugs)
3.0
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Daniel Veillard
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-04-29 10:37 EDT by Chris Tatman
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-04-29 11:49:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Chris Tatman 2004-04-29 10:37:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
When users configure their rhn-applets, the Remove From Panel option
only temporarily removes the applet from the panel.  The applet comes
back whenever the user logs out and back on again.  In a corporate
environment where the updates are centrally maintained, this is an
unnecessary and sometimes unwanted feature.  

Version-Release number of selected component (if applicable):
rhn-applet-2.0.12-1

How reproducible:
Always

Steps to Reproduce:
1.  Right click applet on panel and select Configuration
2.  Click Forward
3.  Click on Remove From Panel
4.  Log out
5.  Log back on
6.  Applet is back on panel
    

Actual Results:  Applet is removed for the current session, but
reappears after users log out and back on.

Expected Results:  The Applet should never appear on the panel after
the 'Remove From Panel' option has been configured.

Additional info: na
Comment 1 Daniel Veillard 2004-04-29 11:49:08 EDT
You must save the desktop config in step 4 to have the change
permanently recorded, like for any other change at the desktop
level. This is a feature really !

Daniel

Note You need to log in before you can comment on or make changes to this bug.