On Tue, Jun 13, 2006 at 12:32:53AM +0200, Per Olofsson wrote: > Denis Barbier: > > On Mon, Jun 12, 2006 at 03:34:27PM +0200, Per Olofsson wrote: > > > > It looks a bit like this: > > > > > > > > http://lists.debian.org/debian-amd64/2005/05/msg00518.html > > > > > > > > Although not affecting as many apps.. > > > > > > Well, in any case it seems like it's a bug in the X libraries so I'm > > > reassigning it to libx11-6. > > > > Can you please reassign it back to lyx-xforms? > > At the moment, there is nothing in this bugreport to support your claim > > that it is caused by libx11-6. The backtrace shows > > 0xa7db4cb8 in XFindOnExtensionList (structure=0xc09, number=1040697125) > > and these arguments look clearly wrong, but we do not know where they do > > come from. > > Please work first with bug submitter to reproduce it, and then reassign > > it to libx11-6 if there is indeed a bug there, with explanations on how > > to reproduce it. I am afraid that Debian X maintainers cannot investigate > > random bugs in any X application. > > For instance, the following informations may be helpful: > > * Is X a local or remote display? > > * Does it crash when launched from a newly created account? > > * Does it crash at startup, or when processing a particular file? > > * Any special in user configuration? > > ... > > OK, I understand. I thought that this was maybe a known bug. > > I think lyx-xforms is deprecated anyway.
Just for the record, The answers to the above questions are: * Is X a local or remote display? local * Does it crash when launched from a newly created account? yes * Does it crash at startup, or when processing a particular file? startup * Any special in user configuration? not AFAIK (since new account has same segfault). Problem persists regardless of window manager. James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
