The "update-interval" don't go beyond 100 secs and the app can crash

[Almir Campos]

Steps:

1 - Edit the range on the 'update-interval' key to a max over 100.00 seconds.
2 - Re-compile the schemas (glib-compile-schemas)
3 - Run gnome-system-monitor.
4 - Open the 'Preferences' window
5 - Click on the "+" button several times
6 - Verify that it won't be beyond "100.00".

Also, if after following the above steps you use 'gsettings' or 'dconf-editor' to update the current value to a value above 100.00 secs you will see that the 'Preferences' window will keep the value '100.00' - please see the attached screenshot.

Finally, during the tests the app crashed several times. At least in one of them I sent the automatic report.

My environment:

Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic

Hardware:

Memory: 7.7 GiB
Processor: Intel Core i7-5600U CPY @ 2.60GHz x 4
Graphics: Intel HG Graphics 5500 (Broadwell GT2)
OS type: 64-bit
Disk: 243.6 GB

Please, let me know if you need more data or info.

Thank you.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

One alternative would be to provide the id of the automatic report you mentioned.

Also if the only way to trigger the bug is to change the schemas by hand then it's not a really a bug that impacts Ubuntu, could still be a bug in the code not handling that change but that would be reported upstream

[Launchpad Janitor (janitor)]

[Expired for gnome-system-monitor (Ubuntu) because there has been no activity for 60 days.]