[Bugs] #1403 UNSP: shell breaks if system bus cannot be accessed

[Sugar Labs Bugs]

#1403: shell breaks if system bus cannot be accessed
------------------------------------------+---------------------------------
    Reporter:  sascha_silbe               |          Owner:  sascha_silbe               
        Type:  defect                     |         Status:  accepted                   
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar                      |        Version:  Git as of bugdate          
    Severity:  Major                      |       Keywords:  r?                         
Distribution:  Unspecified                |   Status_field:  New                        
------------------------------------------+---------------------------------

Comment(by tomeu):

 Replying to [comment:5 sascha_silbe]:
 > Replying to [comment:4 tomeu]:
 > > Agreed, but shouldn't we be testing on an environment closer to that
 of our users?
 > Where possible we should, of course. But the alternative here is no
 testing at all on some systems.

 So we cannot run or connect to the system bus on those systems?

 > I'd like to see as much testing as possible on ''all'' levels, from
 automated (unit/regression) tests up to manual testing on "real" systems
 (not KVM/qemu). The more bugs we catch on lower levels, the less work our
 human testers need to do.
 >
 > The test suite for datastore (will be submitted for review soon) and the
 patch we're talking about already enabled me to find (and fix) several
 bugs. IMO that's well worth it.
 > Unless there's a bug in my patch, the only effect will be that instead
 of all of Sugar not working, only the features relying on the system bus
 will be disabled. That's easily recognizable and the exceptions are always
 in the logs, so discovering the reason for it isn't hard either. Reading
 logs is already required if the system bus is reachable, but the
 individual services are not, so to the (non-chroot) user it doesn't make a
 real difference.
 > Even if there is a bug in my patch, that's well ofset by the bugs it
 enabled me to find. :)

 I don;t think it's a big deal in this concrete patch, but if we need to
 make all Sugar features "degrade gracefully", do you see the amount of
 code we'll need to change and add? That's why I'm asking these questions.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/1403#comment:6>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system