[Touch-packages] [Bug 1053539] Re: lscpu crashed with SIGFPE in read_topology()
** Changed in: util-linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1053539 Title: lscpu crashed with SIGFPE in read_topology() Status in Util-Linux-ng: Fix Released Status in util-linux package in Ubuntu: Fix Released Bug description: when I run in the terminal lscpu gives me an error "floating point exception (`core 'generated)" ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: util-linux 2.20.1-5.1ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Thu Sep 20 19:44:38 2012 ExecutablePath: /usr/bin/lscpu InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120917) ProcCmdline: lscpu ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=es_ES.UTF-8 Signal: 8 SourcePackage: util-linux StacktraceTop: ?? () __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () ?? () Title: lscpu crashed with SIGFPE in __libc_start_main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1053539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 712892] Re: mount (silently) ignores options for bind mounts
** Changed in: util-linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/712892 Title: mount (silently) ignores options for bind mounts Status in Linux: Unknown Status in Util-Linux-ng: Fix Released Status in util-linux package in Ubuntu: Fix Released Bug description: Binary package hint: util-linux mount ignores any options given for bind mounts and adds an incorrect line to mtab. there is (at least) one exception: the option ro (== read-only). it warns that the bind mount is mounted read-write, if one tries to use that option together with bind. some examples of the current behavior (with comments): ~/bla# mkdir foo ~/bla# mkdir bar ~/bla# touch foo/test ~/bla# mount foo/ bar/ -obind,ro mount: warning: bar/ seems to be mounted read-write. # at least it says so ~/bla# rm bar/test ~/bla# ls bar/test ls: cannot access bar/test: No such file or directory # expected after that warning ~/bla# touch foo/test ~/bla# mount foo/ bar/ -obind,somebogusoption1 ~/bla# mount foo/ bar/ -obind,somebogusoption2 ~/bla# mount foo/ bar/ -obind,somebogusoption3 ~/bla# mount ... /root/bla/foo on /root/bla/bar type none (rw,bind) /root/bla/foo on /root/bla/bar type none (rw,bind,somebogusoption1) /root/bla/foo on /root/bla/bar type none (rw,bind,somebogusoption2) /root/bla/foo on /root/bla/bar type none (rw,bind,somebogusoption3) # mount adds bogus lines to mtab... ~/bla# ls bar/ test # but at least it does mount umount bar mount ... /root/bla/foo on /root/bla/bar type none (rw,bind) /root/bla/foo on /root/bla/bar type none (rw,bind,somebogusoption1) /root/bla/foo on /root/bla/bar type none (rw,bind,somebogusoption2) # and umount only removes one (bogus) line per execution :) the behavior is kinda documented in the manpage (well the bogus lines are clearly a bug (two actually), but i don't care right now). a workaround is to first bind mount and then use the remount option for setting other options e.g.: ~/bla# mount foo/ bar/ -obind ~/bla# mount bar/ -oremount,ro ~/bla# rm bar/test rm: cannot remove `bar/test': Read-only file system the problem is... this does not work with fstab: neither setting up one line with options bind,ro such as /root/bla/foo /root/bla/bar nonebind,ro (this gives the same warning as above) nor using two, one with the remount option: /root/bla/foo /root/bla/bar nonebind /root/bla/foo /root/bla/bar noneremount,ro (this even fails silently to remount read-only!) the warning was introduced by Karel Zak in november 2009. i read that debian had a patch for correcting at least some of the issues above, but i could not find anything. one workaround for certain situations could be to use pam_mount. this war reported/tested on ubuntu 10.10 with kernel 2.6.35-25 and mount 2.17.2-0ubuntu1.10.10.1. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/712892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 264555] Re: Link to www.namesys.com in 'man mount' is dead
Upstream fixed in v2.15. ** Changed in: util-linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/264555 Title: Link to www.namesys.com in 'man mount' is dead Status in util-linux package in Ubuntu: Fix Released Bug description: The link below in the manual page for 'mount' is dead: Mount options for reiserfs Reiserfs is a journaling filesystem. The reiserfs mount options are more fully described at http://www.namesys.com/mount-options.html. The owner of this URL, Hans Reiser, is in prison for murdering his wife. The site www.namesys.com no longer exists, though the name is still registered to Hans Reiser at his former address. If anyone is maintaining reiserfs, this link should be changed in the man file and other docs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/264555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 980835] Re: tty[1-6] is now root:tty 0660 instead of root:root 0600
** Changed in: util-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/980835
Title:
tty[1-6] is now root:tty 0660 instead of root:root 0600
Status in Util-Linux-ng:
Fix Released
Status in util-linux package in Ubuntu:
Fix Released
Bug description:
As of precise (2.20.1-1ubuntu3 to be exact), /dev/tty[1-6] now has the
following permissions:
$ ls -l /dev/tty[1-6]
crw-rw 1 root tty 4, 1 Apr 12 13:06 /dev/tty1
crw-rw 1 root tty 4, 2 Apr 12 13:06 /dev/tty2
crw-rw 1 root tty 4, 3 Apr 12 13:06 /dev/tty3
crw-rw 1 root tty 4, 4 Apr 12 13:06 /dev/tty4
crw-rw 1 root tty 4, 5 Apr 12 13:06 /dev/tty5
crw-rw 1 root tty 4, 6 Apr 12 13:06 /dev/tty6
In 11.10 and earlier (I checked back to hardy), the permissions were:
$ ls -l /dev/tty[1-6]
crw--- 1 root root 4, 1 2012-03-25 09:18 /dev/tty1
crw--- 1 root root 4, 2 2012-03-25 09:17 /dev/tty2
crw--- 1 root root 4, 3 2012-03-25 09:17 /dev/tty3
crw--- 1 root root 4, 4 2012-03-25 09:17 /dev/tty4
crw--- 1 root root 4, 5 2012-03-25 09:17 /dev/tty5
crw--- 1 root root 4, 6 2012-03-25 09:17 /dev/tty6
This appears to be because of this util-linux commit:
http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=3aa6b68f7e19fa3e1c2bba75bee921a98b7b46af
I'm not sure if this is a problem, but it isn't clear why the change was made
and I'm having a hard time knowing why the group was changed. This is the bit
of code that I think is the cause:
+ /*
+* There is always a race between this reset and the call to
+* vhangup() that s.o. can use to get access to your tty.
+* Linux login(1) will change tty permissions. Use root owner
and group
+* with permission -rw--- for the period between getty
and login.
+*/
+ if (chown (buf, 0, gid) || chmod (buf, (gid ? 0660 : 0600))) {
+ if (errno == EROFS)
+ log_warn("%s: %m", buf);
+ else
+ log_err("%s: %m", buf);
+ }
There might not be anything to do with this, but I am filing it to get
other's opinions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/util-linux-ng/+bug/980835/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 397564] Re: wall message should use HH:MM:SS in printing the time, to avoid ambiguity
** Changed in: util-linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/397564 Title: wall message should use HH:MM:SS in printing the time, to avoid ambiguity Status in Util-Linux-ng: Fix Released Status in util-linux package in Ubuntu: Fix Released Bug description: Binary package hint: util-linux wall normally looks like this: -- kirkland@t61p:/local/source/base-files$ echo Ambiguous | wall Broadcast Message from kirkland@t61p (/dev/pts/14) at 14:44 ... Ambiguous -- Note the 14:44 is only accurate to the minute. It would be much more useful to have the seconds in there as well. -- kirkland@t61p:/local/source/base-files$ echo Accurate | wall Broadcast Message from kirkland@t61p (/dev/pts/14) at 14:47:32 ... Accurate -- The patch is trivial, attached. Please include. :-Dustin To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/397564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406133] Re: findmnt: libsmartcols ASCII art problem [patch]
** Changed in: util-linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1406133 Title: findmnt: libsmartcols ASCII art problem [patch] Status in util-linux package in Ubuntu: Fix Released Bug description: The libsmartcols component used by findmnt to draw the filesystem tree is smart enough to wrap lines in case the output doesn’t fit into the screen. However, it fails to draw the lines correctly in this case. Attached patch fixes the problem. Someone more knowledgeable in libsmartcols internals might want to change the buffer size from an arbitrary 1024 to something taken from actual data, the best way to do that eludes me. Sample of incorrect output: --%< ├─/boot /dev/sda1 ext3 rw,relatime,data=ordered ├─/usr /dev/mapper/vgshadow-ubuntu_usr ext4 rw,noatime,data=ordered ├─/var /dev/mapper/vgshadow-ubuntu_var ext4 rw,noatime,data=ordered ├─/home /dev/mapper/vgshadow-home ext4 rw,noatime,data=ordered └─/srv /dev/mapper/vgshadow-srv reiserfs rw,noatime,notail --%< Patch adds missing vertical lines at any level necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1406133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
