gnome-system-monitor renice causes close

[Hew]

Binary package hint: gnome-system-monitor

Trying to "Change Priority" for any process of any owner causes g-s-m to close with the following error shown in the terminal:

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 125982 error_code 8 request_code 1 minor_code 0)

Apport and gdb do not see any crash, so I can't get a backtrace. This is reproducible for me every time. Note that the priority slider does not need to be changed, as the crash happens when pressing the "Change Priority" button under any circumstances. This is similar to the fixed libgksu bug #206583, but appears to be a separate issue. This did not occur previously in Jaunty.

Steps to reproduce:
1) Open gnome-system-monitor
2) Right-click on any process in the Processes tab and choose "Change Priority"
3) Adjusting the slider is optional. Press the "Change Priority" button.

What should happen:
4) The priority chosen by the slider is applied to the process, and g-s-m stays open.

What actually happens:
4) g-s-m closes, and "Starting Administrative Application" appears in the gnome-panel. No renice occurs.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-system-monitor
NonfreeKernelModules: nvidia
Package: gnome-system-monitor 2.26.0.1-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-system-monitor
Uname: Linux 2.6.28-11-generic x86_64

[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.

[Hew (hew)]

As I mentioned in the description, and as with bug 206583, it doesn't seem to "crash", but simply close. Apport doesn't catch anything, and reproducing the problem in gdb doesn't produce any backtrace.

However, I expect the problem to be easily reproducible for anyone running up-to-date Jaunty.

[Sebastien Bacher (seb128)]

you should be able to get a stacktrace by setting a break point on gdk_x_error with libgtk2.0-0-dbg installed

[Hew (hew)]

Thanks, I managed to get a backtrace with "break gdk_x_error"; doing the renice on user and root processes produces different looking backtraces so I have attached both. Although strangely, I couldn't easily trigger the issue at first. Now it's back to 100% reproduction again though.

[Sebastien Bacher (seb128)]

the issue seems either a wnck or a xorg one

[Fernando Miguel (fernandomiguel)]

bug 364843 is a dupe of this one.
i'm trying to kill a process owned by root using gnome-system-monitor.
it used to invoke GKSU, but not it just closes it self
$ gnome-system-monitor

** (gnome-system-monitor:28409): WARNING **: SELinux was found but is not enabled.

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 121038 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.)

[Krzysztof Debski (fantom15)]

I can confirm this bug in a fully updated 32-bit Interpid.

I can make priority lower, but not higher.
System monitor tries to spawn gksudo but for some reason it dies.

[Milo Casagrande (milo)]

I stumbled upon this problem both in Jaunty and in Karmic.

[claim (claim-interia)]

I confirm the bug still occurs in Karmic.

[Hew (hew)]

Problem appears to be fixed for me in Lucid, can someone else confirm?

[aporter (aporter)]

Hew, yes it seems fixed for me in Lucid also. Does that mean this ticket is "fix committed" or "fix released"? Since Lucid isn't released I'm not sure if this counts as released or not.

[Hew (hew)]

Ubuntu bug status applies to the development version. See https://wiki.ubuntu.com/Bugs/Status for information about bug status.