FS#5870 - ls command segmentation fault (coreutils 6.5)

Attached to Project: Arch Linux
Opened by Alberto Gonzalez (Luis) - Tuesday, 21 November 2006, 13:24 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I upgraded coreutils to 6.5 and when I run 'ls' in my home directory I get a segmentation fault message. If I run 'dir' instead I do get my contents listed. And 'ls' works in other directories or even subdirectories of my home directory.

Downgrading to coreutils 6.4.2 solves the problem.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Tuesday, 21 November 2006, 20:24 GMT
Reason for closing:  Fixed
Comment by Apollon Oikonomopoulos (apoikos) - Tuesday, 21 November 2006, 15:50 GMT
I can confirm the same. The segmentation fault occurs when there is an entry in the current directory with uid or gid not listed in passwd or group. Try for example:

touch test
chgrp 123456 test
ls -l

and it should give you a segfault.
Comment by Tobias Powalowski (tpowa) - Tuesday, 21 November 2006, 18:14 GMT
what arch do you use 64 or 686?
Comment by Alberto Gonzalez (Luis) - Tuesday, 21 November 2006, 19:04 GMT
I use 686 arch.
Comment by Tobias Powalowski (tpowa) - Tuesday, 21 November 2006, 19:27 GMT
sorry cannot confirm, i did your example here it works
Comment by Apollon Oikonomopoulos (apoikos) - Tuesday, 21 November 2006, 19:46 GMT
i686 here as well, all packages up to date.
Comment by Apollon Oikonomopoulos (apoikos) - Tuesday, 21 November 2006, 19:53 GMT
It seems it's an upstream issue:
http://lists.gnu.org/archive/html/bug-coreutils/2006-11/msg00149.html

The resolution is here: http://lists.gnu.org/archive/html/bug-coreutils/2006-11/msg00153.html

I'm trying the patch to see if it works.
Comment by Apollon Oikonomopoulos (apoikos) - Tuesday, 21 November 2006, 20:06 GMT
The patch from http://lists.gnu.org/archive/html/bug-coreutils/2006-11/msg00153.html works for me.

Loading...