Bug#468254: bash-completion: strange behavior on ls and spaces

Also, typing "ls \ " and pressing tab gives: "ls \\\ " With another tab: "ls \\\ " and so on... -- - Udi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#389157: noflushd: Noflushd uses up all the cpu-time it can get

I did a couple more backtraces and got different results (after detaching and reattaching): (gdb) bt #0 0xa7f2c410 in ?? () #1 0xaf9df678 in ?? () #2 0x08056468 in ?? () #3 0x0001 in ?? () #4 0xa7e9e423 in open () from /lib/tls/i686/cmov/libc.so.6 #5 0x0804dbef in sync_part (name=0x8054d

Bug#389157: noflushd: Noflushd uses up all the cpu-time it can get

OK it happened today and here's the backtrace: # gdb /usr/sbin/noflushd `pidof noflushd` GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under ce

Bug#389157: noflushd: Noflushd uses up all the cpu-time it can get

I get this too every week or so, after a daily script that spins up /dev/hda runs (noflushd has already spun it back down when it happens). /dev/sda is not ever spun down (not supposed to be). I'm using 2.6.18 with the Con Kolivas patchset (http://members.optusnet.com.au/ckolivas/kernel/). # ps a