Python update = LyX crashing

hazza96 · Post by **hazza96** » Thu Jun 05, 2008 3:48 am

I use the latest version of Ubuntu 8.04, recently there was a python update, now LyX will not open a document that I have been working on.... or any document for that matter, it just crashes.

Anyone having a similar problem? Anyone know a workaround?

NEW: TikZ book now 40% off at Amazon.com for a short time.

And: Currently, Packt sells ebooks for $4.99 each if you buy 5 of their over 1000 ebooks. If you choose only a single one, $9.99. How about combining 3 LaTeX books with Python, gnuplot, mathplotlib, Matlab, ChatGPT or other AI books? Epub and PDF. Bundle (3 books, add more for higher discount): https://packt.link/MDH5p

Post by **Stefan Kottwitz** » Thu Jun 05, 2008 2:51 pm

Hi hazza96,

do you get an error message?

Stefan

hazza96 · Post by **hazza96** » Fri Jun 06, 2008 3:08 am

If I start it using the icon, it starts ok but as soon as I try and open any file it just disappears, no error messages nothing.

When I start it up using a terminal it does give some error message but I can't remember what, it says something about 'you found a bug' and how to report it but that causes LyX to crash as well.

I will get a more detailed error report and post that.

hazza96 · Post by **hazza96** » Fri Jun 06, 2008 4:32 am

Here is the error report:

Code: Select all

1
2
3
4
5
6
7
8
9
10
11
12
QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active
QWidgetPrivate::endSharedPainter: Attempting to end a null painter
QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions in Help->Introduction and send us a bug report, if necessary. Thanks !
Bye.
Aborted
 
 
הההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההה
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

hazza96 · Post by **hazza96** » Fri Jun 06, 2008 4:45 am

After doing a bit of searching on that error message it appears that an update to QT is the cause of the problem. The latest version of LyX doesn't have the issue so I am going to try and find it to install on my laptop.

washingweiss · Post by **washingweiss** » Wed Jun 11, 2008 6:23 pm

The problem should be due to a system-update with backports activated in the sources.list.

There's a solution: https://bugs.launchpad.net/ubuntu/+sour ... bug/228067.
To put it in a nutshell:

1. Disable the backports updates (unsupported) in the update manager
2. apt-get remove libqt4-dbus libqt4-test libqtcore4 libqt4-xml libqtgui4 libqt4-network libqt4-script libqt4-opengl libqt4-svg libqt4-assistant
3 apt-get clean
(! removes all previously downloaded deb files from /var/cache/apt/archives)
4. apt-get install --reinstall libqt4-gui libqt4-core
5. Check, if everything went fine:
apt-get -f install or
dpkg --configure -a

LaTeX.org

LyX ⇒ Python update = LyX crashing