** Description changed:
Binary package hint: byobu
<elmo> 16:46:26> Setting up byobu (2.68-0ubuntu1.1) ...
<elmo> 16:46:26> chown: invalid user: `asac'
<elmo> 16:46:33> thanks kirkland :-P
This needs to be handled more gracefully.
+
+ ====================
+ SRU
+ - Impact: Upgrading users could experience a problem with Byobu's postinst,
which touches a flag in each users' screen run directory. If a user's name has
changed since their screen run directory was created at boot, then Byobu's
chown procedure might fail. This is perhaps more likely to happen on long
running uptime servers.
+ - How addressed: The chown command used in Byobu's postinst was ugly and
naive. Instead, use chown --reference against the parent directory. Also, ||
true this command, as it's hardly essential to the package upgrade.
+ - How to reproduce: Create a test user, "foo". As user foo, start a byobu
session. Exit that session. Rename user "foo" to "bar". Note that
/var/run/S-foo still exists. Upgrade byobu. Byobu's postinst will touch
/var/run/S-foo/byobu.reload-required, and try to chown it to "foo", except
"foo" does not exist.
+ - Regression potential: Patch is trivial, clean, regression potential is
negligible.
+ - Minimal patch: http://paste.ubuntu.com/625633/
+ ====================
** Changed in: byobu (Ubuntu Lucid)
Status: Triaged => Fix Committed
** Changed in: byobu (Ubuntu Maverick)
Status: Triaged => Fix Committed
** Changed in: byobu (Ubuntu Natty)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796422
Title:
postinst chown can fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/796422/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
