Andrew D Bate

This is actually due to a bug in the elementary stylesheet. The same issue happens when using Nemo. The problem is due to the hit region for the separator being...

Note however though that `gvfs` does not have NFSv4 support. See issues https://gitlab.gnome.org/GNOME/gvfs/-/issues/18 and https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/13. Also, in my experience NFS support through `gio` seems a bit hit and miss. It...

Now that 0.13.0 has been released, I see that there is an option to enable/disable smooth lines on the CPU chart (however, this option currently requires Monitor to be restarted):...

Here is a video of how Gnome System Monitor handles the turning on/off of smooth lines (43 seconds): https://user-images.githubusercontent.com/2998569/159173512-1819b0bf-7a5e-49e1-8eb9-4a5670eb0bfa.mp4 As you can see, in Gnome System Monitor, when you toggle...

Thinking again about the wording on which I commented above: It would be even more concise to say "Draw smooth lines on CPU chart (requires restart)". This would take up...

Here is the output: ``` $ G_MESSAGES_DEBUG=all GTK_DEBUG=interactive com.github.stsdc.monitor Monitor 0.12.0 (com.github.stsdc.monitor:3786): GLib-GIO-DEBUG: 15:34:20.877: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (com.github.stsdc.monitor:3786): dconf-DEBUG: 15:34:20.877: watch_fast: "/com/github/stsdc/monitor/settings/" (establishing: 0, active:...

The GPU is the one integrated into the Acer Aspire notebook. The debug log I attached above reports it as: ``` ** (com.github.stsdc.monitor:3786): DEBUG: 15:34:24.203: Resources.vala:67: GPU: AMD PALM (DRM...

Running `gdb com.github.stsdc.monitor` and then `run` revealed the problem. The relevant lines from the gdb output: ``` Thread 1 "com.github.stsd" received signal SIGSEGV, Segmentation fault. 0x0000555555574082 in monitor_system_cpu_info_popover_general_page (self=0x555555cfdbe0) at...

@stsdc Yes, I tested it on that machine at the time and it fixed the issue.

@stsdc I have just upgraded to 0.13.0, but it appears that this issue is back again. Looking at the [file history for SystemCPUInfoPopover.vala](https://github.com/stsdc/monitor/commits/dev/src/Views/SystemView/SystemCPUInfoPopover.vala), I can see that this issue was...