[Bug 820895] [NEW] Log File Viewer does not log "Process Name"

Launchpad Bug Tracker 820895 at bugs.launchpad.net
Wed Jan 25 11:19:07 UTC 2012


You have been subscribed to a public bug:

The gnome "Log File Viewer" does not log the Process Name (or
Application Name) that generated the log item. For example, if an
outbound internet connection is blocked and this event is logged, only
the "ID" (i.e., PID) is shown in the report. But the PID is useless
because it is ephemeral and does not live past the session. Users are
left with no way to learn what Application or Process was responsible
for generating the log item.

The "Process Name" should be listed in log items instead of the PID.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-utils 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-33.71-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
Architecture: i386
Date: Thu Aug  4 08:05:47 2011
ExecutablePath: /usr/bin/gnome-system-log
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcEnviron:
 LC_TIME=en_GB.UTF-8
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gnome-utils
XsessionErrors: (polkit-gnome-authentication-agent-1:1444): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

** Affects: rsyslog (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: apport-bug i386 lucid
-- 
Log File Viewer does not log "Process Name"
https://bugs.launchpad.net/bugs/820895
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to rsyslog in Ubuntu.




More information about the foundations-bugs mailing list