On Thu, Feb 25, 2010 at 12:24 AM, LyX Ticket Tracker <t...@lyx.org> wrote: > #6553: Assert on Opening the Edit menu to the left of a Math Inset <snip> > PS. Why don't you report this on the devel-list. Especially if it concerns > on-going business.
The literal answer to your question is "because the bugtracker seemed like the appropriate place to report bugs". In future should I also mention this on the list if there are recent regressions? Also there are a number of other Crash/Assertion bugs that seem to be left at Priority normal. Is this on purpose? In the bugs reported by me, is there more information required? Note that none of the bugs below are ones I have come across when actually using LyX, so it seems reasonable to me that these would be a lower priority than bugs that users hit frequently. -- http://tinyurl.com/yf5gj2r #6554 Crash on delete "List of Algorithms" in Embedded Objects Help File after saving. crash regression normal new defect gmatht #6552 Crash when inserting TeX-code in math mode and scrolling assertion normal new defect abcdefghijkl #6548 Assertion on pasting quote into math. assertion normal new defect gmatht #6514 Previewing '..lyx' can lead to assertion. assertion normal new defect gmatht #6513 LyX-Code assertion when changing document type to DocBook. assertion regression normal new defect gmatht #6482 Assert when searching backwards twice through two "Open documents" assertion normal new defect gmatht #6464 Crash when exiting LyX from second window when first window has changed buffer. crash normal new defect gmatht #6462 Out-of-bounds index in GuiErrorList::goTo when new buffer is active. assertion normal new defect gmatht #6453 SIGABRT in lyx::Paragraph::isSeparator assertion normal new defect gmatht #6267 Ocasional crash on Mac OS X. Intermittent. crash os=macosx normal new defect kghose -- John C. McCabe-Dansted
