Re: serious bug (fedora issue?)
Le 05/01/2019 à 20:46, Patrick Dupre a écrit : Hello, Was the information that I provided useful? I also have to face other crash issues. I will try to communicate after the previous one have been solved. Dear Patrick, I just stumbled on your posts while looking at my old inbox content before leaving in vacation... I am very sorry that we did not follow up on this. Do you still experience this painful situation? What I see from the log is that : 1/ the spellchecker is launched (#53-#56) 2/ it sets selection and triggers explicitly an update (#52-#53) 3/ this eventually triggers the computation of metrics for a graphics 4/ the graphics is loaded (so presumably it was not yet the case) 5/ this in turn causes a call to an external unzip program (#41-#40) 6/ the mechanism to show progress (wheel and timing) triggers (#32-#30) 7/ it updates the statusbar [#30-#26) 8/ this leads to a repaint of something (#25) 9/ the backing store (the thing on which we actually paint) of some widget tries to synchronize itself (#16-#14) 10/ it leads to a full repaint of our workarea (why, I am not sure) (#4] 11/ this eventually crashes, presumably because the backing store is not ready yet to receive things to paint. (#11-#10) After wrtigin all this, that does not really help yet (except that we could probably avoid 2/ and maybe forbid updates around 7/). But now I notice that the warnings show first: QBackingStore::endPaint() called with active painter on backingstore paint device are bugs in particular Qt versions. See e.g. https://bugreports.qt.io/browse/QTBUG-66452 althoug this doe snot involve a crash. So, first question: what is your Qt version? JMarc
Re: serious bug (fedora issue?)
Hello, Was the information that I provided useful? I also have to face other crash issues. I will try to communicate after the previous one have been solved. Thank. === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | ===
Re: serious bug (fedora issue?)
Le 30/12/2018 à 22:05, Dr Eberhard Lisse a écrit : Should I raise a bug on the tracker for this? Yes please. I guess we should skip everything ERT. JMarc
Re: serious bug (fedora issue?)
I tried "buffer-anonymize"
and found that
\begin{enumerate}[resume, label={\arabic*}.]
becomes
\begin{enumerate}[resume, a={\aa*}.]
Should I raise a bug on the tracker for this?
el
On 2018-12-29 18:19 , Jean-Marc Lasgouttes wrote:
[...]
> Is it enough to obfuscate it with "buffer-anonymize"?
[...]
Re: serious bug (fedora issue?)
0x55da71c8 in lyx::graphics::CacheItem::tryDisplayFormat() const () #44 0x55db34ed in lyx::graphics::Loader::Impl::startLoading() () #45 0x55b909d8 in lyx::RenderGraphic::metrics(lyx::MetricsInfo&, lyx::Dimension&) const () #46 0x5593e95e in lyx::TextMetrics::redoParagraph(long) () #47 0x5593ff50 in lyx::TextMetrics::metrics(lyx::MetricsInfo&, lyx::Dimension&, int) () #48 0x55b6fe0f in lyx::InsetText::metrics(lyx::MetricsInfo&, lyx::Dimension&) const () #49 0x55ab3347 in lyx::InsetCollapsible::metrics(lyx::MetricsInfo&, lyx::Dimension&) const () #50 0x5593e95e in lyx::TextMetrics::redoParagraph(long) () #51 0x5597fd7a in lyx::BufferView::scrollToCursor(lyx::DocIterator const&, bool) () #52 0x55984c65 in lyx::BufferView::processUpdateFlags(lyx::Update::flags) () #53 0x55d5a1df in lyx::frontend::SpellcheckerWidget::Private::setSelection(lyx::DocIterator const&, lyx::DocIterator const&) const () #54 0x55d5beb8 in lyx::frontend::SpellcheckerWidget::Private::check() [clone .localalias.129] () #55 0x55d5c734 in lyx::frontend::SpellcheckerWidget::on_ignoreAllPB_clicked() () #56 0x55d5d1c1 in lyx::frontend::SpellcheckerWidget::qt_metacall(QMetaObject::Call, int, void**) () #57 0x75ff6ec7 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #58 0x769af8e6 in QAbstractButton::clicked(bool) () at /lib64/libQt5Widgets.so.5 #59 0x769afb0e in QAbstractButtonPrivate::emitClicked() () at /lib64/libQt5Widgets.so.5 #60 0x769b0f63 in QAbstractButtonPrivate::click() () at /lib64/libQt5Widgets.so.5 #61 0x769b1135 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #62 0x769065c8 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #63 0x768c7475 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #64 0x768cedd8 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #65 0x55ba4c8e in lyx::frontend::GuiApplication::notify(QObject*, QEvent*) () #66 0x75fcec36 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #67 0x768ce0cd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /lib64/libQt5Widgets.so.5 #68 0x76921368 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #69 0x76923f0e in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #70 0x768c7475 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #71 0x768ceb90 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #72 0x55ba4c8e in lyx::frontend::GuiApplication::notify(QObject*, QEvent*) () #73 0x75fcec36 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #74 0x76374f43 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #75 0x76377085 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib64/libQt5Gui.so.5 #76 0x7635246b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #77 0x7fffe1c6b7cf in QPAEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5XcbQpa.so.5 #78 0x75fcdb7b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #79 0x75fd5c46 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #80 0x55883a65 in lyx::LyX::exec(int&, char**) () #81 0x5572a68a in main () =========== Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | === > Sent: Saturday, December 29, 2018 at 7:14 PM > From: "José Abílio Matos" > To: lyx-devel@lists.lyx.org > Cc: "Jean-Marc Lasgouttes" , lyx-us...@lists.lyx.org > Subject: Re: serious bug (fedora issue?) > > On Saturday, 29 December 2018 16.19.06 WET Jean-Marc Lasgouttes wrote: > > Le 07/11/2018 à 14:35, Patrick Dupre a écrit : > > > Hello, > > > > > > There is a serious bug with the version 2.3.1 under fedora 28 > > > When I run the spellchecker, I got the following crash. > > > > Is it possible with fedora to get the debug information, so that you can > > give us a proper becktrace? José, are you reading us? > > Yes. Using gdb. :-) > > The instructions are mo
Re: serious bug (fedora issue?)
On Saturday, 29 December 2018 16.19.06 WET Jean-Marc Lasgouttes wrote: > Le 07/11/2018 à 14:35, Patrick Dupre a écrit : > > Hello, > > > > There is a serious bug with the version 2.3.1 under fedora 28 > > When I run the spellchecker, I got the following crash. > > Is it possible with fedora to get the debug information, so that you can > give us a proper becktrace? José, are you reading us? Yes. Using gdb. :-) The instructions are more or less the following from the command line: $ gdb /usr/bin/lyx ... (gdb) run That is, after you get the gdb prompt (gdb) enter run That will get lyx running. After lyx crashes you will get back to the gdb prompt additionally with further information, like: Missing separate debuginfos, use: dnf debuginfo-install OpenEXR- libs-2.2.0-15.fc29.x86_64 ... That part is specific to Fedora it tells how to install the debuginfo packages. As root run the command described above: # dnf debuginfo-install OpenEXR-libs-2.2.0-15.fc29.x86_64 ... Repeat again the same procedure, starting by entering run in the gdb prompt and when lyx crashes in the gdb backtrace enter bt (abbreviation for backtrace). That will give the full backtrace together with the debug information. > > Then I am stuck if I want to recover. It crashes immediately. > > If I start from the previous version, again the spellchecker will crash at > > the same place. > > Changing the name may help, bit again a crash appears later in the > > document. > > > > Unfortunately, I cannot make the document public. > > Is it enough to obfuscate it with "buffer-anonymize"? > > The spellchecker will not like it, though :) As far as I understand the problem is not if there are typos or not. :-) > JMarc -- José Abílio
Re: serious bug (fedora issue?)
Hello, What I did last time is the following. However, it seems that the length of the document matters as well as the number of pictures. F7 (at the beginning of the document). At one point it failed. lyx the document in recover more. F7 again. It may fail a bit further. Then I do the same again. But it may immediately fail. Then, I rerun lyx, but not in recover mode. it failed again. Then do it again. and usually it does not fail immediately, and I can run f7 again it I am lucky. I can save the document at each correction until it fails again. When it fails again. I redo the same thing. If I do not run F7 at the begin of the document but close to the previous failure, I may have a chance to reach the end of the document. It is random and painful process. I can try to debug if you tell me exactly what to do. My Best. === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | === > Sent: Saturday, December 29, 2018 at 5:19 PM > From: "Jean-Marc Lasgouttes" > To: lyx-us...@lists.lyx.org, "LyX Mechanics" > Subject: Re: serious bug (fedora issue?) > > Le 07/11/2018 à 14:35, Patrick Dupre a écrit : > > Hello, > > > > There is a serious bug with the version 2.3.1 under fedora 28 > > When I run the spellchecker, I got the following crash. > > Is it possible with fedora to get the debug information, so that you can > give us a proper becktrace? José, are you reading us? > > > Then I am stuck if I want to recover. It crashes immediately. > > If I start from the previous version, again the spellchecker will crash at > > the same > > place. > > Changing the name may help, bit again a crash appears later in the document. > > > > Unfortunately, I cannot make the document public. > > Is it enough to obfuscate it with "buffer-anonymize"? > > The spellchecker will not like it, though :) > > > > JMarc >
Re: serious bug (fedora issue?)
Le 07/11/2018 à 14:35, Patrick Dupre a écrit : Hello, There is a serious bug with the version 2.3.1 under fedora 28 When I run the spellchecker, I got the following crash. Is it possible with fedora to get the debug information, so that you can give us a proper becktrace? José, are you reading us? Then I am stuck if I want to recover. It crashes immediately. If I start from the previous version, again the spellchecker will crash at the same place. Changing the name may help, bit again a crash appears later in the document. Unfortunately, I cannot make the document public. Is it enough to obfuscate it with "buffer-anonymize"? The spellchecker will not like it, though :) JMarc
Re: serious bug
When editing, and doing a carriage return, then backspace on the old paragraph, carriage return, results in lyx 1.5.0rc1 crashing - 1.5 is i'm not able to reproduce it. can you provide exact steps how to achive this crash ? pavel
Re: serious bug
I just reproduced it on this file. Move cursor to the end of paragraph, then to start of work tasks do CR Move cursor to start of words seller biased, then CR Move cursor to the start of that for then CR at that point lyx crashes. - W. Bentley MacLeod confirmed. i filed the bug http://bugzilla.lyx.org/show_bug.cgi?id=3844 . thank you for reporting. pavel
Re: serious bug
Pavel Sanda wrote: I just reproduced it on this file. Move cursor to the end of paragraph, then to start of work tasks do CR Move cursor to start of words seller biased, then CR Move cursor to the start of that for then CR at that point lyx crashes. - W. Bentley MacLeod confirmed. i filed the bug http://bugzilla.lyx.org/show_bug.cgi?id=3844 . Strange, I cannot reproduce. A/
Re: serious bug
W. Bentley MacLeod wrote: When editing, and doing a carriage return, then backspace on the old paragraph, carriage return, results in lyx 1.5.0rc1 crashing - 1.5 is so much better than 1.4.4 in many respects I am trying to use it, but this bug keeps occurring. I am using the windows version on XP service pack 2. I can't reproduce the crash with current svn. I presume you know already that the math panel does not toggle in this version (it did in beta 3). This neither. Abdel.
Re: serious bug
Alfredo Braunstein wrote: Pavel Sanda wrote: I just reproduced it on this file. Move cursor to the end of paragraph, then to start of work tasks do CR Move cursor to start of words seller biased, then CR Move cursor to the start of that for then CR at that point lyx crashes. - W. Bentley MacLeod confirmed. i filed the bug http://bugzilla.lyx.org/show_bug.cgi?id=3844 . Strange, I cannot reproduce. linux, btw. A/
Re: serious bug
confirmed. i filed the bug http://bugzilla.lyx.org/show_bug.cgi?id=3844 . Strange, I cannot reproduce. svn up did the trick. current trunk is ok. pavel
Re: serious bug
> When editing, and doing a carriage return, then backspace on the old > paragraph, carriage return, results in lyx 1.5.0rc1 crashing - 1.5 is i'm not able to reproduce it. can you provide exact steps how to achive this crash ? pavel
Re: serious bug
> I just reproduced it on this file. > Move cursor to the end of paragraph, then to start of work "tasks" do CR > Move cursor to start of words "seller biased", then CR > Move cursor to the start of "that for" then CR at that point lyx crashes. > - > W. Bentley MacLeod confirmed. i filed the bug http://bugzilla.lyx.org/show_bug.cgi?id=3844 . thank you for reporting. pavel
Re: serious bug
Pavel Sanda wrote: >> I just reproduced it on this file. >> Move cursor to the end of paragraph, then to start of work "tasks" do CR >> Move cursor to start of words "seller biased", then CR >> Move cursor to the start of "that for" then CR at that point lyx crashes. >> - >> W. Bentley MacLeod > > confirmed. i filed the bug http://bugzilla.lyx.org/show_bug.cgi?id=3844 . Strange, I cannot reproduce. A/
Re: serious bug
W. Bentley MacLeod wrote: When editing, and doing a carriage return, then backspace on the old paragraph, carriage return, results in lyx 1.5.0rc1 crashing - 1.5 is so much better than 1.4.4 in many respects I am trying to use it, but this bug keeps occurring. I am using the windows version on XP service pack 2. I can't reproduce the crash with current svn. I presume you know already that the math panel does not toggle in this version (it did in beta 3). This neither. Abdel.
Re: serious bug
Alfredo Braunstein wrote: > Pavel Sanda wrote: > >>> I just reproduced it on this file. >>> Move cursor to the end of paragraph, then to start of work "tasks" do CR >>> Move cursor to start of words "seller biased", then CR >>> Move cursor to the start of "that for" then CR at that point lyx >>> crashes. >>> - >>> W. Bentley MacLeod >> >> confirmed. i filed the bug http://bugzilla.lyx.org/show_bug.cgi?id=3844 . > > Strange, I cannot reproduce. linux, btw. A/
Re: serious bug
> > confirmed. i filed the bug http://bugzilla.lyx.org/show_bug.cgi?id=3844 . > > Strange, I cannot reproduce. svn up did the trick. current trunk is ok. pavel
