(In reply to comment #13) > (In reply to comment #11) > > ... since it is a gtk bug in the first place. > > So, has this in fact been reported to gtk? Anyone have a link to the bug > report?
My question stands unanswered.
(In reply to comment #13)
> (In reply to comment #11)
> > ... since it is a gtk bug in the first place.
>
> So, has this in fact been reported to gtk? Anyone have a link to the bug
> report?
My question stands unanswered.