** Changed in: gnome-system-monitor
Importance: Unknown = Critical
--
Wrong password causes crash...
https://bugs.launchpad.net/bugs/60112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
gnome-system-monitor (2.16.1-0ubuntu1) edgy; urgency=low
.
* New upstream release:
- Fixed locales dir initialization.
- Fixed memory maps for 64bits kernel running a 32bits system-monitor.
- Fixed gksu password prompt. (Malone: #60112)
* debian/control.in:
- bumped
** Changed in: gnome-system-monitor (upstream)
Status: Confirmed = Fix Released
--
Wrong password causes crash...
https://launchpad.net/bugs/60112
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: gnome-system-monitor (upstream)
Status: Unknown = Confirmed
--
Wrong password causes crash...
https://launchpad.net/bugs/60112
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
fixed upstream
** Changed in: gnome-system-monitor (Ubuntu)
Status: Confirmed = Fix Committed
--
Wrong password causes crash...
https://launchpad.net/bugs/60112
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I've forwarded the issue upstream with a debug backtrace:
http://bugzilla.gnome.org/show_bug.cgi?id=356111
** Changed in: gnome-system-monitor (Ubuntu)
Importance: Untriaged = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Needs Info = Confirmed
** Bug watch added:
I can't reproduce this because I don't see any of these system processes
in my list. How did you get those to list there?
--
Wrong password causes crash...
https://launchpad.net/bugs/60112
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Confirmed on up-to-date Edgy with the same gnome-system-monitor version
(2.16.0-0ubuntu1).
Darren: Maybe you're not in the admin group? I don't know if it might
affect gnome-system-monitor though, it's just a guess.
** Changed in: gnome-system-monitor (Ubuntu)
Assignee: (unassigned) =
It's probably because he's not gone to View - All Processes
Could someone get a debug traceback following the steps at
https://wiki.ubuntu.com/DebuggingProgramCrash
** Changed in: gnome-system-monitor (Ubuntu)
Assignee: Ubuntu Desktop Bugs = (unassigned)
Status: Confirmed = Needs
