[Sugar-devel] Problems with Read Activity on XO

2009-11-04 Thread Jim Simmons
Sayamindu,

I've been having an odd problem with the Read activity on my XO
lately.  I'd report it as a bug but I don't know how to recreate it or
give enough information to see where the problem is coming from.  I'm
hoping you can help me diagnose what's happening.

You might remember giving me a version of Read that worked better with
DJVU files.  I uninstalled the original Read and used that one
successfully for a couple of months at least.  One day, for no reason
I can see, it stopped coming up.  You'd see the pulsing book icon for
a few minutes, then nothing.  I'd bring up the Log activity and there
would be an entry for Read but it would contain no messages whatever.
Totally empty.  I've seen my own Activities fail any number of times
while they were in development but I always got *some* messages, even
if they weren't very helpful.

I removed the Read activity from the Journal then used the Software
Update dialog to reinstall the original Read.  It apparently did so.
However, when I test it with a PDF it shows exactly the same symptoms
as the other one did.

Everything else on my XO seems to work just fine, so I'm stumped.  If
you have any ideas on things I could look at to resolve this I'd
appreciate it.

Thanks,

James Simmons
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Problems with Read Activity on XO

2009-11-04 Thread Sayamindu Dasgupta
It may be possible is something is segfaulting (I vaguely remember
seeing something like this). dmesg usually keeps track of things that
segfault, and you can also take a look at shell.log

Another way would be to use the Terminal:
sugar-launch org.laptop.sugar.ReadActivity

Thanks,
Sayamindu


On Wed, Nov 4, 2009 at 10:47 PM, Jim Simmons nices...@gmail.com wrote:
 Sayamindu,

 I've been having an odd problem with the Read activity on my XO
 lately.  I'd report it as a bug but I don't know how to recreate it or
 give enough information to see where the problem is coming from.  I'm
 hoping you can help me diagnose what's happening.

 You might remember giving me a version of Read that worked better with
 DJVU files.  I uninstalled the original Read and used that one
 successfully for a couple of months at least.  One day, for no reason
 I can see, it stopped coming up.  You'd see the pulsing book icon for
 a few minutes, then nothing.  I'd bring up the Log activity and there
 would be an entry for Read but it would contain no messages whatever.
 Totally empty.  I've seen my own Activities fail any number of times
 while they were in development but I always got *some* messages, even
 if they weren't very helpful.

 I removed the Read activity from the Journal then used the Software
 Update dialog to reinstall the original Read.  It apparently did so.
 However, when I test it with a PDF it shows exactly the same symptoms
 as the other one did.

 Everything else on my XO seems to work just fine, so I'm stumped.  If
 you have any ideas on things I could look at to resolve this I'd
 appreciate it.

 Thanks,

 James Simmons




-- 
Sayamindu Dasgupta
[http://sayamindu.randomink.org/ramblings]
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Problems with Read Activity on XO

2009-11-04 Thread Jim Simmons
Sayamindu,

Didn't see any evidence of segfault in dmesg or shell.log.  However, I
tried out:

sugar-launch org.laptop.sugar.ReadActivity

and it worked beautifully.  Read gave me that ugly dialog that lets
you select a document from the Journal, I selected one of the PDFs,
and it loaded right up.  Everything worked just fine, and it created a
Journal entry called Unknown with the Read icon on it.  When I try
to resume from the Journal, either the new entry or one of the
original PDFs, I get the symptoms I described before.

I *might* be able to launch Read from the Activity Ring.  I turned off
my XO and put it away before I thought to try it.  (I'm at work).

So it looks to me that there is nothing wrong with Read itself, but
there might be something wrong with how its installed.

Thanks,

James Simmons


On Wed, Nov 4, 2009 at 2:09 PM, Sayamindu Dasgupta sayami...@gmail.com wrote:
 It may be possible is something is segfaulting (I vaguely remember
 seeing something like this). dmesg usually keeps track of things that
 segfault, and you can also take a look at shell.log

 Another way would be to use the Terminal:
 sugar-launch org.laptop.sugar.ReadActivity

 Thanks,
 Sayamindu
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Problems with Read Activity on XO

2009-11-04 Thread Jim Simmons
Sayamindu,

FYI, Read can't be launched from my Activity Ring either.  The only
thing that works is the sugar-launch from the Terminal.

James Simmons


On Wed, Nov 4, 2009 at 3:05 PM, Jim Simmons nices...@gmail.com wrote:
 Sayamindu,

 Didn't see any evidence of segfault in dmesg or shell.log.  However, I
 tried out:

 sugar-launch org.laptop.sugar.ReadActivity

 and it worked beautifully.  Read gave me that ugly dialog that lets
 you select a document from the Journal, I selected one of the PDFs,
 and it loaded right up.  Everything worked just fine, and it created a
 Journal entry called Unknown with the Read icon on it.  When I try
 to resume from the Journal, either the new entry or one of the
 original PDFs, I get the symptoms I described before.

 I *might* be able to launch Read from the Activity Ring.  I turned off
 my XO and put it away before I thought to try it.  (I'm at work).

 So it looks to me that there is nothing wrong with Read itself, but
 there might be something wrong with how its installed.

 Thanks,

 James Simmons


 On Wed, Nov 4, 2009 at 2:09 PM, Sayamindu Dasgupta sayami...@gmail.com 
 wrote:
 It may be possible is something is segfaulting (I vaguely remember
 seeing something like this). dmesg usually keeps track of things that
 segfault, and you can also take a look at shell.log

 Another way would be to use the Terminal:
 sugar-launch org.laptop.sugar.ReadActivity

 Thanks,
 Sayamindu

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel