Bug 163957 - gnome-system-monitor can't display NPTL threads
Summary: gnome-system-monitor can't display NPTL threads
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: libgtop2
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-22 13:30 UTC by Bastien Nocera
Modified: 2014-06-18 09:07 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2007-10-19 18:57:39 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 134831 None None None Never

Description Bastien Nocera 2005-07-22 13:30:46 UTC
Upstream bug:

gnome-system-monitor can't display NPTL threads when the "Show Threads" option
is on in the preferences.

How to reproduce (example):

1) start xmms with NPTL (e.g. xmms in an xterm should suffice)
2) confirm the presence of threads with "ps awuxm | grep xmms"
3) start gnome-system-monitor, enable threads and no threads are shown for xmms

4) now close xmms and start it with LinuxThreads (e.g. "LD_ASSUME_KERNEL=2.4.19
xmms" in an xterm)
5) gnome-system-monitor correctly displays threads

One idea was to completely remove the "Show threads" option from

Comment 1 Søren Sandmann Pedersen 2006-01-10 22:30:06 UTC
Upstream has now removed thread support completely in HEAD, so we can add a
patch to do the same.

Comment 2 Issue Tracker 2007-06-19 09:19:52 UTC
CRM autoclosed, closing

Internal Status set to 'Resolved'
Status set to: Closed by Tech
Resolution set to: 'Auto Closed'

This event sent from IssueTracker by pdemauro 
 issue 59237

Comment 3 RHEL Product and Program Management 2007-10-19 18:57:39 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.