Re: [gentoo-user] KDE Very Slow - Failed Sleep Command

2006-04-13 Thread Teresa and Dale
Lord Sauron wrote:

On 4/12/06, Teresa and Dale [EMAIL PROTECTED] wrote:
  

My light blew out on one of my servers.  No smoke but still no workey.
:-(  I have to use top instead.  Since the drive is so old, I can hear
it with no problems at all.



A new LED and a soddering iron and you could fix it...

--
== GCv3.12 ==
GCS d-(++) s+: a? C++ UL+ P+
L++ E--- W+(+++) N++ o? K? w--- O? M+
V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+
DI+++ D+ G e* h- !r !y
= END GCv3.12 

  


Naaa.  I don't look at it much anyway.  As long as it lets me ssh in, I
know it is working.  I even had another thought, what if I plugged the
cable up backwards.  O_O  I have done that before.   hangs head in shame 

Dale
:-)
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE Very Slow - Failed Sleep Command

2006-04-12 Thread Hemmann, Volker Armin
On Wednesday 12 April 2006 01:45, Lord Sauron wrote:
 Hello,

 This happened once before in Kubuntu, though this time I was more
 alert and know what I did right before this happened.  So what did
 transpire?

 I sent my laptop into sleep mode via the popup menu on the battery
 monitor in KDE.  It did this, however, when the machine came out of
 sleep mode, there was no monitor.  It wasn't on.  I tried my basic set
 of tricks: try and change the screen brightness; try and switch
 monitors via the key combo on the laptop; close the lid and re-open
 it; press the key combo to turn the monitor off; press the key combo
 to go back to sleep mode (didn't work).

 Eventually I picked a button that did work: POWER.  The system shut
 down normally!  After X11 died, it went back the the framebuffer and
 acted like nothing had happened.

 However, right after this, KDE has been acting *really* slow.  Much
 slower than it should.  # top revealed that artsd, xorg, and kded were
 eating cpu time.  This is the same behaviour as on Kubuntu before.  I
 suspect the cause was the same, however, I don't remember exactly so I
 won't point fingers.

 Do any of you know what this is?  Do you think if I recompiled xorg,
 kde, and arts if it'd fix the problem?  Or, even better, is there a
 way to axe all the configuration settings and see if that fixes the
 problem?  Please help, I think it's affecting Gnome as well (scary!)

recompiling will fix NOTHING.

There are a lot of temporary files in /tmp and ~ / remove them and see if the 
problem is still there.
All KDE related configs are in ~/.kde3.5 (.kde3.4), so (re)moving that sets 
KDE back to its 'fresh' state.
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE Very Slow - Failed Sleep Command

2006-04-12 Thread Martins Steinbergs
On Wednesday 12 April 2006 22:59, Hemmann, Volker Armin wrote:
 On Wednesday 12 April 2006 01:45, Lord Sauron wrote:
  Hello,
 
  This happened once before in Kubuntu, though this time I was more
  alert and know what I did right before this happened.  So what did
  transpire?
 
  I sent my laptop into sleep mode via the popup menu on the battery
  monitor in KDE.  It did this, however, when the machine came out of
  sleep mode, there was no monitor.  It wasn't on.  I tried my basic set
  of tricks: try and change the screen brightness; try and switch
  monitors via the key combo on the laptop; close the lid and re-open
  it; press the key combo to turn the monitor off; press the key combo
  to go back to sleep mode (didn't work).
 
  Eventually I picked a button that did work: POWER.  The system shut
  down normally!  After X11 died, it went back the the framebuffer and
  acted like nothing had happened.
 
  However, right after this, KDE has been acting *really* slow.  Much
  slower than it should.  # top revealed that artsd, xorg, and kded were
  eating cpu time.  This is the same behaviour as on Kubuntu before.  I
  suspect the cause was the same, however, I don't remember exactly so I
  won't point fingers.
 
  Do any of you know what this is?  Do you think if I recompiled xorg,
  kde, and arts if it'd fix the problem?  Or, even better, is there a
  way to axe all the configuration settings and see if that fixes the
  problem?  Please help, I think it's affecting Gnome as well (scary!)

 recompiling will fix NOTHING.

 There are a lot of temporary files in /tmp and ~ / remove them and see if
 the problem is still there.
 All KDE related configs are in ~/.kde3.5 (.kde3.4), so (re)moving that sets
 KDE back to its 'fresh' state.

read ~/.xsession-errors
maybe some hint there, once i had that file fill free space on /home with few 
GB 'cause busy filling errors

before start KDE also try remove previous session saves, maybe there some 
sassion saved in bad state
rm ~/.kde/share/config/session/*


-- 
Linux 2.6.15-ck7 AMD Athlon(tm) 64 Processor 3200+
 23:11:49 up 13:44,  4 users,  load average: 0.00, 0.11, 0.17
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE Very Slow - Failed Sleep Command

2006-04-12 Thread Teresa and Dale
Martins Steinbergs wrote:



read ~/.xsession-errors
maybe some hint there, once i had that file fill free space on /home with few 
GB 'cause busy filling errors

before start KDE also try remove previous session saves, maybe there some 
sassion saved in bad state
rm ~/.kde/share/config/session/*


  


You might also want to use top to see what, if anything, is using up
your CPU time.  Also keep in mind that if the CPU is fairly idle that
the hard drive may be busy as well.  I ran into this once before on a
really slow system and it was the updatedb program.  It was nice'd
correctly but that doesn't apply to the hard drive.  I read earlier that
they are working on that too though.

Just a thought.

Dale
:-)  :-)
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE Very Slow - Failed Sleep Command

2006-04-12 Thread Lord Sauron
On 4/12/06, Hemmann, Volker Armin [EMAIL PROTECTED] wrote:
 On Wednesday 12 April 2006 01:45, Lord Sauron wrote:
  Hello,
 
  This happened once before in Kubuntu, though this time I was more
  alert and know what I did right before this happened.  So what did
  transpire?
 
  I sent my laptop into sleep mode via the popup menu on the battery
  monitor in KDE.  It did this, however, when the machine came out of
  sleep mode, there was no monitor.  It wasn't on.  I tried my basic set
  of tricks: try and change the screen brightness; try and switch
  monitors via the key combo on the laptop; close the lid and re-open
  it; press the key combo to turn the monitor off; press the key combo
  to go back to sleep mode (didn't work).
 
  Eventually I picked a button that did work: POWER.  The system shut
  down normally!  After X11 died, it went back the the framebuffer and
  acted like nothing had happened.
 
  However, right after this, KDE has been acting *really* slow.  Much
  slower than it should.  # top revealed that artsd, xorg, and kded were
  eating cpu time.  This is the same behaviour as on Kubuntu before.  I
  suspect the cause was the same, however, I don't remember exactly so I
  won't point fingers.
 
  Do any of you know what this is?  Do you think if I recompiled xorg,
  kde, and arts if it'd fix the problem?  Or, even better, is there a
  way to axe all the configuration settings and see if that fixes the
  problem?  Please help, I think it's affecting Gnome as well (scary!)

 recompiling will fix NOTHING.

If the filesystem got corrupted it might do something... though in
retrospect not likely.

 There are a lot of temporary files in /tmp and ~ / remove them and see if the
 problem is still there.

Actually, I did # top and took a closer look...  my pagefile wasn't
mounted.  I fixed that...  I think a hibernate command axed the swap
partition.  mkswap and swapon then fixed that problem.  Oh well... 
it's what you get for toying with the (highly-experimental) ACPI
stuff.

 All KDE related configs are in ~/.kde3.5 (.kde3.4), so (re)moving that sets
 KDE back to its 'fresh' state.

Luckily I won't have to do that yet!  Back when I was using Kubuntu I
didn't know about mkswap and swapon, so I was rather mystified. 
However, I'm really happy I was able to find the problem.  Shows I'm
learning something : )

--
== GCv3.12 ==
GCS d-(++) s+: a? C++ UL+ P+
L++ E--- W+(+++) N++ o? K? w--- O? M+
V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+
DI+++ D+ G e* h- !r !y
= END GCv3.12 

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE Very Slow - Failed Sleep Command

2006-04-12 Thread Lord Sauron
On 4/12/06, Teresa and Dale [EMAIL PROTECTED] wrote:
 Martins Steinbergs wrote:

 
 
 read ~/.xsession-errors
 maybe some hint there, once i had that file fill free space on /home with few
 GB 'cause busy filling errors

Yeah, I'll be looking in there shortly to see if there's any residual problems.

 before start KDE also try remove previous session saves, maybe there some
 sassion saved in bad state
 rm ~/.kde/share/config/session/*

I'll be doing that too.

 You might also want to use top to see what, if anything, is using up
 your CPU time.  Also keep in mind that if the CPU is fairly idle that
 the hard drive may be busy as well.  I ran into this once before on a
 really slow system and it was the updatedb program.  It was nice'd
 correctly but that doesn't apply to the hard drive.  I read earlier that
 they are working on that too though.

On my laptop, it used to be (under the tyranny of the 350meg windows
pagefile) that if the hard drive lit up the system was busy.  Under
linux if the cpu lights up it's busy.  It's a nice change.  The hard
drive for the X40 is so darn slow...

--
== GCv3.12 ==
GCS d-(++) s+: a? C++ UL+ P+
L++ E--- W+(+++) N++ o? K? w--- O? M+
V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+
DI+++ D+ G e* h- !r !y
= END GCv3.12 

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] KDE Very Slow - Failed Sleep Command

2006-04-12 Thread Teresa and Dale
Lord Sauron wrote:

You might also want to use top to see what, if anything, is using up
your CPU time.  Also keep in mind that if the CPU is fairly idle that
the hard drive may be busy as well.  I ran into this once before on a
really slow system and it was the updatedb program.  It was nice'd
correctly but that doesn't apply to the hard drive.  I read earlier that
they are working on that too though.



On my laptop, it used to be (under the tyranny of the 350meg windows
pagefile) that if the hard drive lit up the system was busy.  Under
linux if the cpu lights up it's busy.  It's a nice change.  The hard
drive for the X40 is so darn slow...

--
== GCv3.12 ==
GCS d-(++) s+: a? C++ UL+ P+
L++ E--- W+(+++) N++ o? K? w--- O? M+
V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+
DI+++ D+ G e* h- !r !y
= END GCv3.12 

  


My light blew out on one of my servers.  No smoke but still no workey. 
:-(  I have to use top instead.  Since the drive is so old, I can hear
it with no problems at all.

Dale
:-)
-- 
gentoo-user@gentoo.org mailing list