> This is an automatic notification regarding your Bug report > which was filed against the gimp package: > > #509651: Gimp (2.2): Script Causes Crash, Then Writes to Drive at ~1GB/min > > It has been closed by Ari Pollak <[email protected]>. > > Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Ari Pollak > <[email protected]> by > replying to this email. > > > -- > 509651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509651 > Debian Bug Tracking System > Contact [email protected] with problems >
your response was: "Version: 2.4.0-1 There are multiple things going on here: - A misbehaving script interacting badly with gimp 2.2 - The gimp process wasn't exited cleanly, so it didn't clean up its temp files - Ext3 filesystems have space reserved for root by default" I'm not sure who responded to my original message, but this response is certainly not adequate. I'm sure you get false bug reports from noobs all the time, and maybe this is another one; however, I would like to point out that my time is at least as valuable as any member of the debian team. I spent many hours attempting to solve this bug and following the bug reporting instructions line-by-line, making a conscious effort to not waste someone else's time. Does the response I got mean that it has been decided that there is no bug. Does it mean that you don't care about bugs in gimp 2.2 because a newer version of gimp is available (I just checked again, and it says that my version of gimp, 2.2.13-1etch4, is the latest one for etch, which is the latest stable release)? Did anyone even run the script to duplicate the results? A program that allows a script to behave badly has a bug. I just checked the gimp documentation, and it didn't mention anything about the dangers of running new scripts on older versions (of course, it's the software's job to check). A program that doesn't clean-up it's temp files has a bug, especially when that program was restarted and closed "cleanly". Could you please tell me where these unclean temp files are? They aren't in my /tmp directory. Apparently, there is space reserved for root. I came across this explanation as a reason for a disk discrepancy. Silly me for dismissing it, thinking that it would be electronically insane to automatically reserve 10GB of space for root, bill gates would be proud. Because this is free software, I certainly don't expect anything; however, honesty is appreciated. If you don't care about this bug, please just be honest and say that you have no desire to create bug-free code. I can spend my valuable time figuring out a work around on my own. nate carr -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
