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 102707 - 'New Login' as an entry in 'Actions' menu
'New Login' as an entry in 'Actions' menu
Status: RESOLVED DUPLICATE of bug 72598
Product: gnome-panel
Classification: Other
Component: general
2.1.x
Other Linux
: Normal enhancement
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-06 22:42 UTC by Blazej
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Blazej 2003-01-06 22:42:27 UTC
When GDM is installed it gives you a 'New Login' entry in
Applications->System submenu. I suggest moving it to Action panel menu,
just above the logout option. Seems just more logical there from the
usability point of view. It could be done the same way the find file tool
is dealt with ie. check whether GDM is installed and if so, place  the menu
entry there. I tried to patch the panel code and even got to the point,
where selecting the new menu option would actually run new login
(gdmflexiserver) but I was unable to deal with drag'n'drop from menu to
panel (any option from 'Actions' submenu when dragged was something
different than should have been, like icon supposed to log me out spawned a
'find file' window). So I left it there, but it gave me the impression of
not being to difficult to achieve. At least for someone who has a clue
about the panel code. :)
Comment 1 Vincent Untz 2003-01-08 21:17:28 UTC
Blazej: please look at bug #72598. This is nearly a duplicate. Is it
ok to mark your bug as dup of this one ? Maybe you could add a comment
there...
Comment 2 Blazej 2003-01-09 13:56:02 UTC
Sure, mark this bug as a duplicate of #72598 and I will make my
comment there.
Comment 3 Vincent Untz 2003-01-09 15:02:29 UTC

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