[02:01] <jdong> is there a way to tell rm -r not to recurse into another filesystem?
[02:01] <jdong> that's a mistake I can seriously see myself making some day
[02:15] <twb> jdong: you could use find -xdev -exec rm {} +
[02:15] <jdong> twb: yeah, good idea, might just do that
[05:05] <rmjb> lamont: I'm taking a crack at merging asmail
[05:06] <bddebian> I requested a sync of it today
[05:06] <jdub> assmail? awesome.
[05:06] <bddebian> And someone else already had a merge posted for it
[05:06] <bddebian> I got your assmail.. ;-P
[05:07] <rmjb> oh...
[05:08] <rmjb> you requested a sync? you're not keeping the libxext-dev build dep?
[05:14] <bddebian> Not necessary
[10:35] <jdub> hrmph. the only thing keeping restricted on my laptop is the ipw3945 binary. grr.
[10:38] <Burgundavia> jdub: indeed. madwifi for me
[02:00] <twb> Mithrandir: ping?
[02:47] <testsusf> hello im trying to figure out the script that checks the filesystem.. and im woundering.. what maked the files /fastboot and /forcefsck im currently looking at the checkfs.sh script in /etc/init.d/
[02:49] <testsusf> do anyone know
[02:52] <azeem> testsusf: please ask in #ubuntu
[02:52] <testsusf> they dont know
[02:52] <azeem> then ask elsewhere, this is not the right channel
[02:54] <twb> I've often had the problem where #ubuntu is full of people asking relatively simple (i.e. beginner) questions, flooding out anyone trying to work out something complex.  Is there an #ubuntu-experts or something?
[02:55] <Keybuk> heh
[02:56] <Keybuk> there should be
[02:56] <twb> What is the procedure for organizing one?
[02:56] <Keybuk> /join #ubuntu-experts
[02:56] <Keybuk> get other people to join too
[02:56] <Keybuk> announce it on ubuntu-devel-discuss or similar
[02:56] <twb> That's a bit de facto, but OK.
[02:57] <Keybuk> no official procedure
[02:57] <twb> I think #ubuntu-expert would be better.
[02:57] <bhale> seems i am the only person there
[02:58] <Keybuk> #ubuntu-i'm-a-developer-get-me-out-of-here? :p
[02:58] <twb> Ya
[02:59] <twb> The only problem, of course, is that now my modeline has [#ubuntu-d]  instead of [#u]  :-(
[02:59] <twb> Ah, c'est la vie.
[03:00] <mdke> maybe a separate channel for beginners would work better than a separate channel for experts
[03:00] <twb> mdke: I disagree strongly.
[03:01] <twb> New users will join #ubuntu, because they don't know any better.
[03:01] <BenC> mdke: Yeah, you don't want new people going into #ubuntu and then being told to go to #ubuntu-lusers
[03:01] <twb> Otherwise every second post to #ubuntu will be "go to #ubuntu-n00b, noob!"
[03:01] <mdke> I was simply thinking that this is the way the forum works, and it does a good job
[03:02] <twb> Yes, well, fora.
[03:02] <mdke> anyway, given the strength of your reaction, I won't pursue it
[03:02] <bhale> hah most of us have Views
[03:02] <bhale> best to live and let live
[03:34] <Keybuk> my gods, the dbus low-level API is evil
[03:34] <cypher1> Keybuk, hi
[03:35] <Keybuk> cypher1: hello
[03:41] <twb> I say we go back to abacusen
[03:42] <bluefoxicy> low level api?  It doesn't have a high-level abstraction layer?
[03:43] <Keybuk> bluefoxicy: it has them for GTK+, Qt, etc.
[03:44] <twb> What about ncurses?
[03:44] <twb> I mean, surely dbus is independent of the UI toolkit you use?
[03:44] <bluefoxicy> wtf
[03:44] <bluefoxicy> how the hell do you need a tool kit to pass data around
[03:45] <bluefoxicy> what exactly is d-bus for now
[03:45] <jdub> Keybuk means glib and Qt
[03:45] <Keybuk> jdub: glib is just the GTK+ library
[03:45] <jdub> (and the non-UI Qt bits with Qt 4)
[03:45] <bluefoxicy> ah
[03:45] <bluefoxicy> glib makes more sense though
[03:46] <jdub> Keybuk: "no"
[03:46] <Keybuk> jdub: yes; I know they like to think of it as a generic library, but it's *FAR* too heavy
[03:47] <Keybuk> and far too closely tied to GTK+
[03:47] <jdub> hardly
[03:47] <Keybuk> the fact it's the library that implements the GTK+ object system, signal system, etc.
[03:47] <Keybuk> glib is *HUGE*
[03:48] <Keybuk> it's ten times the size of upstart, for example
[03:48] <Keybuk> entirely inappropriate for linking there
[03:49] <jdub> that's a forced example
[03:49] <Keybuk> why is it?
[03:49] <Keybuk> it's the relevant example
[03:49] <jdub> it's unnecessary, and /usr
[03:49] <jdub> not even on the radar
[03:49] <Keybuk> eh?
[03:50] <Keybuk> it was very much on the radar
[03:50] <jdub> and then you worked out the obvious
[03:51] <Keybuk> which is that glib is only suitable for projects using GTK+, or non-GTK components of the same project
[03:51] <Keybuk> and that if you are writing a project that doesn't involve GTK+ at all, it's far too heavyweight and there are more suitable libraries or code collections
[03:52] <jdub> well, no, but i'll leave you to it
[03:53] <Ng> on the other hand, a typical desktop has glib loaded anyway
[03:54] <BenC> wow, the buildd's look totally fucked
[03:54] <BenC> https://launchpad.net/+builds/+build/286708
[03:54] <BenC> the builds log there for linux-meta shows it trying to build kdebluetooth
[03:55] <BenC> linux-meta got put into depwait because of libopenobex1-dev, because kdebluetooth failed to build :/
[03:56] <BenC> On i386, the linux-meta build shows
[03:56] <BenC> Automatic build of swig1.3_1.3.29-2.1ubuntu1 on rothera by sbuild/i386 1.170.5
[03:59] <Keybuk> interesting
[04:34] <mdke> do the cds still include windows foss software?
[04:54] <wasabi_> So... apport. Are we going to replace bugbuddy with this?
[04:54] <Lathiat> that seems to have happened already?
[04:55] <wasabi_> hmm did it. sure though I'd seen bug buddy recently.
[04:58] <dsas> bug-buddy is still used in most (all?) gnome apps
[05:00] <wasabi_> Heh. Nice. Another change which seems to have ignored evms/lvm users.
[05:01] <wasabi_> My /boot partition is now listed in the disk mounter app. And it lets me mount it.
[05:01] <wasabi_> Except, it's already mounted.
[05:03] <mdke> wasabi_: what's the disk mounter app?
[05:05] <wasabi_> It's that gnome panel app. They appear in nautilus too
[05:05] <mdke> ah that one
[05:06] <wasabi_> bug#76177
[05:06] <wasabi_> Ubugtu: ?
[05:07] <wasabi_> He must not like me. =(
[05:07] <crimsun_> bug 76177
[05:07] <Ubugtu> Malone bug 76177 in nautilus "allows mounting of partitions that are already mounted (corruption!)" [Critical,Unconfirmed]  http://launchpad.net/bugs/76177
[05:07] <wasabi_> oh, spaces. =(
[05:11] <bluefoxicy> what
[05:11] <bluefoxicy> you can mount the same partition twice wtf
[05:12] <wasabi_> dev mapper stuff.
[05:12] <bluefoxicy> oh
[05:12] <bluefoxicy> yeah, then it becomes 2 different devices to the kernel and the FS driver
[05:12] <bluefoxicy> last I looked mounting /dev/hda5 on /mnt/1 and /mnt/2 just kind of hooked up two mount points to the same VFS object
[05:13] <wasabi_> Actually it should error saying it's already  mounted.
[05:13] <bluefoxicy> hmm.. in that case it'd be a kernel issue, not nautilus
[05:14] <wasabi_> Don't really think so.
[05:14] <wasabi_> Probably more likely hal.
[05:17] <wasabi_> Well, it's HAL which is advertising it as mountable... so, it's either HAL's decision to not do so, or somebody elses decision to tell HAL not to.
[05:23] <Lure> wasabi_: this is probably related to changes done by pitti (hal)
[05:24] <wasabi_> Yeah, looks like all known partitions are shown now.
[05:24] <wasabi_> And sure enough, that's know.
[06:19] <_MMA_> Hi guys. Can anyone point me to who works on Usplash?
[06:19] <bSON> hi
[06:20] <bSON> the ubuntu version of gnome-session's gnome-wm script must be updated to support compiz like the upstream version
[06:21] <neuralis> _MMA_: you want to talk to mjg59.
[06:21] <_MMA_> neuralis: Thank you. Where is he located? Im in the states.
[06:22] <neuralis> _MMA_: uk.
[06:22] <_MMA_> Thanx again.
[06:22] <_MMA_> mjg59: ping
[06:28] <adam0509> hello, I wrote about (important) bug in Dapper/Edgy, but I didn't get any feedback yet...
[06:28] <adam0509> so please check : 
[06:28] <adam0509> https://bugs.launchpad.net/distros/ubuntu/+bug/75097
[06:29] <Ubugtu> Malone bug 75097 in Ubuntu "Ubuntu Dapper/Edgy can't mount some CD-Drive" [Undecided,Unconfirmed]  
[06:30] <adam0509> thanks Ubugtu ;)
[06:30] <mdke> you have to be quite patient - there are 20,000 bugs filed, it takes some time to go through them
[06:30] <adam0509> okay... if you say so
[06:30] <adam0509> But I hope it will be fixed in Feisty...
[06:50] <owh> Keybuk: Would you have a moment to discuss bug #48806?
[06:50] <Ubugtu> Malone bug 48806 in sysvinit "vfat filesystems checked by fsck" [Wishlist,Confirmed]  http://launchpad.net/bugs/48806
[06:52] <owh> Keybuk: The bug is marked as wishlist and I was wondering how a bug that causes data loss could be marked as such.
[06:54] <owh> Keybuk: I realise that a work-around, by not having the fs being checked during boot would not be an actual fix, so would it be fair to say that a resolution could be provided in two steps, an initial fix that stops the vfat partitions from being checked and an actual fix that fixes dosfsck - or am I being a dummy and you're already doing this?
[06:55] <owh> @now London
[06:56] <Ubugtu> Current time in Europe/London: December 17 2006, 17:56:03 - Next meeting: Technical Board in 2 days
[06:56] <stefg> around tea-time, I'd guess :-)
[06:56] <owh> Hmm, perhaps Keybuk is chewing on food :-)
[06:56] <owh> @now Perth
[06:56] <Ubugtu> Current time in Australia/Perth: December 18 2006, 01:56:49 - Next meeting: Technical Board in 2 days
[06:57] <owh> Hmm, and that time does not include day light saving :-)
[06:57] <owh> stefg: I'll send him an email.
[07:00] <owh> stefg: FYI: owh==onno-itmaze on launchpad
[07:00] <stefg> thx ..chew...chew...
[07:05] <owh> stefg: How do I get in touch with you?
[07:06] <Keybuk> ajmitch: ping?
[07:07] <Keybuk> owh: arguably the bug there is in dosfsck for corrupting the filesystem
[07:08] <owh> Keybuk: That was exactly how I read it too.
[07:08] <owh> Keybuk: Would it be fair to suggest a fix in two stages?
[07:09] <Keybuk> owh: if you can find a non-error-prone way to fix the boot fsck
[07:09] <owh> Keybuk: Am I incorrect in understanding that marking column 6 as 0 does not prevent the check?
[07:10] <owh> Uhm in fstab that should be.
[07:10] <Keybuk> that's true, yes
[07:10] <Keybuk> 0 means fstab won't check the filesystem
[07:11] <owh> So, would that give the users of an fstab filesystem less of a heart-attack?
[07:11] <stefg> which is advisable, if the fscker is chewing your files....
[07:11] <owh> I realise that this won't actually fix the problem.
[07:12] <stefg> sudo chmod -x dosfsck ....
[07:12] <Keybuk> the trouble is, there's no way to do that
[07:13] <owh> I don't understand what you're telling me.
[07:13] <Keybuk> not without disabling checking on filesystems that the user might actually have wanted checked
[07:13] <Keybuk> no way to modify fstab "properly"
[07:13] <wasabi_> So... I notice that we are now listing all partitions in UI such as nautilus.
[07:13] <wasabi_> That's hal making that decision right?
[07:13] <owh> You mean, parse fstab and change the appropriate value, or do you mean something else?
[07:14] <owh> Or do you mean detect which ones to disable at some (installation) time?
[07:17] <stefg> The real problem is not that the fstab isn't 'right'... having it checked would be a valid choice if dosfsck would work... so it's dosfsck that must be  fixed, not /etc/fstab ( or dosfsck must be disabled, as long as it is not fixed). 
[07:17] <Keybuk> owh: ?
[07:18] <owh> Yes, but fixing dosfsck is a much bigger problem, the actual fix, the first step is to stop trashing someone's filesystem.
[07:18] <Keybuk> we can't stop trashing them
[07:18] <stefg> yup, by disabling it altogether
[07:18] <Keybuk> that's what I'm saying
[07:18] <Keybuk> not without disabling checking where a sysadmin has explicitly enabled it
[07:18] <owh> Ah, now we're talking on the same page :-)
[07:19] <owh> Yes, I understand that changing fstab doesn't actually fix the issue.
[07:19] <Keybuk> changing fstab causes another issue
[07:19] <owh> So, is there a sane default, that is, don't check?
[07:19] <owh> What issue does it cause?
[07:20] <Keybuk> it would disable checking of fat filesystems that should be checked
[07:20] <Keybuk> and that the user has explicitl
[07:20] <Keybuk> +y marked to be checked
[07:20] <stefg> No, there's in insane default that eats peoples files, without a chance to prevent that (except interupting the installation and changin fstab manually)
[07:20] <mjg59> Keybuk: We still don't autoload modules on isapnp systems?
[07:21] <owh> So, would a work-around be a wrapper script around dosfsck that checks the fs-type and only checks fat16 and spits out a warning and does nothing if it's a fat32?
[07:21] <Keybuk> mjg59: uhh, we autoload those lists of modules in /etc/modprobe.d/isapnp
[07:21] <mjg59> Keybuk: Ah, so not really :)
[07:21] <owh> That is, until dosfsck is actually fixed.
[07:21] <mjg59> Keybuk: We should handle soundcards in that
[07:22] <Keybuk> mjg59: to my knowledge the kernel still isn't exporting a MODALIAS from the pnp subsystem, and still isn't exporting aliases from pnp drivers
[07:22] <mjg59> They all provide modalias lines, but they don't seem to get properly associated with them
[07:22] <Keybuk> mjg59: right, some do; but the kernel doesn't generate a MODALIAS for pnp devices
[07:23] <mjg59> They're exported via /sys/bus/pnp
[07:23] <mjg59> Surely we can hack around that?
[07:23] <Keybuk> no, they're not
[07:23] <Keybuk> ls: /sys/bus/pnp/devices/*/modalias: No such file or directory
[07:23] <mjg59> Keybuk: /sys/bus/pnp/*/id
[07:23] <Keybuk> that's not the modalias strng
[07:23] <mjg59> No
[07:23] <Keybuk> and doesn't match the modalias strings
[07:23] <mjg59> But it's a unique identifier
[07:23] <Keybuk> no, it's not unique
[07:23] <mjg59> Keybuk: For the hardware, it is
[07:23] <Keybuk> no
[07:23] <Keybuk> they're classes
[07:24] <Keybuk> (you know this :p)
[07:24] <mjg59> For the devices we care about, they're not
[07:24] <Keybuk> and you know that we both tried to turn those id lists into a unique string that matched the device
[07:24] <Keybuk> and failed
[07:24] <mjg59> No, the issue was that we couldn't figure out WTF the modalias lines in the modules referred to
[07:24] <Keybuk> we seem to have this conversation about once every 6 months, at about this point in the release <g>
[07:24] <mjg59> So we probably ought to get someone to tell us that
[07:27] <Keybuk> I've tried that, didn't get anywhere
[07:27] <Keybuk> the kernel should be exporting MODALIAS for the devices
[07:27] <Keybuk> after all, it can match devices and drivers
[07:27] <Keybuk> BenC may be able to help
[07:28] <owh> Keybuk: I've just been googling a little and came across this: How to determine the width of a FAT: http://homepages.tesco.net/J.deBoynePollard/FGA/determining-fat-widths.html
[07:32] <owh> Keybuk: Also: http://homepages.tesco.net/J.deBoynePollard/FGA/determining-fat-widths.html
[07:34] <owh> Keybuk: So, is a good summary of the issue: "dosfsck is broken. If we let it loose on fat32 it kills it. We cannot disable it because some users want to check their fat12/fat16 drive (which presumably isn't broken). We cannot turn off fsck for FAT volumes because of this."
[07:35] <Treenaks> owh: so if you can make it detect fat32 and abort, all is well?
[07:36] <owh> Well, in as far as the fat32 won't be hosed, yes.
[07:36] <owh> But if you want to check a fat32, then it won't check it.
[07:36] <owh> So, you will get behaviour where the admin sets that they want to check the filesystem, but a fat32 won't be checked.
[07:37] <mjg59> We could fix dosfsck
[07:37] <owh> That's my understanding of the problem.
[07:37] <owh> mjg59: That of course is the real fix :-)
[07:38] <sistpoty> what's wrong with dosfsck? how to reproduce?
[07:39] <owh> sistpoty: It appears to trash a fat32 volume.
[07:39] <owh> sistpoty: From my reading, any fat32 volume, but that may be wrong.
[07:39] <owh> sistpoty: It seems to die on long file names.
[07:39] <sistpoty> owh: hm... I didn't find any corruption of my fat32 volume yet... and I bet there are long filenames
[07:40] <owh> Hmm, that's interesting.
[07:40] <sistpoty> owh: might be interesting to first find out exactly *when* dosfsck does stuff wrong
[07:40] <sistpoty> but maybe I just didn't recognize corruption yet *g*
[07:41] <owh> sistpoty: Up to right now, when you said that I was under the impression that it always trashed it. Have you done a fscheck in DOS afterwards?
[07:41] <owh> +or Doze.
[07:41] <sistpoty> owh: I assume so, I did... but I'll find out in a minute... brb
[07:44] <_MMA_> mjg59: Im wondering if you can point me to current documentation for Usplash and or whomever is working on the Feisty Usplash.
[07:46] <finalbeta> _MMA_, you can probably find the information you want here :http://www.netsplit.com/blog/articles/category/upstart
[07:47] <mc44> _MMA_: try Seveas 
[07:47] <mc44> finalbeta: usplash!=upstart
[07:47] <finalbeta> lols, indeed. sry
[07:48] <_MMA_> :)
[07:48] <_MMA_> np
[07:48] <sistpoty> owh: re... nope, xp file check thingy didn't yield any errors
[07:48] <mjg59> _MMA_: What documentation currently exists is what's in the package
[07:48] <Seveas> _MMA_, docs -> apt-get install usplash-dev
[07:48] <Seveas> and for feisty afaik nothing big happened yet
[07:48] <owh> sistpoty: Well I'm glad to see that :)
[07:48] <mjg59> There's no real development planned for usplash other than bug fixing. It does pretty much what we want it to.
[07:48] <_MMA_> Thanx Serveas. I need to figure it out for Ubuntu Studio.
[07:49] <Seveas> mjg59, well, I have some theming improvements planned, but that's minor
[07:49] <owh> So now we have a bug that trashes *some* fat32 filesystems.
[07:49] <_MMA_> I was mot looking for what its capable of.
[07:49] <_MMA_> s/mot/more
[07:50] <sistpoty> owh: hm... I do have filenames > 8 chars... but it would be really interesting when/what is being crashed
[07:50] <owh> sistpoty: I wholeheartedly agree with you.
[07:50] <owh> I also suspect that the bug shouldn't be allocated to sysvinit.
[07:51] <owh> I think that's just a symptom.
[07:52] <sistpoty> owh: hm... but my fat32 partition is only 80Gb. maybe it's related to the size of the partition
[07:52] <owh> sistpoty: Hmm, lemmie see if the person who came to me told me how big their partition was. One mo...
[07:53] <sistpoty> owh: 140 Gb
[07:53] <_MMA_> Seveas: Would you chat with me on -artwork please? :)
[07:55] <owh> sistpoty: Was that in the bug report or on the channel?
[07:55] <sistpoty> owh: bug report
[07:56] <owh> sistpoty: Yeah, I saw that, I was trying to add another data point :-)
[07:57] <owh> sistpoty: Look at that: Bug #47215
[07:57] <Ubugtu> Malone bug 47215 in dosfstools "fsck.vfat hangs, eats CPU on problematic file" [Medium,Unconfirmed]  http://launchpad.net/bugs/47215
[07:57] <owh> Well, we can confirm it :-)
[07:58] <owh> sistpoty: It's a bit scant on detail ;-)
[07:58] <sistpoty> hm...
[08:00] <owh> sistpoty: There's another one, that truncates a file, looks to be > 4Gb file. Bug #62831
[08:00] <Ubugtu> Malone bug 62831 in dosfstools "fsck.vfat truncates files of 4294967295 bytes length to 0 bytes at boot-time" [Undecided,Unconfirmed]  http://launchpad.net/bugs/62831
[08:01] <owh> sistpoty: That report actually tells us how to reproduce it. I wonder if it's all the same bug?
[08:01] <sistpoty> owh: that would at least give some hints where the bug originates
[08:03] <owh> sistpoty: From reading the reports, not having seen a single line of code I would suspect that there is an assumption being made that is a FAT16 assumption, a pointer is being trashed and the application sh*ts itself and writes the wrong information to disk. But that's *speculation* only.
[08:04] <owh> sistpoty: Whoa, there's a pile of them: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=dosfstools;dist=unstable
[08:08] <sistpoty> owh: I'll try to reproduce this bug. maybe the fix is trivial... but first I'll grab s.th. to eat, so I'll probably be afk for an hour
[08:08] <owh> sistpoty: Hmm, it's 4am here, I am slinking off to bed :-)
[08:08] <sistpoty> gn8 owh
[08:08] <owh> sistpoty: I'll check in in the morning :-)
[08:09] <owh> sistpoty: owh==onno-itmaze on launchpad.
[08:09] <sistpoty> owh: ok, thx
[08:20] <ajmitch> Keybuk: pong
[08:34] <Keybuk> ajmitch: did you get much further with the selinux patch for upstart?
[08:38] <ajmitch> haven't had time due to work
[09:14] <soothsay> I'm trying to package something (for myself) for the first time. I'm using debhelper. It's a library and seems to compile cleanly and also seems to install into the correct directory when using prefix. I run dh_make, edit control and then run dpkg-buildpackage -rfakeroot. The package appears to be built cleanly but the .deb is essentially empty (only Copyright notice and changelog). What am I doing wrong?
[09:14] <soothsay> gen_control gives a warning unknown substitution variable ${shlibs:Depends}
[09:15] <soothsay> same for ${misc:Depends}
[09:16] <gpocentek> soothsay: could you upload your package somewhere, and move this discussion to #ubuntu-motu ? :)
[09:17] <soothsay> The source or the deb?
[09:17] <soothsay> Will goto motu
[09:19] <soothsay> Sorry BTW. Didn't read the topic :(
[10:06] <bluefoxicy> this is so weird
[10:07] <bluefoxicy> connect(4, {sa_family=AF_FILE, path="/tmp/ssh-IBZEow7532/agent.7532.seahorse"}, 110) = 0
[10:07] <bluefoxicy> ^^^ ssh
[10:08] <Fujitsu> I don't think that to be particularly weird, nor particularly appropriate for random insertion into a development channel.
[10:08] <bluefoxicy> Fujitsu:  ssh hangs on feisty, for me only.
[10:08] <bluefoxicy> also yeah
[10:21] <mdke> can it be that someone doesn't read my blog?
[10:21] <ajmitch> sadly so
[10:21] <mdke> outrageous.
[10:21] <ajmitch> I know
[10:21] <ajmitch> who wouldn't hang off your every word?
[10:23] <mdke> what's his real name? I'll email him
[10:24] <mdke> gosh, not only does he not read my blog, he conceals his real name too. Outrageouser and outrageouser
[10:28] <jmantha> mdke: totally
[10:29] <mdke> bluefoxicy: ah, there you are. See bug 76030
[10:29] <Ubugtu> Malone bug 76030 in seahorse "ssh (client) stops working after upgrade to Feisty" [Undecided,Confirmed]  http://launchpad.net/bugs/76030
[10:31] <bluefoxicy> mdke:  saw your link.
[10:32] <mdke> bluefoxicy: relieved to hear it
[10:33] <bluefoxicy> and it works, yay.
[11:18] <sistpoty> owh: still awake?
[11:18] <owh> Nope, just came back online with a strong coffee in hand :-)
[11:18] <sistpoty> hehe
[11:18] <sistpoty> owh: I'm just about to test if I can reproduce the bug
[11:19] <owh> sistpoty: How did you do that, with a large file?
[11:20] <sistpoty> owh: yes... in a minute I'll know more ;)
[11:20] <owh> The suspense is killing me :-)
[11:22] <sistpoty> owh: hm... no result :(
[11:22] <sistpoty> yep
[11:23] <sistpoty> didn't find anything, at least with -n
[11:23] <owh> Is there any point in contacting all the reporters and asking them for more information?
[11:23] <sistpoty> owh: let me retry without -n... maybe that will lead to results
[11:25] <owh> The reports in Debian point to "weird" characters in file names, back slashes and spaces - one report is on Japanese characters, could it be a character set problem?
[11:26] <sistpoty> owh: might be as well, no real clue
[11:31] <sistpoty> owh: hm... still no sign that dosfsck did anything to my partition. I'll restart xp and do a test... brb
[11:31] <owh> Cool
[11:40] <sistpoty> owh: nope, still no error or anything... *clueless*
[11:40] <owh> sistpoty: It appears that the last activity in this code was in May of 1998, making me wonder if we're barking up the wrong tree.
[11:41] <owh> sistpoty: Let me postulate: "What if the code is fine and the user data loss is a result of a corrupt FAT32 that the Windows version of scandisk does not properly fix or notice."
[11:42] <sistpoty> owh: hm... haven't thought about this one yet... 
[11:43] <sistpoty> owh: I guess we should ping submitters for further info, how to reproduce this bug
[11:44] <owh> sistpoty: I don't know if we're going to get any useful answers though. Most likely it will be along the lines of "a rabbit ate my data"
[11:44] <sistpoty> owh: it's always worth a try
[11:46] <owh> stefg said that the workaround of making fstab not check worked there, but I didn't get the opportunity to ask for further details. I've got to go and drop off my wife, back in 20 minutes, but I'm happy to ping the submitters of all the bugs that look the part.
[11:46] <sistpoty> owh: ok, would be great
[11:58] <twb> Mithrandir: ping?
[12:01] <owh> +k
[12:02] <owh> sistpoty: I'll draft a quick request for more information...
[12:02] <sistpoty> owh: thx... I've already written s.th. to 62831