*** This bug is a duplicate of bug 206583 ***
https://bugs.launchpad.net/bugs/206583
** This bug has been marked a duplicate of bug 206583
System Monitor crashes when lowering nice value of process
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You
Ubuntu bug status applies to the development version. See
https://wiki.ubuntu.com/Bugs/Status for information about bug status.
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete = Fix Released
--
gnome-system-monitor renice causes close
Problem appears to be fixed for me in Lucid, can someone else confirm?
** Changed in: gnome-system-monitor (Ubuntu)
Status: Triaged = Incomplete
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member
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.
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug
I confirm the bug still occurs in Karmic.
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I stumbled upon this problem both in Jaunty and in Karmic.
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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.
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because
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
** Bug watch added: GNOME Bug Tracker #579777
http://bugzilla.gnome.org/show_bug.cgi?id=579777
** Also affects: gnome-system-monitor via
http://bugzilla.gnome.org/show_bug.cgi?id=579777
Importance: Unknown
Status: Unknown
--
gnome-system-monitor renice causes close
** Changed in: gnome-system-monitor
Status: Unknown = New
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gnome-system-monitor (Ubuntu)
Status: New = Triaged
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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.
** Attachment
** Attachment added: gdb-g-s-m.txt (root)
http://launchpadlibrarian.net/25787513/gdb-g-s-m.txt
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
the issue seems either a wnck or a xorg one
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete = New
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
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.
--
you should be able to get a stacktrace by setting a break point on
gdk_x_error with libgtk2.0-0-dbg installed
--
gnome-system-monitor renice causes close
https://bugs.launchpad.net/bugs/363558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25718118/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/25718119/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/25718120/ProcStatus.txt
--
18 matches
Mail list logo
