GNOME Bugzilla – Bug 549760
crash after changing the nice value
Last modified: 2011-11-11 10:03:55 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/206583 "I tried to change the priority of a process by right clicking > Change Priority After changing the slider value and clicking the Change Priority value, System Monitor closes. The crash only occurs when increasing the priority (lowering the nice value). Decreasing priority works as intended." ".
+ Trace 205816
Thread 2 (process 10331)
Thread 1 (process 10328)
Thanks,
This is a particularly concerning bug for me, as we use G-S-M to kill misbehaving processes on LTSP servers with many simultaneous users logged in. A (duplicate) bug concerning a crash trying to kill processes is present. What I would enjoy seeing is a gksudo-type escalation so 'admin' users can kill other users' processes. When you try to kill other users' processes it crashes - but running manually w/gksudo allows you to do so without crashing. Thanks for your help!!
Well, if you look at the stacktrace, it actually crashes while running gksu (using its API) but crashes much deeper. That "BadMatch (invalid parameter attributes)" X error looks bad. Do you have any more messages in your .xsession-erros ? Does running standalone gksu trigger any X error/warnings ? (gksu is not hosted on GNOME bugzilla)
from the downstream bug, this is what the ~/.xsession-errors contains: "** (gnome-system-monitor:30021): WARNING **: SELinux was found but is not enabled. Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x1e01f20)" of type `GString' Gdk-ERROR **: The program 'gnome-system-monitor' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 72926 error_code 8 request_code 1 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... "
could the gdk_x_error be related to bug 534995 ?
Hello, libgksu hasn't changed much in these last months, but it's "fading" effect seems to be the problem. I can actually reproduce this in Debian's gnome-system-monitor by trying anything that would use gksu, such as lowering or raising priority, killing other user processes and stuff. I cannot reproduce the problem when using the gksu client, though. Can those of you who are experiencing the problem please try to set the /apps/gksu/disable-grab key to True in gconf-editor? Also, I haven't looked at gnome-system-monitor's code yet, but is it using threads or some other kind of paralelism that could make it draw its graphs while libgksu is doings its effect? It could be related, and I may need to add some gdk_threads_enter/gdk_threads_leave in my code.
The problem indeed happens when password is required. Setting /apps/gksu/disable-grab to True makes the problem disappear.
I can confirm the workaround in comment #6, for G-S-M 2.22.3 under Ubuntu 8.04LTS. Sure would be nice to get a fix for the core issue, however. :)
ok, so I finally took some time to debug this in libgksu proper, and I believe I have a fix; I'm going to be releasing libgksu 2.0.8 today with the fix; I'm attaching the patch to libgksu here, though, since it is pretty simple and people may want to backport it to stable versions.
(In reply to comment #8) > ok, so I finally took some time to debug this in libgksu proper, and I believe > I have a fix; I'm going to be releasing libgksu 2.0.8 today with the fix; I'm > attaching the patch to libgksu here, though, since it is pretty simple and > people may want to backport it to stable versions. > Thank you for fixing this bug. Can you attach the patch here. I do not think you have done that yet. By the way this bugs status is still unconfirmed can that be fixed. I'm looking front to using this patch with Ubuntu 8.04.
I can confirm that this bug has been fixed.