[rox-users] Re: Launch more than one FreeFS = crash

[Stephen W. <st...@ke...>]

Kacper Wysocki <ka...@on...> wrote:

> My favorite way of tracking disk usage over mutiple disks while  
> reorganizing my files used to be opening one stand-alone FreeFS for  
> each partition- this way I had quick, constantly updated info about how  
> much space was being used at any given time while mucking about with  
> rox-filer. Sadly, this has not been working ever since I upgraded to  
> 1.5.1 (from some old version I don't even remember). Upon launch of a  
> second instance of FreeFS both instances crash giving the following  
> error:
> 
> "The program 'freefs' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadWindow (invalid Window parameter)'.
>   (Details: serial 597 error_code 3 request_code 19 minor_code 0)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()  
> function.)"
> 
> ...which is probably useless to you unless I actually do an strace or  
> backtrace. The problem also occurs in 1.4.2, AFAIK the newest release,  
> and I'm guessing it's been there since the migration to GTK2. I'd love  
> to know if anyone else is experiencing the same problem, and whether  
> there's anything I can do to allay the situation (I'm a novice in C,  
> but I do know how to provide a backtrace).

This is actually a bug in ROX-CLib which was (hopefully) fixed in version
1.1.3.  If you already have ROX-CLib 1.1.3 then I need to start worrying.

-- 
Stephen Watson     http://www.kerofin.demon.co.uk/

I woke up and I had a big idea/To buy a new soul at the start of every year
I paid up and it cost me pretty dear/Here's a hymn to those that disappear