After PA shell crash, booting takes a long time

[Lamarque V. Souza]

Em Monday 05 November 2012, David Talmage escreveu:
> On Monday, November 05, 2012 08:23:07 PM Lamarque V. Souza wrote:
> > Em Monday 05 November 2012, David Talmage escreveu:
> > > On Saturday, November 03, 2012 02:40:26 PM Lamarque V. Souza wrote:
> > > > Em Saturday 03 November 2012, David Talmage escreveu:
> > > > > On Saturday, November 03, 2012 01:25:29 AM Lamarque V. Souza wrote:
> > > > > > Em Friday 02 November 2012, David Talmage escreveu:
> > > > > > > I need help figuring this out.  My PA3 WeTab now takes 15
> > > > > > > minutes to boot to a usable state.  Even then, it's not as
> > > > > > > responive as it used to be. ...
> > > > > > > What can I do to debug this?  Should I forget about it and
> > > > > > > reinstall PA3?
> > > > > > 	
> > > > > > 	Send us the ~/.xsession-errors files and the crashlog if you
> > > > > > 	still
> > > > > 
> > > > > ...
> > > > 
> > > > ...
> > > 
> > > ...
> > 	
> > 	Did you compact your tarball backup? 5.9 GB of compacted data is a lot
> > 
> > of thing.
> 
> Most of it was JPEG files so I didn't bother to try compressing it.
> 
> > > Things were so messed up on my WeTab that I had to mount the drive
> > > using 'mount'.
> > 	
> > 	It's a pitty you were not able to save a log of what went wrong. More
> > 
> > and more I think it was a filesystem corruption.
> 
> I agree.  There was no .xsession-errors in my home directory or in /tmp or
> /var/tmp.  I looked at every file in /tmp and /var/tmp.
> 
> Even now, with the fresh installation of PA3, I have no ~/.xsession-errors.

	Hmmm yes, I have just checked it and there is no ~/.xsession-errors 
anymore. Its contents is going to /tmp/startactive-mer.log by what I can see 
here.

-- 
Lamarque V. Souza
Software Engineer (basyskom.com)
Nokia Certified Qt Specialist
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/active/attachments/20121105/ce56c265/attachment-0001.html>