173032 2007-04-01 15:55 0000 sys-apps/coreutils-6.8 - funky error in ls -x on x86 2007-04-30 18:55:50 0000 1 1 1 Unclassified Gentoo Linux Core system unspecified All Linux RESOLVED FIXED P2 normal --- 1 g2boojum@gentoo.org base-system@gentoo.org oku.ns@dream.com g2boojum@gentoo.org 2007-04-01 15:55:10 0000 server ~ > mkdir ~/entries server ~ > cd ~/entries server entries > touch computers gentoo home server entries > /bin/ls computers gentoo home server entries > /bin/ls -x home gentoo home Clearly something is going wrong. It's interesting that the ls -x line appropriately allocates space for the first entry ("computers"), but then fills it with "home". server ~ # paludis --info paludis 0.22.1 Built by root@server on 2007-03-28T15:10:21-0500 CXX: i686-pc-linux-gnu-g++ 4.1.2 (Gentoo 4.1.2) CXXFLAGS: -O2 -mtune=i686 -pipe -fomit-frame-pointer LDFLAGS: DATADIR: /usr/share LIBDIR: /usr/lib LIBEXECDIR: /usr/libexec SYSCONFDIR: /etc stdlib: GNU libstdc++ 20070214 libebt: 1.3.0 libwrapiter: 1.0.0 sandbox: enabled Repository virtuals: Configuration information: format: virtuals Repository installed_virtuals: Configuration information: format: installed_virtuals Repository gentoo: Configuration information: buildroot: /var/tmp/paludis cache: /usr/portage/metadata/cache distdir: /usr/portage/distfiles eclassdirs: /usr/portage/eclass format: ebuild location: /usr/portage names_cache: /var/empty newsdir: /usr/portage/metadata/news pkgdir: /usr/portage/packages profiles: /usr/portage/profiles/default-linux/x86/2006.0 securitydir: /usr/portage/metadata/glsa setsdir: /usr/portage/sets sync: rsync://rsync.gentoo.org/gentoo-portage sync_options: write_cache: /var/empty Package information: app-admin/eselect-compiler: (none) dev-java/java-config: (none) dev-lang/python: 2.3.6, 2.4.4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r6 dev-util/confcache: (none) sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.15-r1 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.20-r2 Variable information: ACCEPT_KEYWORDS: AUTOCLEAN: CBUILD: i686-pc-linux-gnu CFLAGS: -O2 -mtune=i686 -pipe -fomit-frame-pointer CHOST: i686-pc-linux-gnu CONFIG_PROTECT: CONFIG_PROTECT_MASK: CTARGET: CXXFLAGS: -O2 -mtune=i686 -pipe -fomit-frame-pointer DISTDIR: /usr/portage/distfiles FEATURES: GENTOO_MIRRORS: INSTALL_MASK: LANG: LC_ALL: LDFLAGS: LINGUAS: MAKEOPTS: -j2 PKGDIR: PORTAGE_COMPRESS: PORTAGE_COMPRESS_FLAGS: PORTAGE_RSYNC_EXTRA_OPTS: PORTAGE_RSYNC_OPTS: PORTAGE_TMPDIR: /var/tmp/paludis PORTDIR: /usr/portage PORTDIR_OVERLAY: SYNC: USE: Repository installed: Configuration information: buildroot: /var/tmp/paludis format: vdb location: /var/db/pkg names_cache: /var/empty provides_cache: /var/empty root: / world: /var/db/pkg/world Repository local_overlay: Configuration information: buildroot: /var/tmp/paludis cache: /var/empty distdir: /usr/portage/distfiles eclassdirs: /usr/portage/eclass /usr/local/portage/eclass format: ebuild location: /usr/local/portage master_repository: gentoo names_cache: /var/empty newsdir: /usr/local/portage/metadata/news pkgdir: /usr/portage/packages profiles: /usr/portage/profiles/default-linux/x86/2006.0 securitydir: /usr/local/portage/metadata/glsa setsdir: /usr/local/portage/sets sync: sync_options: write_cache: /var/empty Thanks to mark_alec, who verified that the same bug occurs on a portage-based system, so that we can rule out paludis as being the cause of the problem (or me just being outright insane, for that matter). g2boojum@gentoo.org 2007-04-01 16:07:44 0000 Downgrading to sys-apps/coreutils-6.7-r1 "fixes" the problem, so it's definitely a 6.9 issue. vapier@gentoo.org 2007-04-01 23:41:47 0000 6.8 has same problem vapier@gentoo.org 2007-04-02 12:52:12 0000 talked with upstream and got this fixed ... it'll be in next coreutils version g2boojum@gentoo.org 2007-04-02 21:10:15 0000 Thank you very much; I definitely appreciate it. vapier@gentoo.org 2007-04-30 18:55:50 0000 *** Bug 176432 has been marked as a duplicate of this bug. ***