On Mon, Jul 14, 2008 at 12:28:51PM +0200, Sven Joachim wrote:
> tags 489733 + lfs
> thanks
>
> On 2008-07-14 11:42 +0200, Mike Hommey wrote:
>
> > On Mon, Jul 07, 2008 at 02:57:09PM +0200, Sven Joachim wrote:
> >> Package: xulrunner-1.9
> >> Version: 1.9~rc2-5
> >> Severity: normal
> >>
> >> In the last few weeks I've been puzzled by a strange phenomenon. When I
> >> open the directory where I put my downloaded files
> >> (/home/sven/tmp/download) in Gecko browsers (iceweasel, conkeror,
> >> iceape), the listing is incomplete, it stops after 16 Kilobyte. Now I
> >> admit that I should really clean up that directory, but surely that's no
> >> reason not to display it completely.
> >>
> >> I've attached the listing as seen in iceweasel (via Ctrl-u) and the
> >> output of "ls -lA". Interestingly, other large directories such as
> >> /usr/bin and /usr/share/doc are not truncated.
> >
> > What version of iceweasel, conkeror and iceape did you try that with?
>
> The latest versions in unstable.
>
> > Does it also happen if you copy this directory to another location?
>
> Yes.
>
> > Could you zero out all files in the directory, and then put the result
> > in a tarball (after verifying it still triggers the bug)
> >
> > You could do the above with
> > cp -a /home/sven/tmp/download /tmp/download
> > find /tmp/download -type f -exec shred -n0 -x -z {} \;
> > tar -zcSvf /tmp/download.tar.gz -C /tmp download
> >
> > The resulting tarball should be small enough to be sent here.
>
> But it will not trigger the bug. Instead I have found a way to
> reproduce it:
>
> --8<---------------cut here---------------start------------->8---
> # create scratch directory
> mkdir /tmp/scratch
> cd /tmp/scratch
> # create a bunch of files for the listing
> touch $(seq 500)
> # create a big file
> dd if=/dev/zero of=sparse-file bs=1 count=0 seek=2G
> --8<---------------cut here---------------end--------------->8---
>
> => The listing of /tmp/scratch in the browsers is truncated.
>
> This will very likely not be reproducible under amd64, so you should get
> yourself an i386 chroot for it. In the original directory I have a 4G
> DVD image which triggered the problem.
That sounds familiar. I'm pretty sure there is another bug reported for
this issue, but I can't find it in the mass of bugs we have on
iceweasel/iceape/xulrunner...
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
