Your message dated Fri, 16 Jun 2006 17:49:03 +0300
with message-id <[EMAIL PROTECTED]>
and subject line [Closing] gnopstree: Serious problems, not worth packaging
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wnpp
Severity: wishlist
* Package name : gnopstree
Version : 0.76
Upstream Author : Rocky Bernstein <[EMAIL PROTECTED]
* URL : http://sourceforge.net/projects/gnopstree
* License : GPL
Description : Display running processes as a tree or forest (GTK+)
(Include the long description here.)
See picture at http://gnopstree.sourceforge.net/screenshot.jpg
The gnopstree is a program to display via GNOME/GTK the Unix processes
as a tree or forest; the roots of the tree are on the left-hand side
and the leaf processes (with no children) are on the right-hand
side. The status of each process (running, sleeping, stopped, etc.)
can be indicated by a color. Different users can appear as different
colors too.
Within each level, processes are grouped so that those with the same
parent process id are grouped together. Within this, processes are
arranged by userid with lower number uid's appearing towards the
top. In general, the order of children is the order in which they were
spawned, with the older processes appearing towards towards the top.
In contrast to pstree and many tree-widget based programs, the overall
tree display uses diagonal lines; some effort is made to effectively
use the full 2-dimensional area of the screen by balancing levels and
centering the children of a node between their parent. A goal of the
program is to give a picture of what's going on. When possible,
processes are kept close to their parents so one needn't scroll around
too much and so that there isn't a lot of redrawing as processes are
created or destroyed.
One can click on a process to get more information (via ps) about that
process, send a signal to the process, or set its priority, assuming
you have the permission to do so. Since programs of this ilk can
consume a bit of CPU on their own, some effort has been made to turn
off the update process when the program is iconified or not visible.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
--- End Message ---
--- Begin Message ---
tags 311323 - pending
thanks
The program segementation faults when exited and prints lot of errors
when started/running. Too old, Not worth packaging. Removed from
Debian sponsors site as well.
GnomeUI-CRITICAL **: file gnome-canvas.c: line 1275
(gnome_canvas_item_reparent): asertion `GNOME_IS_CANVAS_ITEM (item)' failed.
GnomeUI-CRITICAL **: file gnome-canvas.c: line 1275
(gnome_canvas_item_reparent): asertion `GNOME_IS_CANVAS_ITEM (item)' failed.
--- End Message ---
