command-not-found (0.2.4) feisty; urgency=low
[ Michael Vogt ]
* remove support for suggestins.d/ dir (not used currently and
may break stuff)
[ Zygmunt Krynicki ]
* Fixed launchpad #95794: warning emitted about not finding group name
* data files updated
[ Johan Kiviniemi ]
*
** Changed in: command-not-found (upstream)
Status: Fix Committed => Fix Released
--
warning emitted about not finding group name
https://launchpad.net/bugs/95794
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Also affects: command-not-found (upstream)
Importance: Undecided
Status: Unconfirmed
** Changed in: command-not-found (upstream)
Importance: Undecided => Low
Status: Unconfirmed => Fix Committed
--
warning emitted about not finding group name
https://launchpad.net/bugs/957
This is caused by invoking 'groups' without redirection. Fixed in the
trunk and in ubuntu-feisty-release branch.
--
warning emitted about not finding group name
https://launchpad.net/bugs/95794
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
This is caused by invoking 'groups' without redirection. Fixed in the
trunk and in ubuntu-feisty-release branch.
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Zygmunt Krynicki
Status: In Progress => Fix Committed
--
warning emitte
Thanks I'll try to reproduce this now
** Changed in: command-not-found (Ubuntu)
Status: Needs Info => In Progress
--
warning emitted about not finding group name
https://launchpad.net/bugs/95794
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
I'm using command-not-found 0.2.3, but it also occurs with all the
earlier version I've seen. Anything that triggers c-n-f will cause that
to be output, whether it finds something that has a matching package or
not.
After looking, I just noticed that somehow my user has a gid of 500, but
there is
Could you provide some more information:
- how to reproduce this
- which version of command-not-found are you using
- exactly which command you typed to trigger this
** Changed in: command-not-found (Ubuntu)
Status: Unconfirmed => Needs Info
--
warning emitted about not finding group
