desktop-packages team mailing list archive

[Ayan George <ayan.george@xxxxxxxxxxxxx>]

** Changed in: oem-priority/oneiric
       Status: Fix Committed => Fix Released

** Changed in: gnome-nettool (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-nettool in Ubuntu.
https://bugs.launchpad.net/bugs/766862

Title:
  remote finger no longer work, local finger limited (pinky vs finger)

Status in GNOME Nettool:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project oneiric series:
  Fix Released
Status in “gnome-nettool” package in Ubuntu:
  Fix Released

Bug description:
  SRU Justificaiton
  -----------------

  Impact:

  This update allows remote finger to work if a proper finger client is
  installed.

  Fix:

  A minor code change that has gnome-nettool attempt to use the 'finger'
  before falling back to 'pinky' instead of vice-versa.

  Patch:

  The changes have been applied to gnome-nettool git master branch in
  commit 89e0bb648e9e8bd96a5eb5e0284abf74fc244c95.  I've attached a
  debdiff in comment #5.

  Regression Potential:

  There should be very little potential for regression.

  Test Case:

  * Install finger (sudo apt-get install finger)
  * Run gnome-nettool
  * Select the 'finger' tab.
  * Enter the hostname of a machine running a finger server and the username of a properly configured account.

  gnome-nettool should display the finger information returned by the
  remote host.

  ------------------------

  
  Binary package hint: gnome-nettool

  This is a duplicated entry for the gnome upstream bug#611408

  Simon Paillard [reporter] 2010-02-28 15:20:55 UTC

  Hello,

  This has been reported intially in http://bugs.debian.org/550991

  Remote finger no longer works.
  It seems the switch from finger to pinky caused a regression in finger feature.

  > gnome-nettool's finger functionality does not work.  If I try to finger
  > bmc@xxxxxxxxxxxxxxxxxxxxxxx or amu@xxxxxxxxxxxx (or anyone else, for
  > that matter), it sends no packets, and produces only the output:
  >
  >   Login    Name                 TTY      Idle   When             Where

  This seems to be a regression since 2.22.1-1, after the switch to pinky
  as finger program, introduced after the resolution of:
  https://bugzilla.gnome.org/show_bug.cgi?id=549588
  commit a9eaa17cdae8563e19e1afc2aebe64e534a4da85
  2008-12-04 02:56 German Poo-Caamano  Fixed #549588. Try to use pinky
  instead of finger. Use finger as fallback.

  $ pinky amu@xxxxxxxxxxxx
  Login    Name                 TTY      Idle   When         Where

  It doesn't seem pinky is able to do the same job as finger does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-nettool/+bug/766862/+subscriptions