Hello

I am using BOINC 4.6 on LInux MINT.

I set up my computer an dBOINC was running. I moved my computyer to its permanent location, and , it stopped working. I added a new video card. When clicking on the icon to start it up, it just does not work,.

I used the command line, and I ended up finding an error:

Setting up project and slot directories
dir_open: Could not open directory 'slots' from '/home/joseph'.
29-Dec-2018 17:48:48 [---] Checking active tasks
29-Dec-2018 17:48:48 [---] Setting up GUI RPC socket
29-Dec-2018 17:49:17 [---] GUI RPC bind to port 31416 failed: 98
29-Dec-2018 17:49:18 gstate.init() failed
Error Code: -180

I am not quite sure where to start looking so if I can get any ideas, I'd appreciate it.

Thanks for any ideas.

Joseph

Starting BOINC Manager (the icon) under Linux only starts the GUI, it does not start the client. You have to start the client separately, from the command line, using sudo /etc/init.d/boinc-client start
After that start the manager.

---

Hello,

I have installed BOINC before on Linux MINT and Ubuntu, and have never had to run the client seperately. Weird that I might need to do it now.

I tried your idea of starting the client, and then the manager, and it is not work unfortunately.

Thanks

Starting BOINC Manager (the icon) under Linux only starts the GUI, it does not start the client. You have to start the client separately, from the command line, using sudo /etc/init.d/boinc-client start
After that start the manager.

Sorry Jord but I don't think you are correct on this one. I am running various versions of Linux in dual Boot configuration on 16 Machines. By clicking or double clicking the BOINC Manager Icon is all I have to do to run the client. The Command line option is just another way of doing it.

Hello

If it amkes a difference, I installed the software using the software manager: v 7.9.3

I am using th elatest version of Linux MINT.

Thanks

Same problem here, I loaded BOINC on the 26th (Ubuntu 18.04) and it has run fine until this morning when the client appears to be running (system monitor is showing high cpu usage in the pattern I have come to associate with Boinc although I cannot see the process in the process list) but the manager will not start.

Are there any logs that I can look at or any commands I can try to debug the problem?

I have found the following from about the time I closed down the computer last night :-


(boincmgr:4877): GLib-GIO-CRITICAL **: 22:31:30.952: g_dbus_server_get_client_address: assertion 'G_IS_DBUS_SERVER (server)' failed

(boincmgr:4877): GLib-CRITICAL **: 22:31:30.963: g_variant_new_string: assertion 'string != NULL' failed

(boincmgr:4877): Gtk-CRITICAL **: 22:31:31.287: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:4877): Gtk-CRITICAL **: 22:31:31.288: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:4877): Gtk-CRITICAL **: 22:31:31.288: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:4877): Gtk-CRITICAL **: 22:31:31.288: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
execv: No such file or directory
execv: No such file or directory
execv: No such file or directory
Gdk-Message: 23:18:20.386: boincmgr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 23:18:20.389: WebKitWebProcess: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(boincmgr:3748): Gtk-CRITICAL **: 08:47:57.198: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:3748): Gtk-CRITICAL **: 08:47:57.220: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:3748): Gtk-CRITICAL **: 08:47:57.221: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:3748): Gtk-CRITICAL **: 08:47:57.221: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:3748): GLib-GObject-WARNING **: 17:45:08.652: invalid (NULL) pointer instance

(boincmgr:3748): GLib-GObject-CRITICAL **: 17:45:08.652: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(boincmgr:3748): Gtk-CRITICAL **: 17:45:08.652: gtk_window_set_modal: assertion 'GTK_IS_WINDOW (window)' failed
execv: No such file or directory
execv: No such file or directory
execv: No such file or directory
Gdk-Message: 23:08:49.136: WebKitWebProcess: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(boincmgr:5153): Gtk-CRITICAL **: 09:03:34.040: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:5153): Gtk-CRITICAL **: 09:03:34.040: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:5153): Gtk-CRITICAL **: 09:03:34.041: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:5153): Gtk-CRITICAL **: 09:03:34.041: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:5153): GLib-GObject-WARNING **: 11:46:03.187: invalid (NULL) pointer instance

(boincmgr:5153): GLib-GObject-CRITICAL **: 11:46:03.200: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(boincmgr:5153): Gtk-CRITICAL **: 11:46:03.200: gtk_window_set_modal: assertion 'GTK_IS_WINDOW (window)' failed
Gdk-Message: 00:04:44.953: WebKitWebProcess: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(boincmgr:4018): Gtk-CRITICAL **: 11:31:17.382: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:4018): Gtk-CRITICAL **: 11:31:17.383: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:4018): Gtk-CRITICAL **: 11:31:17.383: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:4018): Gtk-CRITICAL **: 11:31:17.384: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:4018): GLib-GObject-WARNING **: 12:23:38.671: invalid (NULL) pointer instance

(boincmgr:4018): GLib-GObject-CRITICAL **: 12:23:38.684: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(boincmgr:4018): Gtk-CRITICAL **: 12:23:38.684: gtk_window_set_modal: assertion 'GTK_IS_WINDOW (window)' failed

(boincmgr:3157): Gtk-CRITICAL **: 17:38:51.034: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:3157): Gtk-CRITICAL **: 17:38:51.137: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:3157): Gtk-CRITICAL **: 17:38:51.137: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:3157): Gtk-CRITICAL **: 17:38:51.138: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(boincmgr:3157): GLib-GObject-WARNING **: 17:40:59.709: invalid (NULL) pointer instance

(boincmgr:3157): GLib-GObject-CRITICAL **: 17:40:59.709: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(boincmgr:3157): Gtk-CRITICAL **: 17:40:59.709: gtk_window_set_modal: assertion 'GTK_IS_WINDOW (window)' failed
Gdk-Message: 22:42:05.065: boincmgr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

I can now confirm that the Boinc client is running, it has been posting completed work units to WCG.

I am having the same problem since upgrading from Mint 19 to 19.1. The Boinc client is starting and running fine; I also have BoincTasks installed and can check that my projects are running. However, when I start BOINC Manager, it shows "Disconnected" at the bottom and no Projects or Tasks are shown.

I don't know whether this is relevant but I noticed in the syslog that it occasionally mentioned that the file temp.xml was missing from lib /var/lib/boinc so, on the off chance, I created an empty spreadsheet of that name and now Boinc Manager starts.

The error messages do not appear to relate to the times when I have tried to start Boinc Manager so it could well be a red herring but ...

Whenever I have an issue where either the client or manager doesn't start, I always do a dependency check for each to be sure all the resources needed are available. With a Linux distro revision upgrade, it is always possible something was removed or added that could cause issues.

Whenever I have an issue where either the client or manager doesn't start, I always do a dependency check for each to be sure all the resources needed are available. With a Linux distro revision upgrade, it is always possible something was removed or added that could cause issues.

Hmm, I did try a reinstall of BoincMgr which should have sorted out any dependency problems before I came here to ask for help so I don't *think* it was that but it is a possibility.