Using the latest gnome 3.16 from packages. If i try to load gnome-system-monitor it doesn't start. Running it through the terminal i get the following message: (<unknown>:1280): glibmm-CRITICAL **: unhandled exception (type Glib::Error) in signal handler: domain: g-io-error-quark code : 0 what : Unable to find default local directory monitor type LibGTop-Server: pid 1281 received eof.
I have the same problem: gnome-system-monitor (<unknown>:91004): glibmm-CRITICAL **: unhandled exception (type Glib::Error) in signal handler: domain: g-io-error-quark code : 0 what : Unable to find default local directory monitor type LibGTop-Server: pid 91005 received eof. My system: FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 GNOME 3.16
Same problem here, using 10.2-RELEASE/amd64. This issue was also reported on Ubuntu https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1430068 so it seems that it's a upstream bug.
I have two systems running FreeBSD 10.2-STABLE r286975 amd64. Both systems are quad Opterons, one with 4 single core and the other with 4 dual core. One is using xorg 7.7_1 (compiled some time ago from ports) and gnome3-3.16.2 obtained via pkg; the other is running xorg 7.7_2 and gnome3-3.16.2 obtained via pkg. gnome-system-monitor operates correctly on the xorg 7.7_1 system but fails in the described manner with xorg 7.7_2. This happens running either Cygwin/X x64 or Ubuntu Studio 14 x64. I have both systems currently running; the bug is not a serious problem for me since other X11 programs are working correctly (with complaints); for example, virtualbox-ose operates properly on both. Mike Squires mikes@siralan.org UN*X at home since 1986
(In reply to mikes from comment #3) I think Xorg 7.7_2 is from March. On Gnome 3.14 works without problem but stopped working on Gnome 3.16 on my system. I have installed FreeBSD on iMac (amd64).
I have the same issue with FreeBSD 10.2 and Gnome System Monitor 3.16.0. FreeBSD desktop 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
(In reply to Yonas Yanfa from comment #5) Thanks for reporting! I guess that this bug will be fixed as soon as possible.
Is this still relevant? Or could it be closed?
Now is 2018 and it works on mine GNOME 3.18
Thanks for reply. So, please close the PR.