trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: July 2015

Re: [trinity-users] Debugging stability

From: Michele Calgaro <michele.calgaro@...>
Date: Tue, 28 Jul 2015 08:55:13 +0900
-----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-----