** Changed in: hundredpapercuts
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1471459
Title:
First run of nano creates a
This bug was fixed in the package nano - 2.5.2-1
---
nano (2.5.2-1) unstable; urgency=medium
* New upstream release.
- Ignores $HOME when effective user is root, to avoid creating root-owned
files when for example invoking under sudo (LP: #1471459).
* Sync debian/nanorc
This has been addressed in nano's SVN, r5580. In version 2.5.2 and
higher, nano will ignore $HOME when it is effectively running as root,
and will therefore not create or change anything in the home directory
of the user that invokes nano through a plain sudo.
(It also means that it will not use
Anyone, what does 'grep -e storylog -e poslog /etc/nanorc' on Wily say?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1471459
Title:
First run of nano creates a directory
Paul, when you temporarily move ~/.nano and ~/.nanorc to different
names, does a run of 'sudo nano' then create a new ~/.nano?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
It turns out that Ubuntu carries a patch for sudo that Debian doesn't: see
keep_home_by_default.patch [1].
See also the changelog [2], somewhere in item 72. So I think one should ask
the Ubuntu maintainer of sudo what the motivation for this patch is. And if
there is no strong reason for it,
For those affected by the bug, could you please paste the output of
'sudo sudo -V | head -1', and of 'sudo sudo -V | grep -e ve: -e HOME',
and of 'sudo grep -v ^# /etc/sudoers'? Because if all things are at
their defaults, the sudo of Wily shouldn't be preserving HOME but should
be setting it to
Requested information. Fresh server installation from Wily daily a
couple of days ago:
doug@serv64-dev:~$ sudo sudo -V | head -1
Sudo version 1.8.12
doug@serv64-dev:~$ sudo sudo -V | grep -e ve: -e HOME
Environment variables to remove:
PYTHONHOME
Environment variables to preserve:
Current nano (2.4.2) will only check for the existence of $HOME/.nano/
(and create it when it doesn't exist) when 'set historylog' or 'set
poslog' are set in the $HOME/.nanorc file (or when the -H or -P options
are used on the command line). But... when nano is used for the very
first time (with
** Summary changed:
- Launching nano with sudo creates a root owned directory in $HOME
+ First run of nano creates a directory in $HOME, if run as sudo will be root
owned
** Description changed:
- If nano is started with sudo then a root owned directory .nano is
- created i a user's $HOME
10 matches
Mail list logo
