Opened 12 years ago

Closed 12 years ago

Last modified 8 years ago

#106 closed enhancement (fixed)

No logout option

Reported by: askvictor Owned by: sayamindu
Priority: major Milestone:
Component: Sugar Version: Git as of bugdate
Severity: Major Keywords:
Cc: eben Distribution/OS: Unspecified
Bug Status: Resolved

Description

If sugar is being deployed in a computer lab rather than laptops, it would be useful to have a 'log out' option in addition to the restart and shutdown options in sugar.

Attachments (1)

logout.patch (1013 bytes) - added by askvictor 12 years ago.
Patch for /usr/share/sugar/shell/view/home/favoritesview.py to allow logout

Download all attachments as: .zip

Change History (10)

Changed 12 years ago by askvictor

Patch for /usr/share/sugar/shell/view/home/favoritesview.py to allow logout

comment:1 Changed 12 years ago by askvictor

I've created a patch that allows this - patch the file /usr/share/sugar/shell/view/home/favoritesview.py and logout is added as a menu option. There is no logout icon yet.

comment:2 Changed 12 years ago by erikos

  • Owner changed from marcopg to sayamindu
  • Priority changed from minor to major
  • Status changed from new to assigned

askvictor, thanks for the patch. I have applied a similar patch to the sugar Fedora 10 package. We had a more detailed discussion in http://dev.laptop.org/ticket/8141

To get attention for patches, please use the guidelines here http://sugarlabs.org/go/DevelopmentTeam/CodeReview#Patch_submission and add a r? keyword.

Sayamindu said he would take care of this.

comment:3 Changed 12 years ago by erikos

  • Cc eben added

comment:4 follow-up: Changed 12 years ago by eben

I've yet to fully understand what logout means in our context. Sugar isn't multi-user aware yet, so in general the logout option doesn't make sense. In what contexts does it make sense, and can we dynamically determine when it does and doesn't and only offer the action when it's applicable?

comment:5 in reply to: ↑ 4 Changed 12 years ago by alsroot

Replying to eben:

I've yet to fully understand what logout means in our context. Sugar isn't multi-user aware yet, so in general the logout option doesn't make sense. In what contexts does it make sense, and can we dynamically determine when it does and doesn't and only offer the action when it's applicable?

that makes sense for common GNU/Linux distribution - user wants to work in sugar environment and he could login to sugar from account manager (like gdm); later he could decide leave sugar and login to Gnome/Kde environment

I use similar patch in Gentoo/ALTLinux packages

comment:6 follow-up: Changed 12 years ago by eben

OK, so while Sugar itself isn't multi-user capable, a user could "login" to a Sugar session and later leave that session via a "logout" option. Two follow up questions are:

  1. Can we, in software, determine when such an option is usable? (And if not, what does "logout" do when booting directly into Sugar, such as on an XO?)
  1. What does this mean if we later wish to introduce true multi-user support within Sugar itself? Do they conflict, or is this a non-issue?

comment:7 in reply to: ↑ 6 Changed 12 years ago by alsroot

Replying to eben:

OK, so while Sugar itself isn't multi-user capable, a user could "login" to a Sugar session and later leave that session via a "logout" option. Two follow up questions are:

  1. Can we, in software, determine when such an option is usable? (And if not, what does "logout" do when booting directly into Sugar, such as on an XO?)

I think the most suitable place is disto-level patches

  1. What does this mean if we later wish to introduce true multi-user support within Sugar itself? Do they conflict, or is this a non-issue?

Gnome/KDE are also true multi-user systems and there is logout option (and also 'switch user')

comment:8 Changed 12 years ago by tomeu

  • Bug Status set to Resolved
  • Distribution/OS set to Unspecified
  • Milestone set to 0.84
  • Resolution set to fixed
  • Severity set to Major
  • Status changed from assigned to closed
  • Version set to Git as of bugdate

comment:9 Changed 8 years ago by godiard

  • Milestone 0.84 deleted

Milestone 0.84 deleted

Note: See TracTickets for help on using tickets.