27 Jul
2015
27 Jul
'15
11:13 a.m.
Hi all,
in the recent weeks I am experiencing serious stability issues on two of my machines
running KDE
3. I know KDE 3 is not Trinity and whatever the causes are they might be fixed in Trinity,
but
nevertheless I believe that the debugging techniques are identical for KDE and Trinity.
That's
why I'm asking for help here.
Machine 1
On first of my machines I am experiencing random desktop freezes around two times a day
(this
started around 2 weeks ago). When this happens the current application becomes
irresponsive and I
am unable to switch to different application by using Alt-tab or by clicking on the task
bar. I
am able to kill the graphical environment using Ctrl-Alt-Backspace or go to text console
(Ctrl-Alt-F1) to kill tasks. I was unable to find any program that, when killed, would
unfreeze
the desktop. The only puzzling thing is that killing Firefox seems to make it a zombie
process.
Machine 2
That machine experiences random problems when loading the desktop after login. The problem
manifests itself with an error message from KDE panel saying
that "'/home/USER/.local/share/applications/foo.desktop' service is
broken" (where foo is an
application like Skype, Firefox, etc.) and then the KDE panel becomes irresponsive. Again,
this
is random and sometimes the desktop loads correctly.
In both cases I have no idea how to debug the encountered problems. Are there any logs
that could
point me the source of the problems? Are there any diagnostics that I could run? Any ideas
appreciated as I fell clueless.
Janek
---
Politechnika Łódzka
Lodz University of Technology
Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata.
Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę
prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.
This email contains information intended solely for the use of the individual to whom it
is addressed.
If you are not the intended recipient or if you have received this message in error,
please notify the sender and delete it from your system.
27 Jul
27 Jul
11:59 a.m.
New subject: [trinity-users] Debugging stability
Am Montag, 27. Juli 2015 schrieb Jan Stolarek:
Hi all,
in the recent weeks I am experiencing serious stability issues on two of my machines
running KDE
3. I know KDE 3 is not Trinity and whatever the causes are they might be fixed in
Trinity, but
nevertheless I believe that the debugging techniques are identical for KDE and Trinity.
That's
why I'm asking for help here.
Machine 1
On first of my machines I am experiencing random desktop freezes around two times a day
(this
started around 2 weeks ago). When this happens the current application becomes
irresponsive and I
am unable to switch to different application by using Alt-tab or by clicking on the task
bar. I
am able to kill the graphical environment using Ctrl-Alt-Backspace or go to text console
(Ctrl-Alt-F1) to kill tasks. I was unable to find any program that, when killed, would
unfreeze
the desktop. The only puzzling thing is that killing Firefox seems to make it a zombie
process.
Machine 2
That machine experiences random problems when loading the desktop after login. The
problem
manifests itself with an error message from KDE panel saying
that "'/home/USER/.local/share/applications/foo.desktop' service is
broken" (where foo is an
application like Skype, Firefox, etc.) and then the KDE panel becomes irresponsive.
Again, this
is random and sometimes the desktop loads correctly.
In both cases I have no idea how to debug the encountered problems. Are there any logs
that could
point me the source of the problems? Are there any diagnostics that I could run? Any
ideas
appreciated as I fell clueless.
Janek
Hi!
You checked your hardware and it's OK?
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
8:10 p.m.
New subject: [trinity-users] Debugging stability
You checked your hardware and it's OK?
No, I
have not checked. In the case of first machine I'm nearly 100% certain that this is
not the
fault of the hardware. I'm not so sure about the second machine - it's an old
computer and it has
experienced minor hardware problems. Not sure what exactly I should check and how should I
do it.
I was thinking about running hard-disk checks - if anyone can recommend good program for
doing
that it would be great.
Still, are there any KDE logs that could be helpful in searching for the cause?
Janek
---
Politechnika Łódzka
Lodz University of Technology
Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata.
Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę
prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.
This email contains information intended solely for the use of the individual to whom it
is addressed.
If you are not the intended recipient or if you have received this message in error,
please notify the sender and delete it from your system.
9:27 p.m.
New subject: [trinity-users] Debugging stability
On 07/27/2015 01:10 PM, Jan Stolarek wrote:
I was thinking about running hard-disk checks - if
anyone can recommend
good program for doing that it would be great.
It doesn't sound like hard disk problems to me, but it's good to keep an eye
on the condition of your drives. With smartctl (package smartmontools) you
can see all the S.M.A.R.T. info, error logs, etc. and run the drive's
selftests. Use badblocks to do a surface scan of drives or partitions.
--
PGP key: http://homestead-products.com/pubkey.htm
9:47 p.m.
New subject: [trinity-users] Debugging stability
From: jan.stolarek(a)p.lodz.pl
To: trinity-users(a)lists.pearsoncomputing.net
Date: Mon, 27 Jul 2015 22:10:20 +0200
CC: office(a)klepp.biz
Subject: Re: [trinity-users] Debugging stability
Hi,
To test a computer's reliability, a good test is to run memtest86+ on it.
You can download the iso and burn it to a disc, or it often comes as one of the options on
the grub menu of many livecds. If after 10-15 minutes you see no red on your screen, the
you can be sure that the path between the cpu-chipset-ram is good to go.
Remember also that older TDE releases (such as 3.5.13.2) and old KDE3 is not thread-safe.
This means that on multi-cores computers, troubles may happen where an app is waiting on
another and it creates lock-ups. My Asus EEE X101CH is a special case where I had many
thread lock issues. Most of these has been solved on newer TDE releases (such as the
soon-to-be-released R14.01).
Hope it helps!
-Alexandre
You checked your hardware and it's OK?
No, I have not checked. In the case of first machine I'm nearly 100% certain that this
is not the
fault of the hardware. I'm not so sure about the second machine - it's an old
computer and it has
experienced minor hardware problems. Not sure what exactly I should check and how should
I do it.
I was thinking about running hard-disk checks - if anyone can recommend good program for
doing
that it would be great.
Still, are there any KDE logs that could be helpful in searching for the cause?
Janek
---
Politechnika Łódzka
Lodz University of Technology
Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata.
Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę
prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.
11:55 p.m.
New subject: [trinity-users] Debugging stability
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 07/27/2015 08:13 PM, Jan Stolarek wrote:
Hi all,
in the recent weeks I am experiencing serious stability issues on two of my machines
running KDE 3. I know KDE 3 is
not Trinity and whatever the causes are they might be fixed in Trinity, but nevertheless
I believe that the
debugging techniques are identical for KDE and Trinity. That's why I'm asking for
help here.
Machine 1 On first of my machines I am experiencing random desktop freezes around two
times a day (this started
around 2 weeks ago). When this happens the current application becomes irresponsive and I
am unable to switch to
different application by using Alt-tab or by clicking on the task bar. I am able to kill
the graphical environment
using Ctrl-Alt-Backspace or go to text console (Ctrl-Alt-F1) to kill tasks. I was unable
to find any program that,
when killed, would unfreeze the desktop. The only puzzling thing is that killing Firefox
seems to make it a zombie
process.
Machine 2 That machine experiences random problems when loading the desktop after login.
The problem manifests
itself with an error message from KDE panel saying that
"'/home/USER/.local/share/applications/foo.desktop' service
is broken" (where foo is an application like Skype, Firefox, etc.) and then the KDE
panel becomes irresponsive.
Again, this is random and sometimes the desktop loads correctly.
In both cases I have no idea how to debug the encountered problems. Are there any logs
that could point me the
source of the problems? Are there any diagnostics that I could run? Any ideas appreciated
as I fell clueless.
Janek
Hi Janek,
hard to say, it could be many things. Did you do any sw update to the machine recently
(for example kernel)?
The machine 1 issue sounds like kicker is frozen. You can try going to console and run
ps aux |grep kicker
and see what happen. You could also try to kill kicker and launch it again.
Same goes for kdesktop
For machine 2 I would suggest trying to create a new account and see if the problem
happens there as well. If not,
maybe some files in your home folder got corrupted/inconsistent.
Also ~/.xsession-error may give a clue.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVtsThAAoJECp1t8qK3tXPlsYQAJfnrtygJQr9Wo+jiVpu0qUG
VnjKd5fGQYBV8FteLsiGqTOrcr/tfXEEDgyeb+EaPMQ8hl+ntwROuVMN5NhXOm5Y
3uamw+QXchF2uuNpD6vet2PBuDYwgWWQgOhbotljc+h4jszEVElRuAj+GFbrZUpI
XAoL+B4hUZ5NkO1/spCbwLMbpjYzWzU1wDD8pgiPEiaHrtEysGWw0v+Cx5NJD8FP
RWxRIXemICTYu95ZQ1VVEx/4ZszUKzlVNbta2Zpfgi0Y1z3HFeY69Uj7CbXNez8h
53M7H5lsiEhsJfdzSsqtIDBzY9HGuOM0i0nj+VMg6UcjgOGcOlhuE4sB08RKRdR4
CywQgroSzfmsQQJFxNQdw8khMqiw533IX4wfIpzmEPg2YWogPlgsIfeVaqnXJcXK
AwZBB70vLCyz/1tkAORqyI4fHF2YjdJ+X9iVFB2OPKjKixhxNwvp/Up6JW3uSkzS
mT5U85lcApqHT97QbdjDSbEokuz1TGIeWz14zf8LB81wEdmFbHyfMIGgioIIfryc
6qZnGTEsaC9KMDj/A/7x9BCuiWLbOl7YTgOECVTurSicbFvFqeC0jD4q13jbHLZT
8gvYmvBsO4dJxFD8xL+taEkJU5nwDEgPovvmritfrUHnssVUP5yYs/ENVmezCMZC
mnsFSs7wTLLaUdRpW5Rc
=fCsJ
-----END PGP SIGNATURE-----
3435
days inactive
3435
days old
5 comments
5 participants
participants (5)
-
Alexandre -
Dan Youngquist -
Dr. Nikolaus Klepp -
Jan Stolarek -
Michele Calgaro