Re: [Tuxpaint-users] Problems Saving File

[Bill K. <nb...@so...>]

On Wed, Jan 27, 2010 at 07:31:09AM -0800, henry taylor wrote:
> No                                                                                   
>                                                                                      
> when it occurs I get a report about different starter images failure OR an audio     
> device failure message. Its intermittent and I am not sure about any pattern...      

As I discovered, the error that Tux talks about is usually unrelated to the
error that occured.  It seems I mistakenly expected "strerror()" to return
something related to PNG saving when the PNG library throws an error.
Unfortunately, it doesn't seem to set that, so you get whatever was leftover
(e.g., the unimportant error about a Starter image lacking a background -- something
you'd see if you hit "New" first, and then "Save", which fails -- or the
error about the audio device).


> These are all networked machines and I know that problems occur sometimes when a     
> specific machine fails to hook into the network... tho USUALLY this will also        
> preclude finding and opening the program which is on located on a networked drive    
> not on the specific computer.

Do you know, for certain, where Tux Paint is trying to load/save pictures?


> And I have one machine which which is not connected to the same network but seems to 
> believe that it is connected and successfully saving tho no image is ever found. I'm 
> not worried about that machine tho.

It looks like it can, indeed, fail to save, but still report successful saving.
Which is just awful, in my opinion, and I'm sorry we didn't stress-test these
situations more.

(One problem is that I have a single computer, running Linux.  No access to the
wide variety of setups that people use: Windows/Mac/Linux, fat-client/thin-client,
networked-saved/locally-saved, network-loaded/locally-loaded, etc.)

This is where I'd love to see a real QA (quality assurance) team set up.
Prior to offical releases, we'd have people go through and test every aspect of
the program, to see if any bugs cropped up, or there were any regressions
(bugs that were thought fixed, but weren't actually fixed, or came back due to
another code change).


-bill!