in system monitor's preferences the refresh rate value is not saved when changed by key

[schnollk]

In system monitor's preferences the refresh rate value is not saved when changed by key. On the other hand if I change it via mouse (up/down arrows) the change is remembered.

I have made videos of the szenario but since I reckon there are people getting those attachments via slow email connections is there a way to add this info without them being send by email? I don't have publically accessable webspace where the videos could reside for a while.

[Sebastien Bacher (seb128)]

Thank you for your bug. What version of Ubuntu do you use? Does it work if you press "enter" after typing the value you want to use? You can attach videos to the bug, the attachments are not sent with the comments the mails have the url, but that's not required if the bug is easy enough to trigger

[schnollk (schnollk)]

Hi Sebastien.

Thanks for your answer.

Yes, indead, if I key in the change and press Return instead of the Tab I used to do before closing changes are remembered.

Since I have the videos lying around anyway I might as well send them in.

Cheers.

[schnollk (schnollk)]

here is the second one recorded while setting a value greater than the one before (not really something special but what the hack ;) )

[schnollk (schnollk)]

sorry, I just noticed I totally forgot to enclose more system infos. Here they come:

~$ uname -a && lsb_release -a && aptitude show gnome-system-monitor | grep Version
Linux ubuntu-desktop-i386 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 7.10
Release: 7.10
Codename: gutsy
Version: 2.20.0-0ubuntu1

[Matthew Woerly (nattgew)]

I think this is common to all inputs like this... the require a Return to set the value. If you close out, then it won't save it.

[Christian Funder Sommerlund (zero3)]

I can confirm that this bug still exists in Hardy Beta.

If it is a general interface bug, it is probably outside the scope of gnome-system-monitor though. Does anyone know which package to assign this bug to instead then?

[Christian Funder Sommerlund (zero3)]

I'm marking this one as "Confirmed" for now. Hopefully someone will be able to pinpoint the correct packet for this bug sometime.

[Pedro Villavicencio (pedro)]

Still an issue? this works fine for me with an up to date hardy, thanks.

[Christian Funder Sommerlund (zero3)]

Hi Pedro

This is still an issue. I can confirm with an up-to-date version of Hardy.

To reproduce:
- Open the setting dialog
- Click once in the refresh interval edit box (to select the field making it editable)
- Enter any number different than the current
- Click Close immediately, without clicking anywhere else
- Open the settings dialog again and verify that the value did not change

Again, this is probably a general interface bug in whatever "toolkit" gnome-system-monitor uses to handle its GUI. I have no idea which that is though.

[schnollk (schnollk)]

Same here, still (also up-to-date Hardy)

To make it clear: If you use arrow-up and arrow-down keys, though, it does work. Only if you delete or highlight the number that is to be changed and press any number diffent to the current one and close the dialog (either by clicking "Close" or with Alt+C) the change is not saved. I also tried moving the focus out of the edit field before closing by hitting tab to no avail.

I was going to add a video with XVidCap but it crashed on me. Istanbul takes ages to "save" the capture to disk, i.e. wouldn't finish saving for some reason, so sorry for that.

[Pedro Villavicencio (pedro)]

thanks both, no need to do another screencap, may you forward it upstream since you're facing the issue? I'm not able to reproduce it here, for forwarding instructions please have a look to https://wiki.ubuntu.com/Bugs/Upstream/GNOME; I'm leaving this as Incomplete until it gets forwarded there, thanks for the help.

[Christian Funder Sommerlund (zero3)]

Forwarded upstream at http://bugzilla.gnome.org/show_bug.cgi?id=543315

[Dmitri Bachtin (damg)]

Patch uploaded to upstream, too.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "update_spin_buttons_by_key.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[Robert Roth (evfool)]

Patch forwarded to GNOME, waiting for approval.

[Robert Roth (evfool)]

Setting as Fix Committed, as this has been fixed in upstream gnome, commit http://git.gnome.org/browse/gnome-system-monitor/commit/?id=abc1f5b47efa2dcd5f0e9c378283e9d9e6ac9fdf

[Robert Roth (evfool)]

This bug was fixed in the package gnome-system-monitor - 3.3.3-0ubuntu1

---------------
gnome-system-monitor (3.3.3-0ubuntu1) precise; urgency=low

  * New upstream unstable release.
    - Shows whether OS is 32-bit or 64-bit (LP: #531762)
    - Network load default colors improved for the colorblind (LP: #485712)
    - UI streamlined (status bar removed, fewer default columns in
      processes tab, etc.)
  * debian/patches/02_lpi.patch: Refreshed
  * debian/watch: Watch for unstable releases
 -- Jeremy Bicha <email address hidden> Wed, 28 Dec 2011 14:46:35 -0600