Re: NAND out of space crash (was Display warnings in sugar (Emiliano Pastorino))
disclaimer.
The attached patch is untested and likely insufficient to solve this
problem.
On Sat, Jul 19, 2008 at 01:39:20PM -0400, Erik Garrison wrote:
> On Sat, Jul 19, 2008 at 12:58:13PM -0400, Benjamin M. Schwartz wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Erik Garrison wrote:
> > | On Sat, Jul 19, 2008 at 11:47:21AM -0400, Greg Smith wrote:
> > |> Hi All,
> > |>
> > |> Emiliano has an elegant workaround but crashing the XO on NAND full (to
> > |> un-recoverable state?) is a heinous bug that affects essentially all
> > users.
> > |>
> > |> If someone has the bug ID handy can you send it out and mark it a
> > |> blocker for 8.2.0 (priority = blocker and keyword includes blocks:8.2.0)?
> > |>
> > |> Can I get a design proposal (no re-partitioning please!), scoping and
> > |> lead engineer on it ASAP?
> > |>
> > |> If you have to stop working on something else to do this, let me know
> > |> what will drop and I'll help weigh the consequences.
> > |
> > | My impression is that the long-term benefits of partitioning mean that
> > | it's worthwhile to devote effort to it. Are we not going to work on
> > | partitioning in the future?
> >
> > Adding partitioning does not automatically solve the NAND fillup problem.
> > ~ The fundamental issue is that Sugar tries to write files on boot, and
> > fails to boot if it cannot write those files.
> >
> > The correct solution is to make sure that Sugar can boot even if it cannot
> > write files. This change is needed in order to enable booting on full
> > NAND, whether or not partitioning is used to separate system and user
> > files. In short, these issues, while related, are largely decoupled, and
> > can be attacked separately.
>
> You are absolutely correct.
>
> Partitioning can be used to isolate the system filesystem(s) from the
> effects of user-level data creation, and thus mitigate the risk of
> fillup of a partition yielding an unbootable system. However, the
> solution is wholly ineffectual wrt. the fillup issue until we ensure
> Sugar only needs to write to the partition which we are confident will
> have space. If we are going to check all the file write requirements of
> the Sugar shell, we might as well implement the far better solution of
> enabling Sugar to boot without writing anything.
>
> Below is a patch to Sugar which resolves the only python-side case of a
> file write during startup which I was able to find.
>
> I couldn't find reference to the configuration variables saved in
> _save_session_info elsewhere in the sugar repository. If these
> variables are pulled from the config file after Sugar startup, then this
> patch is a bad idea on its own.
>
>
>
> diff --git a/src/main.py b/src/main.py
> index b1ecc93..1899438 100644
> --- a/src/main.py
> +++ b/src/main.py
> @@ -55,15 +55,19 @@ def _save_session_info():
> #do not rely on it
> #
> session_info_file = os.path.join(env.get_profile_path(), "session.info")
> -f = open(session_info_file, "w")
> +try:
> +f = open(session_info_file, "w")
> +
> +cp = ConfigParser()
> +cp.add_section('Session')
> +cp.set('Session', 'dbus_address',
> os.environ['DBUS_SESSION_BUS_ADDRESS'])
> +cp.set('Session', 'display',
> gtk.gdk.display_get_default().get_name())
> +cp.write(f)
>
> -cp = ConfigParser()
> -cp.add_section('Session')
> -cp.set('Session', 'dbus_address', os.environ['DBUS_SESSION_BUS_ADDRESS'])
> -cp.set('Session', 'display', gtk.gdk.display_get_default().get_name())
> -cp.write(f)
> +f.close()
> +except IOError, (errno, sterror):
> +logger.error("Could not open session_info_file. %s" % sterror)
>
> -f.close()
>
> def _setup_translations():
> locale_path = os.path.join(config.prefix, 'share', 'locale')
> diff --git a/src/main.py b/src/main.py
> index b1ecc93..1899438 100644
> --- a/src/main.py
> +++ b/src/main.py
> @@ -55,15 +55,19 @@ def _save_session_info():
> #do not rely on it
> #
> session_info_file = os.path.join(env.get_profile_path(), "session.info")
> -f = open(session_info_file, "w")
> +try:
> +f = open(session_info_file, "w")
> +
> +cp = ConfigParser()
> +cp.add_section('Session')
> +cp.set('Session', 'dbus_address',
> os.environ['DBUS_SESSION_BUS_ADDRESS'])
> +cp.set('Session', 'display',
> gtk.gdk.display_get_default().get_name())
> +cp.write(f)
>
> -cp = ConfigParser()
> -cp.add_section('Session')
> -cp.set('Session', 'dbus_address', os.environ['DBUS_SESSION_BUS_ADDRESS'])
> -cp.set('Session', 'display', gtk.gdk.display_get_default().get_name())
> -cp.write(f)
> +f.close()
> +except IOError, (errno, sterror):
> +logger.error("Could not open session_info_file. %s" % sterror)
>
> -f.close()
>
> def _setup_translations():
> locale_path = os.path.join(config.prefix, 'share',
Re: NAND out of space crash (was Display warnings in sugar (Emiliano Pastorino))
On Sat, Jul 19, 2008 at 12:58:13PM -0400, Benjamin M. Schwartz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Erik Garrison wrote:
> | On Sat, Jul 19, 2008 at 11:47:21AM -0400, Greg Smith wrote:
> |> Hi All,
> |>
> |> Emiliano has an elegant workaround but crashing the XO on NAND full (to
> |> un-recoverable state?) is a heinous bug that affects essentially all users.
> |>
> |> If someone has the bug ID handy can you send it out and mark it a
> |> blocker for 8.2.0 (priority = blocker and keyword includes blocks:8.2.0)?
> |>
> |> Can I get a design proposal (no re-partitioning please!), scoping and
> |> lead engineer on it ASAP?
> |>
> |> If you have to stop working on something else to do this, let me know
> |> what will drop and I'll help weigh the consequences.
> |
> | My impression is that the long-term benefits of partitioning mean that
> | it's worthwhile to devote effort to it. Are we not going to work on
> | partitioning in the future?
>
> Adding partitioning does not automatically solve the NAND fillup problem.
> ~ The fundamental issue is that Sugar tries to write files on boot, and
> fails to boot if it cannot write those files.
>
> The correct solution is to make sure that Sugar can boot even if it cannot
> write files. This change is needed in order to enable booting on full
> NAND, whether or not partitioning is used to separate system and user
> files. In short, these issues, while related, are largely decoupled, and
> can be attacked separately.
You are absolutely correct.
Partitioning can be used to isolate the system filesystem(s) from the
effects of user-level data creation, and thus mitigate the risk of
fillup of a partition yielding an unbootable system. However, the
solution is wholly ineffectual wrt. the fillup issue until we ensure
Sugar only needs to write to the partition which we are confident will
have space. If we are going to check all the file write requirements of
the Sugar shell, we might as well implement the far better solution of
enabling Sugar to boot without writing anything.
Below is a patch to Sugar which resolves the only python-side case of a
file write during startup which I was able to find.
I couldn't find reference to the configuration variables saved in
_save_session_info elsewhere in the sugar repository. If these
variables are pulled from the config file after Sugar startup, then this
patch is a bad idea on its own.
diff --git a/src/main.py b/src/main.py
index b1ecc93..1899438 100644
--- a/src/main.py
+++ b/src/main.py
@@ -55,15 +55,19 @@ def _save_session_info():
#do not rely on it
#
session_info_file = os.path.join(env.get_profile_path(), "session.info")
-f = open(session_info_file, "w")
+try:
+f = open(session_info_file, "w")
+
+cp = ConfigParser()
+cp.add_section('Session')
+cp.set('Session', 'dbus_address',
os.environ['DBUS_SESSION_BUS_ADDRESS'])
+cp.set('Session', 'display', gtk.gdk.display_get_default().get_name())
+cp.write(f)
-cp = ConfigParser()
-cp.add_section('Session')
-cp.set('Session', 'dbus_address', os.environ['DBUS_SESSION_BUS_ADDRESS'])
-cp.set('Session', 'display', gtk.gdk.display_get_default().get_name())
-cp.write(f)
+f.close()
+except IOError, (errno, sterror):
+logger.error("Could not open session_info_file. %s" % sterror)
-f.close()
def _setup_translations():
locale_path = os.path.join(config.prefix, 'share', 'locale')
diff --git a/src/main.py b/src/main.py
index b1ecc93..1899438 100644
--- a/src/main.py
+++ b/src/main.py
@@ -55,15 +55,19 @@ def _save_session_info():
#do not rely on it
#
session_info_file = os.path.join(env.get_profile_path(), "session.info")
-f = open(session_info_file, "w")
+try:
+f = open(session_info_file, "w")
+
+cp = ConfigParser()
+cp.add_section('Session')
+cp.set('Session', 'dbus_address', os.environ['DBUS_SESSION_BUS_ADDRESS'])
+cp.set('Session', 'display', gtk.gdk.display_get_default().get_name())
+cp.write(f)
-cp = ConfigParser()
-cp.add_section('Session')
-cp.set('Session', 'dbus_address', os.environ['DBUS_SESSION_BUS_ADDRESS'])
-cp.set('Session', 'display', gtk.gdk.display_get_default().get_name())
-cp.write(f)
+f.close()
+except IOError, (errno, sterror):
+logger.error("Could not open session_info_file. %s" % sterror)
-f.close()
def _setup_translations():
locale_path = os.path.join(config.prefix, 'share', 'locale')
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: NAND out of space crash (was Display warnings in sugar (Emiliano Pastorino))
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Erik Garrison wrote: | On Sat, Jul 19, 2008 at 11:47:21AM -0400, Greg Smith wrote: |> Hi All, |> |> Emiliano has an elegant workaround but crashing the XO on NAND full (to |> un-recoverable state?) is a heinous bug that affects essentially all users. |> |> If someone has the bug ID handy can you send it out and mark it a |> blocker for 8.2.0 (priority = blocker and keyword includes blocks:8.2.0)? |> |> Can I get a design proposal (no re-partitioning please!), scoping and |> lead engineer on it ASAP? |> |> If you have to stop working on something else to do this, let me know |> what will drop and I'll help weigh the consequences. | | My impression is that the long-term benefits of partitioning mean that | it's worthwhile to devote effort to it. Are we not going to work on | partitioning in the future? Adding partitioning does not automatically solve the NAND fillup problem. ~ The fundamental issue is that Sugar tries to write files on boot, and fails to boot if it cannot write those files. The correct solution is to make sure that Sugar can boot even if it cannot write files. This change is needed in order to enable booting on full NAND, whether or not partitioning is used to separate system and user files. In short, these issues, while related, are largely decoupled, and can be attacked separately. - --Ben -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiCHSQACgkQUJT6e6HFtqShPgCgoWYHUPQsi6Aa7H9uCyI+m342 aV8An15IEhFE3dxZdSDaZfRtTjuB99lO =JQ70 -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: NAND out of space crash (was Display warnings in sugar (Emiliano Pastorino))
On Sat, Jul 19, 2008 at 11:47:21AM -0400, Greg Smith wrote: > Hi All, > > Emiliano has an elegant workaround but crashing the XO on NAND full (to > un-recoverable state?) is a heinous bug that affects essentially all users. > > If someone has the bug ID handy can you send it out and mark it a > blocker for 8.2.0 (priority = blocker and keyword includes blocks:8.2.0)? > > Can I get a design proposal (no re-partitioning please!), scoping and > lead engineer on it ASAP? > > If you have to stop working on something else to do this, let me know > what will drop and I'll help weigh the consequences. My impression is that the long-term benefits of partitioning mean that it's worthwhile to devote effort to it. Are we not going to work on partitioning in the future? In addition to a more solid solution to the NAND fillup issue, we get the opportunity to improve system performance and upgrade procedures. Partitioning will allow us to test out LZO data compression for the XO's filesystems (excluding /boot and /security). We would expect a significant i/o performance boost from the use of LZO. Additionally, partitioning would improve OFW-level system updates (e.g. copy-nand) by making it far simpler for the update procedure to leave user data intact. That said there are obviously a lot of troubles with partitioning. Updating an existing system to a partitioned one without mashing user data is a major issue. Erik ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: NAND out of space crash (was Display warnings in sugar (Emiliano Pastorino))
Hi All, Emiliano has an elegant workaround but crashing the XO on NAND full (to un-recoverable state?) is a heinous bug that affects essentially all users. If someone has the bug ID handy can you send it out and mark it a blocker for 8.2.0 (priority = blocker and keyword includes blocks:8.2.0)? Can I get a design proposal (no re-partitioning please!), scoping and lead engineer on it ASAP? If you have to stop working on something else to do this, let me know what will drop and I'll help weigh the consequences. Thanks, Greg S [EMAIL PROTECTED] wrote: > Date: Thu, 17 Jul 2008 15:44:56 -0400 > From: "C. Scott Ananian" <[EMAIL PROTECTED]> > Subject: Re: [sugar] Display warnings in sugar > To: "Tomeu Vizoso" <[EMAIL PROTECTED]> > Cc: devel@lists.laptop.org, Eben Eliason <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > On Thu, Jul 17, 2008 at 5:21 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: >> On Thu, Jul 17, 2008 at 2:27 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: >>> I hope our alert system will use the freedesktop.org standard: >>> http://www.galago-project.org/specs/notification/index.php >>> It is widely used in Gnome, and when I last reviewed it seems to be a >>> solid and capable spec. >> The interfaces in that spec look quite good, although perhaps would >> benefit from a simpler, alternative API that also abstracts the D-Bus >> stuff. Perhaps rainbow should do some rate limiting or permissions >> checking, not sure. > > Sure, wrap the actual DBus calls with a simplied sugar/python method > if you like, but *please* let's implement a listener for that API so > that unmodified applications can interact sensibly with Sugar, and so > that our system tools & activities can interoperate with non-Sugar > window managers. > > Similarly, we should really implement that standard freedesktop.org > startup notification spec, so we can get sensible notifications and > icons for 'ordinary' applications. > --scott > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
On Fri, Jul 18, 2008 at 2:53 AM, Gary C Martin <[EMAIL PROTECTED]> wrote: > Just out of interest, where is the code that raises the AP network > authentication name/pass request? That feels like a pretty close > template fit to such a critical warning. sugar/src/hardware/keydialog.py Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
On 17 Jul 2008, at 20:39, Michael Stone wrote: > On Thu, Jul 17, 2008 at 10:27:21AM -0300, Emiliano Pastorino wrote: > > Emiliano, > > I'm not sure of the right way to help you in the long term, but if you > want a quick hack, you might try something like: > > 1. Install a cronjob that runs every few minutes. > 2. When it runs, it should check the available space. > 3. If it concludes that space is low, pop up a warning. > > Warnings can be simple X or pygtk programs (see the 'dialog' > Linux > scripts for ideas). To get this hooked up to the running X > display, > you'll need to set some environment variables: > > DISPLAY=:0 > XAUTHORITY=/home/olpc/.Xauthority > > Ask if you need more help. Just out of interest, where is the code that raises the AP network authentication name/pass request? That feels like a pretty close template fit to such a critical warning. I must just say I'm not 100% convinced about how successful a warning will be (but it is better than nothing). I've hit the issue a couple of times and it was not some slow incremental case where I could take sensible action. Both times, as I recall, I was downloading some ~large library or binary which maxed out the space in one go before I realised the size. --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
On Thu, Jul 17, 2008 at 5:01 PM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 9:44 PM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: >> On Thu, Jul 17, 2008 at 5:21 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: >>> On Thu, Jul 17, 2008 at 2:27 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: I hope our alert system will use the freedesktop.org standard: http://www.galago-project.org/specs/notification/index.php It is widely used in Gnome, and when I last reviewed it seems to be a solid and capable spec. >>> >>> The interfaces in that spec look quite good, although perhaps would >>> benefit from a simpler, alternative API that also abstracts the D-Bus >>> stuff. Perhaps rainbow should do some rate limiting or permissions >>> checking, not sure. >> >> Sure, wrap the actual DBus calls with a simplied sugar/python method >> if you like, but *please* let's implement a listener for that API so >> that unmodified applications can interact sensibly with Sugar, and so >> that our system tools & activities can interoperate with non-Sugar >> window managers. >> >> Similarly, we should really implement that standard freedesktop.org >> startup notification spec, so we can get sensible notifications and >> icons for 'ordinary' applications. > > Yes, what you asked for is what we aim for ;) Yay! --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
On Thu, Jul 17, 2008 at 9:44 PM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 5:21 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: >> On Thu, Jul 17, 2008 at 2:27 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: >>> I hope our alert system will use the freedesktop.org standard: >>> http://www.galago-project.org/specs/notification/index.php >>> It is widely used in Gnome, and when I last reviewed it seems to be a >>> solid and capable spec. >> >> The interfaces in that spec look quite good, although perhaps would >> benefit from a simpler, alternative API that also abstracts the D-Bus >> stuff. Perhaps rainbow should do some rate limiting or permissions >> checking, not sure. > > Sure, wrap the actual DBus calls with a simplied sugar/python method > if you like, but *please* let's implement a listener for that API so > that unmodified applications can interact sensibly with Sugar, and so > that our system tools & activities can interoperate with non-Sugar > window managers. > > Similarly, we should really implement that standard freedesktop.org > startup notification spec, so we can get sensible notifications and > icons for 'ordinary' applications. Yes, what you asked for is what we aim for ;) Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
Thanks, Michael! I was just trying that, but I was missing the XAUTHORITY variable. I think that's going to do the job by now. On Thu, Jul 17, 2008 at 4:39 PM, Michael Stone <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 10:27:21AM -0300, Emiliano Pastorino wrote: > > Emiliano, > > I'm not sure of the right way to help you in the long term, but if you > want a quick hack, you might try something like: > > 1. Install a cronjob that runs every few minutes. 2. When it runs, it > should check the available space. 3. If it concludes that space is low, pop > up a warning. > > Warnings can be simple X or pygtk programs (see the 'dialog' Linux > scripts for ideas). To get this hooked up to the running X display, > you'll need to set some environment variables: > > DISPLAY=:0 > XAUTHORITY=/home/olpc/.Xauthority > > Ask if you need more help. > > Michael > -- Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 3724 int.: 469 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
On Thu, Jul 17, 2008 at 5:21 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 2:27 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: >> I hope our alert system will use the freedesktop.org standard: >> http://www.galago-project.org/specs/notification/index.php >> It is widely used in Gnome, and when I last reviewed it seems to be a >> solid and capable spec. > > The interfaces in that spec look quite good, although perhaps would > benefit from a simpler, alternative API that also abstracts the D-Bus > stuff. Perhaps rainbow should do some rate limiting or permissions > checking, not sure. Sure, wrap the actual DBus calls with a simplied sugar/python method if you like, but *please* let's implement a listener for that API so that unmodified applications can interact sensibly with Sugar, and so that our system tools & activities can interoperate with non-Sugar window managers. Similarly, we should really implement that standard freedesktop.org startup notification spec, so we can get sensible notifications and icons for 'ordinary' applications. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
On Thu, Jul 17, 2008 at 10:27:21AM -0300, Emiliano Pastorino wrote: Emiliano, I'm not sure of the right way to help you in the long term, but if you want a quick hack, you might try something like: 1. Install a cronjob that runs every few minutes. 2. When it runs, it should check the available space. 3. If it concludes that space is low, pop up a warning. Warnings can be simple X or pygtk programs (see the 'dialog' Linux scripts for ideas). To get this hooked up to the running X display, you'll need to set some environment variables: DISPLAY=:0 XAUTHORITY=/home/olpc/.Xauthority Ask if you need more help. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
On Thu, Jul 17, 2008 at 10:50 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: > Hi Emiliano, > > we have this right now: http://wiki.laptop.org/go/Designs/Frame#03 So > in the 8.2.0 release you can trust to have an indication of how much > space is available. > > About having a notification to popup when space runs low, you should > enter a enhancement request in trac. Perhaps too late to get in 8.2.0 > but could be in a later release for sure. Right, we absolutely need this. Hopefully in the future this will improve when we have robust backup/restore integrated with the Journal, so that old and unused Journal entries can "fall off" the machine over time and keep space free. We'll still need the alert, of course; the notification system just wasn't quite ready in time for 8.2.0. A ticket would be appreciated (assign to interface-design for now). Thanks! - Eben > > > Regards, > > Tomeu > > On Thu, Jul 17, 2008 at 3:27 PM, Emiliano Pastorino > <[EMAIL PROTECTED]> wrote: > > Thanks for all your answers. > > The thing is we're having some trouble here in Uruguay with xos that run > out > > of disk space. Kids download lots of activities, take lots of pictures > and > > videos and they manage to use all free space they have. When that > happens, > > it seems that sugar won't load in some cases or takes too long to do it. > > That's why we want to give some kind of warning when they have used, I > don't > > know, 95% of disk space or so, so they can delete some stuff before > > everything crashes. > > We'll try to figure out something, but help will be appreciated! > > > > On Thu, Jul 17, 2008 at 6:21 AM, Tomeu Vizoso <[EMAIL PROTECTED]> > wrote: > >> > >> On Thu, Jul 17, 2008 at 2:27 AM, C. Scott Ananian <[EMAIL PROTECTED]> > >> wrote: > >> > 2008/7/16 Eben Eliason <[EMAIL PROTECTED]>: > >> >> Two answers: > >> >> similar issues. This is going to be handled by the notification > >> >> system, > >> >> which is in its infancy in the upcoming 8.2 release, but should > mature > >> >> and > >> > > >> > I hope our alert system will use the freedesktop.org standard: > >> > http://www.galago-project.org/specs/notification/index.php > >> > It is widely used in Gnome, and when I last reviewed it seems to be a > >> > solid and capable spec. > >> > > >> > I believe that was the plan of record in previous conversations; I > >> > hope I'm not mistaken. > >> > >> What we have implemented now is some basic notifications generated and > >> consumed in the shell, so we haven't added any public API for now. > >> > >> The interfaces in that spec look quite good, although perhaps would > >> benefit from a simpler, alternative API that also abstracts the D-Bus > >> stuff. Perhaps rainbow should do some rate limiting or permissions > >> checking, not sure. > >> > >> Thanks for the comment, > >> > >> Tomeu > >> ___ > >> Devel mailing list > >> Devel@lists.laptop.org > >> http://lists.laptop.org/listinfo/devel > > > > > > > > -- > > Emiliano Pastorino > > LATU - Plan Ceibal > > Av. Italia 6201 CP: 11500, Montevideo, Uruguay > > Tel: (598 2) 601 3724 int.: 469 > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
Hi Emiliano, we have this right now: http://wiki.laptop.org/go/Designs/Frame#03 So in the 8.2.0 release you can trust to have an indication of how much space is available. About having a notification to popup when space runs low, you should enter a enhancement request in trac. Perhaps too late to get in 8.2.0 but could be in a later release for sure. Regards, Tomeu On Thu, Jul 17, 2008 at 3:27 PM, Emiliano Pastorino <[EMAIL PROTECTED]> wrote: > Thanks for all your answers. > The thing is we're having some trouble here in Uruguay with xos that run out > of disk space. Kids download lots of activities, take lots of pictures and > videos and they manage to use all free space they have. When that happens, > it seems that sugar won't load in some cases or takes too long to do it. > That's why we want to give some kind of warning when they have used, I don't > know, 95% of disk space or so, so they can delete some stuff before > everything crashes. > We'll try to figure out something, but help will be appreciated! > > On Thu, Jul 17, 2008 at 6:21 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: >> >> On Thu, Jul 17, 2008 at 2:27 AM, C. Scott Ananian <[EMAIL PROTECTED]> >> wrote: >> > 2008/7/16 Eben Eliason <[EMAIL PROTECTED]>: >> >> Two answers: >> >> similar issues. This is going to be handled by the notification >> >> system, >> >> which is in its infancy in the upcoming 8.2 release, but should mature >> >> and >> > >> > I hope our alert system will use the freedesktop.org standard: >> > http://www.galago-project.org/specs/notification/index.php >> > It is widely used in Gnome, and when I last reviewed it seems to be a >> > solid and capable spec. >> > >> > I believe that was the plan of record in previous conversations; I >> > hope I'm not mistaken. >> >> What we have implemented now is some basic notifications generated and >> consumed in the shell, so we haven't added any public API for now. >> >> The interfaces in that spec look quite good, although perhaps would >> benefit from a simpler, alternative API that also abstracts the D-Bus >> stuff. Perhaps rainbow should do some rate limiting or permissions >> checking, not sure. >> >> Thanks for the comment, >> >> Tomeu >> ___ >> Devel mailing list >> Devel@lists.laptop.org >> http://lists.laptop.org/listinfo/devel > > > > -- > Emiliano Pastorino > LATU - Plan Ceibal > Av. Italia 6201 CP: 11500, Montevideo, Uruguay > Tel: (598 2) 601 3724 int.: 469 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
Thanks for all your answers. The thing is we're having some trouble here in Uruguay with xos that run out of disk space. Kids download lots of activities, take lots of pictures and videos and they manage to use all free space they have. When that happens, it seems that sugar won't load in some cases or takes too long to do it. That's why we want to give some kind of warning when they have used, I don't know, 95% of disk space or so, so they can delete some stuff before everything crashes. We'll try to figure out something, but help will be appreciated! On Thu, Jul 17, 2008 at 6:21 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 2:27 AM, C. Scott Ananian <[EMAIL PROTECTED]> > wrote: > > 2008/7/16 Eben Eliason <[EMAIL PROTECTED]>: > >> Two answers: > >> similar issues. This is going to be handled by the notification system, > >> which is in its infancy in the upcoming 8.2 release, but should mature > and > > > > I hope our alert system will use the freedesktop.org standard: > > http://www.galago-project.org/specs/notification/index.php > > It is widely used in Gnome, and when I last reviewed it seems to be a > > solid and capable spec. > > > > I believe that was the plan of record in previous conversations; I > > hope I'm not mistaken. > > What we have implemented now is some basic notifications generated and > consumed in the shell, so we haven't added any public API for now. > > The interfaces in that spec look quite good, although perhaps would > benefit from a simpler, alternative API that also abstracts the D-Bus > stuff. Perhaps rainbow should do some rate limiting or permissions > checking, not sure. > > Thanks for the comment, > > Tomeu > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > -- Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 3724 int.: 469 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
On Thu, Jul 17, 2008 at 2:27 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: > 2008/7/16 Eben Eliason <[EMAIL PROTECTED]>: >> Two answers: >> similar issues. This is going to be handled by the notification system, >> which is in its infancy in the upcoming 8.2 release, but should mature and > > I hope our alert system will use the freedesktop.org standard: > http://www.galago-project.org/specs/notification/index.php > It is widely used in Gnome, and when I last reviewed it seems to be a > solid and capable spec. > > I believe that was the plan of record in previous conversations; I > hope I'm not mistaken. What we have implemented now is some basic notifications generated and consumed in the shell, so we haven't added any public API for now. The interfaces in that spec look quite good, although perhaps would benefit from a simpler, alternative API that also abstracts the D-Bus stuff. Perhaps rainbow should do some rate limiting or permissions checking, not sure. Thanks for the comment, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
2008/7/16 Eben Eliason <[EMAIL PROTECTED]>: > Two answers: > similar issues. This is going to be handled by the notification system, > which is in its infancy in the upcoming 8.2 release, but should mature and I hope our alert system will use the freedesktop.org standard: http://www.galago-project.org/specs/notification/index.php It is widely used in Gnome, and when I last reviewed it seems to be a solid and capable spec. I believe that was the plan of record in previous conversations; I hope I'm not mistaken. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
Hi Emliano, Thanks a lot for your input and questions. The next release is called 8.2.0 and the features in it are being slowly documented at: http://wiki.laptop.org/go/Release_Notes/8.2.0 That page is subject to change and may contain errors. However, it has some good links and pictures of coming GUI changes. Take a look at that and let us know if it is close to what you need or if you have any suggestions or questions. Eben's link has a lot of good info but not all the screen shots will be implemented in 8.2.0. Make sure to check back before assuming everything is in. Let us know what is important to you, what you like and what you don't like. Uruguay is our biggest deployment right now so we will act as quickly as possible on your feedback. Thanks, Greg Smith OLPC Product Manager PS Lo siento que no nos conocimos cuando usted estuvo en Cambridge. Estoy a su servicio en qualquier que necesita. *** From: "Eben Eliason" <[EMAIL PROTECTED]> Subject: Re: [sugar] Display warnings in sugar To: "Erik Garrison" <[EMAIL PROTECTED]> Cc: devel@lists.laptop.org, [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" Two answers: 1. We absolutely need stronger feedback (actually, feedback at all) for system state, such as disk space, battery level, network failures, and other similar issues. This is going to be handled by the notification system, which is in its infancy in the upcoming 8.2 release, but should mature and actually be taken advantage of by the following one. For more information, see http://wiki.laptop.org/go/Designs/Frame#12. We may later extend the notification system so that activities, too, can notify the user when necessary, even if they aren't presently focused. 2. We do already have some facilities in place to replace standard "dialogs". There is an Alert class (and a few subclasses) defined which activities can use to show non-modal alerts and prompt for feedback. There are also going to be modal alerts (like the control panel, the object chooser, and others), but I'm not sure those have been wrapped up into a class for activities to use at this point. Cloning code from one of those modal alerts might be a fair short term solution in "extreme" cases (such as running out of disk space). - Eben On Wed, Jul 16, 2008 at 4:13 PM, Erik Garrison <[EMAIL PROTECTED]> wrote: > > This is a problem that all XOs face. > > > > Ultimately we should produce a shared solution and push the fix into > > Sugar. I believe there has been some discussion of this? > > > > The problem is getting that fix back out to deployed laptops may not be > > easy... > > > > My 2c. Maybe the XO character in the home view could flash when > > something this serious is wrong. > > > > On Wed, Jul 16, 2008 at 04:53:00PM -0300, Emiliano Pastorino wrote: >> > > Hi, everyone! >> > > >> > > I was wondering if is there a way to open a popup or something like that > > in >> > > sugar, we want to use that or something similar to give warnings to the >> > > user, like "95% of disk space used". >> > > >> > > Thanks! >> > > >> > > -- >> > > Emiliano Pastorino >> > > LATU - Plan Ceibal >> > > Av. Italia 6201 CP: 11500, Montevideo, Uruguay >> > > Tel: (598 2) 601 3724 int.: 469 > > >> > > ___ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
Two answers: 1. We absolutely need stronger feedback (actually, feedback at all) for system state, such as disk space, battery level, network failures, and other similar issues. This is going to be handled by the notification system, which is in its infancy in the upcoming 8.2 release, but should mature and actually be taken advantage of by the following one. For more information, see http://wiki.laptop.org/go/Designs/Frame#12. We may later extend the notification system so that activities, too, can notify the user when necessary, even if they aren't presently focused. 2. We do already have some facilities in place to replace standard "dialogs". There is an Alert class (and a few subclasses) defined which activities can use to show non-modal alerts and prompt for feedback. There are also going to be modal alerts (like the control panel, the object chooser, and others), but I'm not sure those have been wrapped up into a class for activities to use at this point. Cloning code from one of those modal alerts might be a fair short term solution in "extreme" cases (such as running out of disk space). - Eben On Wed, Jul 16, 2008 at 4:13 PM, Erik Garrison <[EMAIL PROTECTED]> wrote: > This is a problem that all XOs face. > > Ultimately we should produce a shared solution and push the fix into > Sugar. I believe there has been some discussion of this? > > The problem is getting that fix back out to deployed laptops may not be > easy... > > My 2c. Maybe the XO character in the home view could flash when > something this serious is wrong. > > On Wed, Jul 16, 2008 at 04:53:00PM -0300, Emiliano Pastorino wrote: > > Hi, everyone! > > > > I was wondering if is there a way to open a popup or something like that > in > > sugar, we want to use that or something similar to give warnings to the > > user, like "95% of disk space used". > > > > Thanks! > > > > -- > > Emiliano Pastorino > > LATU - Plan Ceibal > > Av. Italia 6201 CP: 11500, Montevideo, Uruguay > > Tel: (598 2) 601 3724 int.: 469 > > > ___ > > Sugar mailing list > > [EMAIL PROTECTED] > > http://lists.laptop.org/listinfo/sugar > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Display warnings in sugar
This is a problem that all XOs face. Ultimately we should produce a shared solution and push the fix into Sugar. I believe there has been some discussion of this? The problem is getting that fix back out to deployed laptops may not be easy... My 2c. Maybe the XO character in the home view could flash when something this serious is wrong. On Wed, Jul 16, 2008 at 04:53:00PM -0300, Emiliano Pastorino wrote: > Hi, everyone! > > I was wondering if is there a way to open a popup or something like that in > sugar, we want to use that or something similar to give warnings to the > user, like "95% of disk space used". > > Thanks! > > -- > Emiliano Pastorino > LATU - Plan Ceibal > Av. Italia 6201 CP: 11500, Montevideo, Uruguay > Tel: (598 2) 601 3724 int.: 469 > ___ > Sugar mailing list > [EMAIL PROTECTED] > http://lists.laptop.org/listinfo/sugar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Display warnings in sugar
Hi, everyone! I was wondering if is there a way to open a popup or something like that in sugar, we want to use that or something similar to give warnings to the user, like "95% of disk space used". Thanks! -- Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 3724 int.: 469 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
