The latest patch solves it! (as confirmed on RH's bugzilla). Cyril, out of curiosity: is this bug report going to remain open while the patch finds its way upstream and/or to Debian's patchset? I would like to know more about the procedure if you have any pointers and don't mind.
Thanks to everyone! -- Eduardo. On Tue, Sep 28, 2010 at 5:45 AM, Debian Bug Tracking System <[email protected]> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian X Strike Force <[email protected]> > > If you wish to submit further information on this problem, please > send it to [email protected]. > > Please do not send mail to [email protected] unless you wish > to report a problem with the Bug-tracking system. > > -- > 591061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591061 > Debian Bug Tracking System > Contact [email protected] with problems > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
