search

inyokaproject / inyokaedit

A markup editor for Inyoka articles.
GNU General Public License v3.0
7 stars 6 forks source link

inyokaedit crashed with SIGILL in QPainter::setClipRect() #79

Closed ElTh0r0 closed 7 years ago

ElTh0r0 commented 7 years ago

Writing a new wiki-article when inyokaedit crashed. No further informations or logs available. Lucky me I clicked the save-button regularly ;)

ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: inyokaedit 0.0.9~ppa1-0~37~precise1 ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1 Uname: Linux 3.2.0-11-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CheckboxSubmission: 041bc566a507242cee03dd4e215f9067 CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f CrashDB: inyokaedit Date: Sat Jan 28 16:49:16 2012 ExecutablePath: /usr/bin/inyokaedit InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1) ProcCmdline: inyokaedit Signal: 4 SourcePackage: inyokaedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QPainter::setClipRect(QRectF const&, Qt::ClipOperation) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QTextControl::drawContents(QPainter, QRectF const&, QWidget) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 ThirdParty: True Title: inyokaedit crashed with SIGILL in QPainter::setClipRect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Imported from Launchpad using lp2gh.

ElTh0r0 commented 7 years ago

(by ubuntuflo)

ElTh0r0 commented 7 years ago

(by elthoro) Thanks for your report. Hard to find the reason for crashing... Anything special you did shortly before the crash? Clicking a button or menu entry? Or does it came "from out of the blue"? Is it possible to reproduce this behaviour?

ElTh0r0 commented 7 years ago

(by ubuntuflo) I'm not sure. I can't remember what I've done at last. I'll have an eye on it…

ElTh0r0 commented 7 years ago

(by elthoro) Closed here, because v0.0.9 is obsolete and the bug wasn't reproducible. Thanks anyway for the bug report! Please open a new bug if such a problem arises.