On Sunday 10 Jun 2012 12:10:37 Ralph Corderoy wrote:
> If there's little time between the two then I'd blame Skype.
>
> https://bugs.launchpad.net/ubuntu/+source/skype/+bug/977979
This is possible, because Skype had exited after the incident, just as in the
bug report. However, unlike in the bug report, it doesn't happen at start-up;
I'd been running about an hour when the problem occurred.
> You could leave `dstat 10' running in a terminal window and then you'd
> be able to look at its scrollback after the next instance.
Well its running now...
> Perhaps a Google+ hang-out could replace Skype? :-)
I mainly use Skype to talk to my mother. She knows how to use it and it may
be a bit of a stretch to swith her over to Google+. I'm not a Google+ user
myself and I tend to avoid most social networking tools anyway.
> If it's not that then perhaps some disk indexing task? Log files in
> /var/log might show something starting around the time of your troubles.
Nothing obvious (to me anyway). There was something logged in syslog just
*after* the problem, but nothing before:
Jun 10 10:08:31 BEIGE dbus[938]: [system] Activating service
name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Jun 10 10:08:32 BEIGE org.kde.powerdevil.backlighthelper: QDBusConnection:
system D-Bus connection created before QCoreApplication. Application may
misbehave.
Jun 10 10:08:32 BEIGE dbus[938]: [system] Successfully activated service
'org.kde.powerdevil.backlighthelper'
This keeps repeating at intervals of a few minutes to an hour.
--
Terry Coles
64 bit computing with Kubuntu Linux
--
Next meeting: Bournemouth, Tuesday 2012-06-12 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
New thread on mailing list: mailto:[email protected]
How to Report Bugs Effectively: http://goo.gl/4Xue