[Sugar-devel] [DESIGN] Re: #1842 UNSP: Journal does not provide any error message on write errors
Aleksey Lim
alsroot at member.fsf.org
Mon Jul 12 10:23:27 EDT 2010
On Mon, Jul 12, 2010 at 12:25:17PM +0000, Aleksey Lim wrote:
> ----- Forwarded message from Sugar Labs Bugs <bugtracker-noreply at sugarlabs.org> -----
>
> From: Sugar Labs Bugs <bugtracker-noreply at sugarlabs.org>
> Subject: Re: #1842 UNSP: Journal does not provide any error message on write
> errors
> Cc: bugs at lists.sugarlabs.org
> Reply-To: sugar-devel at lists.sugarlabs.org
> Date: Mon, 12 Jul 2010 12:23:33 -0000
>
> #1842: Journal does not provide any error message on write errors
> ------------------------------------------+---------------------------------
> Reporter: bernie | Owner: alsroot
> Type: defect | Status: assigned
> Priority: Unspecified by Maintainer | Milestone: Unspecified by Release Team
> Component: sugar | Version: 0.84.x
> Severity: Unspecified | Keywords: journal, sugar-love, dev-love, r?
> Distribution: Unspecified | Status_field: Needinfo
> ------------------------------------------+---------------------------------
> Changes (by alsroot):
>
> * status_field: Unconfirmed => Needinfo
>
>
> Comment:
>
> Patch uses NotifyRedAlert but it is not part of sugar-toolkit i.e. code
> won't work, what about just NotifyAlert and switch to red one later?
outdated, new patch[1] uses ErrorAlert
> Also, patch uses _('Alert') for alert title, could be not so informative
> :), what about just "Disk storage error"?
outdated as well
> volumestoolbar.py emits volume-error signal with error text taken from
> exception, not sure if it is a good idea to pass it directly to user
> visible message?
>
> any ideas?
[1] http://people.sugarlabs.org/anish/0001-Journal-show-error-message-on-write-failure-1842.patch
--
Aleksey
More information about the Sugar-devel
mailing list