On Sat, Sep 23, 2006, Attilio Fiandrotti wrote: > I never filed a bug into GNOME's bugzilla because no one ever was able > to reproduce this bug, but if someone can manage to achieve this (Loic? > :) we could file a proper bugreport to have ot fixed in next GTK release.
I would be happy to be a test puppet, but one of the reason I requested testing of Gtk 2.10 + DirectFB was that I don't know how to test it. I know it sounds a bit irresponsible, so I did my best to verify that I didn't break anything incrementally (but I still missed some stuff). I don't want you to lose too much time explaining me with details how your test environment is built, but if you could give some high level hints on the process you follow to test, what you test, and how you debug, that would be really nice. If such a documentation already exist, that would be nice! The most effective way for me would be to be able to test binaries from my laptop, perhaps from a different VT. I understand I might need to boot some d-i builds via the network or a CD in some cases. I also have a Xen setup, it it can help in any tests, and even a VMWare Workstation license (didn't update the kernel modules to 2.6.17 though). Thanks in advance for your help! Please don't feel obliged to document this in great length, I don't want to waste *your* time. -- Loïc Minier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
