BOINC Manager not working after an update

classic Classic list List threaded Threaded
4 messages Options
Bob
Reply | Threaded
Open this post in threaded view
|

BOINC Manager not working after an update

Bob
I installed an update to Ubuntu 19.10 and now the "BOINC Manager" no longer
runs.  I tried to run the program from the icon and in a terminal, as far as I
can tell there are no error messages.  How do I trouble shoot this?

How can I find the program name that is executed when I click an icon that is
on the task bar?

--
Robert Blair


Just because you do not take an interest in politics doesn't mean politics won't take an interest in you!  -- Pericles (430 B..C.)

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: BOINC Manager not working after an update

Karl Auer
On Thu, 2019-11-14 at 20:01 -0800, Bob wrote:
> I installed an update to Ubuntu 19.10 and now the "BOINC Manager" no
> longer runs.  I tried to run the program from the icon and in a
> terminal, as far as I can tell there are no error messages.  How do I
> trouble shoot this?

So when you ran it in a terminal there were no messages of any
description, and the prompt returned? That indicates that:

a) the program exists
b) the program is in your PATH
c) the program was able to be executed
d) the program produced no output to the terminal

... the first three of which are good things!

Check /var/log/syslog as well, it may log errors there.

You could try looking in the task list for likely candidates, i.e., in
a terminal window:

   ps ax

You could also try

   apropos boinc

to see if there are related man pages (also try whatever words BOINC
stands for).

> How can I find the program name that is executed when I click an icon
> that is on the task bar?

Each of those icons has a desktop file. Customised ones are generally
in ~/.local/share/applications, distributed ones are generally
in /usr/share/applications/, autostarted programs are generally in
~/.config/autostart, so check out those places first. To find all the
places they could be, use locate:

   locate .desktop | less

It's quite a list. Local ones override distributed ones if there are
files with the same name in multiple locations.

There is probably a config file somewhere that says what locations the
Launcher should look in for desktop files, but I don't know what that
config file is.

Regards, K.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer ([hidden email])
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: 8D08 9CAA 649A AFEF E862 062A 2E97 42D4 A2A0 616D
Old fingerprint: A0CD 28F0 10BE FC21 C57C 67C1 19A6 83A4 9B0B 1D75



--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Bob
Reply | Threaded
Open this post in threaded view
|

Re: BOINC Manager not working after an update

Bob
** Reply to message from Karl Auer <[hidden email]> on Fri, 15 Nov 2019
16:29:38 +1100

> On Thu, 2019-11-14 at 20:01 -0800, Bob wrote:
> > I installed an update to Ubuntu 19.10 and now the "BOINC Manager" no
> > longer runs.  I tried to run the program from the icon and in a
> > terminal, as far as I can tell there are no error messages.  How do I
> > trouble shoot this?
>
> So when you ran it in a terminal there were no messages of any
> description, and the prompt returned? That indicates that:
>
> a) the program exists
> b) the program is in your PATH
> c) the program was able to be executed
> d) the program produced no output to the terminal
>
> ... the first three of which are good things!
>
> Check /var/log/syslog as well, it may log errors there.

I ran gedit to open syslog and then closed it.
Clicked on the BOINC Manager icon (this program ran before the Ubuntu update).
Ran gedit again.
Here is the data at the end of syslog

