After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 171011 - StickyNotes 'on top' status is not remebered across sessions
StickyNotes 'on top' status is not remebered across sessions
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: stickynotes
2.10.x
Other other
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-20 17:14 UTC by Bas Leerintveld
Modified: 2010-01-24 01:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Bas Leerintveld 2005-03-20 17:14:11 UTC
Distribution: Debian 3.1
Package: gnome-applets
Severity: normal
Version: GNOME2.10.0 2.10.x
Gnome-Distributor: Ubuntu
Synopsis: StickyNotes 'on top' status is not remebered across sessions
Bugzilla-Product: gnome-applets
Bugzilla-Component: stickynotes
Bugzilla-Version: 2.10.x
Description:
Description of Problem:

StickyNotes 'on top' status is not remebered across sessions.

Steps to reproduce the problem:
1.  Disable 'on top' 
2.  Log out, saving session
3.  Log in

Actual Results:

Sticky notes still apear on top.

Expected Results:

I expected sticky notes to behave like any other window now.

Additional Information:

Using Metacity 2.10.0 on Ubuntu Hoary.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-20 12:14 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-applets".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Danielle Madeley 2005-12-21 07:06:14 UTC
The interaction for stickynotes was changed (again) in 2.12, obsoleting this bug.