Column customizations not remembered

[Ben Maurer]

1. remove the /apps/procman gconf keys from your configuration and restart gconfd. This helps to reproduce the issue
2. Start up g-s-m
3. configure the columns in preferences. Check the "arguments" column
4. Reorder the memory and the arguments column so that memory is on the left.
5. Quit g-s-m
6. Reopen g-s-m
7. Note the lack of the memory column

[Sebastien Bacher (seb128)]

Thanks for the bug. Happens without removing gconf keys, I've forwarded it upstream: http://bugzilla.gnome.org/show_bug.cgi?id=365101

[Nuno Santos (zoryn1)]

I'm having this problem too. Is there any workaround to make the memory column not go away?

[Barry Kelly (bkelly-ie)]

This bug is worse in many ways than indicated - it makes the monitor all but useless from my POV, since no matter how I configure it, I either lose the Process Name or I lose the pid ("ID") column.

[James Smith (gtr225-deactivatedaccount)]

This bug has been bothering me for a while. On a fresh install it didn't happen, then all of a sudden I can't get the memory column to show up every time I open System Monitor.

[Ryan (larsrya8)]

This bug is still present in the GNOME System Monitor that ships with Jaunty.

[Julian Alarcon (julian-alarcon)]

I also suffer this Bug, my memory column just disappear... This is frustrating.

Maybe, the problem is from Upgrades.. Cause in 8.10 i didn't have the problem, just after the upgrade to 9.04 this bug appeared...

[Jyaan (box100-prodigy)]

I have this problem too. This couldn't have only appeared in Jaunty because I've had this bug on Intrepid and Jaunty (x86), and again now on Jaunty (64).

[Michael Rooney (mrooney)]

This is a usability issue but I'm not sure if this is a paper cut, as I don't believe anyone knows the specific cause or fix for this. The upstream bug has seen no response in years. If anyone knows the issue let us know but otherwise I think this is not a paper cut, though of course the bug is still valid in Ubuntu.

[Doc (cufalo)]

SOLVED!

gconf-editor:

/apps/procman/proctree/col_15_visible --> True

/apps/procman/proctree/columns_order --> Add n. 15

Hi!

[Jesse Katzman (j-kat)]

Hi Doc.

Thank you for spreading some light on this issue! I no longer have the disappearing column problem, and here's what insight I can add.

The fix for me was slightly different. "/apps/procman/proctree/columns_order" was out of order. It looked like this:
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 15, 13, 14, 16

Changing the order to
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16
(or deleting the key) allowed the memory column to stay the next time I enabled it (through here or the actual monitor).

Changing it back to
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 15, 13, 14, 16
made it stop appearing on startup, disabling col_15_visible.

Placing column 15 in ANY other location does NOT recreate the problem.

Also present in proctree were these keys, which I included because one had the value "15" and they had to do with sorting:
sort_col = 15
sort_order = 1

Again, thank you Doc.

[Doc (cufalo)]

Thanks, bladebot!
In fact, I omitted to say that I had entered the no. 15 in its place.
Hi!

[Cyberkilla (cyberkilla04uk-deactivatedaccount)]

Another confirmation. Deleting the key fixed it for me too.

This has been annoying me for 3 releases.

[liquidator87 (liquidator87)]

Confirmed for me too

[liquidator87 (liquidator87)]

bladebot's method seems to work, but not for all orders...
for me worked 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 14, 16

[Vincent Ladeuil (vila)]

Thanks so much for the workaround this drove me nuts for ages. In my case the 'Command line' column wasn't saved.

[Vincent Ladeuil (vila)]

Once I restored the 0..16 order in 'columns_order' property, everything started to work again: adding columns, changing the *displayed* order.
So the only difference from my user pov now is that the Edit/preferences/process information fields are not displayed in the same order... which I don't care about. But this may help upstream fix the issue.

[Jesse Katzman (j-kat)]

liquidator87: Are you saying you still have this glitch when the columns are in the order you mentioned?

[Chris Wilson (notgary-deactivatedaccount)]

I've poked the upstream report to see if anyone responds, and I've told them that there's a workaround detailed here, that may help them determine the cause of this.

Also, this bug does not seem like it will affect the 'average user' on a regular basis, which is part of the definition of a paper cut, since the Gnome System Monitor is a tool usually used by at least intermediate users, so it is not a paper cut.

[Josh (majik)]

Whether or not the bug poses a significant problem does not make it invalid.

It is still a bug.

[Chris Wilson (notgary-deactivatedaccount)]

Josh, I marked this as invalid only for the 'One Hundred Paper Cuts' project. For a bug to be considered a paper cut, it must first satisfy the strict definition of a paper cut, which can be found here https://wiki.ubuntu.com/PaperCut

This bug is still valid for the g-s-m project.

[Peter Stuifzand (peter-stuifzand)]

I created a patch that fixes this bug.

Explanation:

When can_show_security_context_column() returns false, column COL_SECURITYCONTEXT will be hidden. However the wrong column is found, because the wrong function is used. Changing gtk_tree_view_get_column to my_gtk_tree_view_get_column_with_sort_column_id fixes this bug.

[Dmitri Bachtin (damg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Oneiric Ocelot. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information.