Nov 14 22:57:11 Juptier dbus-daemon[2437]: [session uid=1000 pid=2437]
Activating service name='org.gnome.gedit' requested by ':1.143' (uid=1000
pid=11238 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
Nov 14 22:57:11 Juptier dbus-daemon[2437]: [session uid=1000 pid=2437]
Successfully activated service 'org.gnome.gedit'
Nov 14 22:57:50 Juptier xdg-desktop-por[2581]: Failed to get application
states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window
list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection
not allowed
Nov 14 22:58:25 Juptier gnome-shell[2653]: # _g_io_module_get_default: Found
default implementation gvfs (GDaemonVfs) for ΓÇÿgio-vfsΓÇÖ
Nov 14 22:58:25 Juptier dbus-daemon[2437]: [session uid=1000 pid=2437]
Activating via systemd: service name='org.gnome.Terminal'
unit='gnome-terminal-server.service' requested by ':1.150' (uid=1000 pid=11434
comm="/usr/bin/gnome-terminal.real --window " label="unconfined")
Nov 14 22:58:25 Juptier systemd[2405]: Starting GNOME Terminal Server...
Nov 14 22:58:25 Juptier dbus-daemon[2437]: [session uid=1000 pid=2437]
Successfully activated service 'org.gnome.Terminal'
Nov 14 22:58:25 Juptier systemd[2405]: Started GNOME Terminal Server.
Nov 14 22:58:25 Juptier gnome-shell[2653]: # _g_io_module_get_default: Found
default implementation dconf (DConfSettingsBackend) for ΓÇÿgsettings-backendΓÇÖ
Nov 14 22:58:25 Juptier gnome-shell[2653]: # watch_fast:
"/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
Nov 14 22:58:25 Juptier gnome-shell[2653]: # unwatch_fast:
"/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
Nov 14 22:58:25 Juptier gnome-shell[2653]: # watch_established:
"/org/gnome/terminal/legacy/" (establishing: 0)
Nov 14 22:58:47 Juptier systemd[2405]: gnome-terminal-server.service: Succeeded.
Nov 14 22:58:50 Juptier xdg-desktop-por[2581]: Failed to get application
states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window
list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection
not allowed
Nov 14 23:00:50 Juptier xdg-desktop-por[2581]: message repeated 2 times: [
Failed to get application states:
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not
allowed]
Nov 14 23:01:27 Juptier systemd-resolved[859]: Server returned error NXDOMAIN,
mitigating potential DNS violation DVE-2018-0001, retrying transaction with
reduced feature level UDP.
Nov 14 23:01:38 Juptier dbus-daemon[2437]: [session uid=1000 pid=2437]
Activating service name='org.gnome.gedit' requested by ':1.143' (uid=1000
pid=11238 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
Nov 14 23:01:38 Juptier dbus-daemon[2437]: [session uid=1000 pid=2437]
Successfully activated service 'org.gnome.gedit'

There are errors but I do not know what they are indicating.


>
> You could try looking in the task list for likely candidates, i.e., in
> a terminal window:
>
>    ps ax

I clicked on the BOINC Manager icon then ran ps ax there is no boincmgr running.


>
> You could also try
>
>    apropos boinc

bob1@Juptier:~$ apropos boinc
boinc (1)            - The BOINC client program.
boinccmd (1)         - The command line interface to the BOINC client.
boincmgr (1)         - The graphical BOINC manager for the client.
update-boinc-applinks (1) - create/remove symbolic links for anonymous BOINC
applications
bob1@Juptier:~$

The boinc client is running.
The boinc manager does not run.


> to see if there related man pages (also try whatever words BOINC
> stands for).
>
> > How can I find the program name that is executed when I click an icon
> > that is on the task bar?
>
> Each of those icons has a desktop file. Customised ones are generally
> in ~/.local/share/applications, distributed ones are generally
> in /usr/share/applications/, autostarted programs are generally in
> ~/.config/autostart, so check out those places first. To find all the
> places they could be, use locate:
>
>    locate .desktop | less
>
> It's quite a list. Local ones override distributed ones if there are
> files with the same name in multiple locations.
>
> There is probably a config file somewhere that says what locations the
> Launcher should look in for desktop files, but I don't know what that
> config file is.

Thanks for that information.


>
> Regards, K.

--
Robert Blair


You cannot multiply wealth by dividing it. -- Adrian Rogers

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: BOINC Manager not working after an update

Karl Auer
On Fri, 2019-11-15 at 00:08 -0800, Bob wrote:
> I ran gedit to open syslog and then closed it.
> Clicked on the BOINC Manager icon (this program ran before the Ubuntu
> update).
> Ran gedit again.
> Here is the data at the end of syslog

A better way to see what log entries a program is causing is to open a
terminal window and run "tail -f /var/log/syslog". Then, in a different
terminal window, or from the Launcher or whatever, start the program.

I cannot interpret those error messages. You might look to see if there
is a boinc-specific log file:

   ls -la /var/log/boinc*

I'm sorry, I don't know why boincmgr does not run. It may require a
running client, and attempts to contact the client might be causing
those messages. It's odd that there is nothing to indicate it giving
up, though. So maybe you should first try to get a running client
happening. This will tell you if one is already running:

   ps ax | grep boinc

Regards, K.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer ([hidden email])
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: 8D08 9CAA 649A AFEF E862 062A 2E97 42D4 A2A0 616D
Old fingerprint: A0CD 28F0 10BE FC21 C57C 67C1 19A6 83A4 9B0B 1D75



--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users