| 2006-08-28 14:59:35 |
Rocco Stanzione |
bug |
|
|
added bug |
| 2006-08-28 15:13:40 |
Sebastian Dröge |
vim: status |
Unconfirmed |
Confirmed |
|
| 2006-08-28 15:13:40 |
Sebastian Dröge |
vim: statusexplanation |
|
I can confirm this behaviour here... not sure why it is owned by root though |
|
| 2006-08-28 23:30:07 |
Dennis Kaarsemaker |
vim: status |
Confirmed |
Rejected |
|
| 2006-08-29 00:40:31 |
Rocco Stanzione |
vim: status |
Rejected |
Unconfirmed |
|
| 2006-08-29 00:40:31 |
Rocco Stanzione |
vim: statusexplanation |
I can confirm this behaviour here... not sure why it is owned by root though |
I can easily work around this. I submitted this bug because:
a) it took me quite a while, even with help from #vim, to figure out why these things weren't working
b) it's probably not atypical that the first file edited after a fresh install must be edited as root
c) the failures happen quietly
therefore
d) I suspect quite a lot of users have a root-owned .viminfo that prevents vim from operating correctly, whether they're aware of it or not.
I can live with this bug being rejected, but I'd appreciate it if someone put some thought into it first. Maybe there could even be a discussion. |
|
| 2006-08-29 07:06:21 |
Dennis Kaarsemaker |
vim: status |
Unconfirmed |
Rejected |
|
| 2006-08-29 14:45:27 |
Rocco Stanzione |
vim: status |
Rejected |
Unconfirmed |
|
| 2006-08-29 14:45:27 |
Rocco Stanzione |
vim: statusexplanation |
I can easily work around this. I submitted this bug because:
a) it took me quite a while, even with help from #vim, to figure out why these things weren't working
b) it's probably not atypical that the first file edited after a fresh install must be edited as root
c) the failures happen quietly
therefore
d) I suspect quite a lot of users have a root-owned .viminfo that prevents vim from operating correctly, whether they're aware of it or not.
I can live with this bug being rejected, but I'd appreciate it if someone put some thought into it first. Maybe there could even be a discussion. |
I agree that vim is doing what it's supposed to do. But the result is a problem that's difficult to detect and even harder to track down. It's a consequence of the way we use sudo, which is a great idea, but not standard, and a lot of standard bugless things fail to accommodate it, so we have to make our own accommodations. For example, we put /sbin in the PATH of mortal users, which other distros don't do, because things like 'sudo ifconfig' wouldn't work otherwise. We could just say 'use sudo /sbin/ifconfig', but we don't. Users are editing files with sudo because they're supposed to, and something that nobody meant to happen (.viminfo is owned by root) is happening. Please leave this bug open until somebody (besides the guy who already confirmed it) can break the tie or something. |
|
| 2006-08-29 15:07:24 |
Sebastian Dröge |
vim: status |
Unconfirmed |
Confirmed |
|
| 2006-08-29 15:07:24 |
Sebastian Dröge |
vim: statusexplanation |
I agree that vim is doing what it's supposed to do. But the result is a problem that's difficult to detect and even harder to track down. It's a consequence of the way we use sudo, which is a great idea, but not standard, and a lot of standard bugless things fail to accommodate it, so we have to make our own accommodations. For example, we put /sbin in the PATH of mortal users, which other distros don't do, because things like 'sudo ifconfig' wouldn't work otherwise. We could just say 'use sudo /sbin/ifconfig', but we don't. Users are editing files with sudo because they're supposed to, and something that nobody meant to happen (.viminfo is owned by root) is happening. Please leave this bug open until somebody (besides the guy who already confirmed it) can break the tie or something. |
|
|
| 2006-08-29 21:04:25 |
Dennis Kaarsemaker |
vim: status |
Confirmed |
Rejected |
|
| 2006-08-29 21:21:09 |
Rocco Stanzione |
vim: status |
Rejected |
Confirmed |
|
| 2006-08-29 21:21:09 |
Rocco Stanzione |
vim: statusexplanation |
|
The problem is caused by vim, though it doesn't have a bug, and the symptoms are in vim. Maybe sudo should be modified, maybe some other package should put an empty .viminfo in /etc/skel, or maybe there's another solution. When the appropriate package is identified to apply the solution to, I'll assign this bug to that package. Meanwhile you're putting an awful lot of energy into making sure this doesn't get fixed. Please don't. |
|
| 2006-08-29 22:20:35 |
Paul Sladen |
vim: importance |
Untriaged |
Wishlist |
|
| 2006-08-29 22:20:35 |
Paul Sladen |
vim: statusexplanation |
The problem is caused by vim, though it doesn't have a bug, and the symptoms are in vim. Maybe sudo should be modified, maybe some other package should put an empty .viminfo in /etc/skel, or maybe there's another solution. When the appropriate package is identified to apply the solution to, I'll assign this bug to that package. Meanwhile you're putting an awful lot of energy into making sure this doesn't get fixed. Please don't. |
Ubuntu has a philosophy of "It just works", if there is anything we can do to make life saner for people, we should do.
The technically correct action for vim is probably to create the file chown root:root; so fixing the skel sounds a good workaround to me.
Dennis: please don't reject this (again), the case clearly exists; even if (as you are probably technically right) the issue may not be the fault of vim itself. Correcting the location of the issue is much better than a rejection, as it moves the situation forward.
Rocco: can you test the following:
sudo touch /etc/skel/.viminfo /etc/skel/.vimrc
sudo adduser test
su - test
sudo vi /etc/apt/sources.list
ls -l ~test/.vimrc
if that is not the correct solution, can you test again for '.vim/...'. Then these can be added to the 'vim' package. |
|
| 2006-08-29 22:22:19 |
Paul Sladen |
title |
.viminfo is owned by root and mode 0600 |
vim should populate skel/.viminfo so ownership is not affected by initial sudo |
|
| 2006-09-08 22:56:59 |
Matt Zimmerman |
title |
vim should populate skel/.viminfo so ownership is not affected by initial sudo |
vim creates root-owned files in user $HOME when run under sudo |
|
| 2006-09-08 22:58:53 |
Matt Zimmerman |
vim: importance |
Wishlist |
Medium |
|
| 2006-09-08 22:58:53 |
Matt Zimmerman |
vim: statusexplanation |
Ubuntu has a philosophy of "It just works", if there is anything we can do to make life saner for people, we should do.
The technically correct action for vim is probably to create the file chown root:root; so fixing the skel sounds a good workaround to me.
Dennis: please don't reject this (again), the case clearly exists; even if (as you are probably technically right) the issue may not be the fault of vim itself. Correcting the location of the issue is much better than a rejection, as it moves the situation forward.
Rocco: can you test the following:
sudo touch /etc/skel/.viminfo /etc/skel/.vimrc
sudo adduser test
su - test
sudo vi /etc/apt/sources.list
ls -l ~test/.vimrc
if that is not the correct solution, can you test again for '.vim/...'. Then these can be added to the 'vim' package. |
|
|
| 2006-09-08 23:09:25 |
Matt Zimmerman |
title |
vim creates root-owned files in user $HOME when run under sudo |
Some programs create root-owned files in user $HOME when run under sudo |
|
| 2012-04-24 22:00:11 |
Lesmana Zimmer |
bug |
|
|
added subscriber Lesmana Zimmer |
| 2013-05-07 13:58:19 |
Phillip Susi |
affects |
ubuntu |
vim (Ubuntu) |
|
| 2013-05-07 13:58:19 |
Phillip Susi |
vim (Ubuntu): status |
Confirmed |
Triaged |
|
| 2013-05-07 18:07:37 |
Micah Cowan |
removed subscriber Micah Cowan |
|
|
|
