Hi,
Can anyone tell me how to debug this problem that has just started in the past
few days?
As you know from my previous postings, I installed BOINC on 25th March. At
the same time I installed BOINC Client and BOINC Control and this allowed me
to launch BOINC Manager to setup the configuration. On shutdown, I left the
BOINC Manager running alongside the KDE System Monitor. On the following and
subsequent mornings those two apps started automatically on boot-up. So far
so good.
Yesterday morning I started as normal, but no BOINC Manager. I tried clicking
on the icon that I'd created in the Plasma desktop Widget - nothing, so I
rebooted and everything was fine.
Today the same thing occurred, but rebooting didn't help, so I tried purging
the three BOINC packages and their associated dependencies, but that didn't
help. I then found that if I ran 'sudo boincmgr' in a shell the Manager came
up.
So I started diagnosing. Running 'boincmgr' in a shell simply exits with no
error. The apt history log shows me successfully installing the three
packages on the 25th and the purge today but I couldn't see anything relevant
in the updates log (I checked if any of the dependencies had been updated by
Discover Updater since the 25th and they hadn't. The only update cycle that
has been run recently was this morning; after this problem became apparent.
The only mention of boincmgr in syslog says:
Mar 31 08:11:30 OptiPlex dbus-daemon[1749]: [session uid=1000 pid=1749]
Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-
bus.service' requested by ':1.29' (uid=1000 pid=1894 comm="boincmgr "
label="unconfined")
I don't really have any idea what all that means.
Does anyone have any ideas what might have happened or how I can go about
finding ot the cause?
--
Terry Coles
--
Next meeting: BEC, Bournemouth, Tuesday, post-lurgi 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
