qt4 apps segmentation fault after update

Bug #228243 reported by Ivan Candelas
This bug report is a duplicate of:  Bug #242648: backport lyx 1.5.5-1 to hardy. Edit Remove
4
Affects Status Importance Assigned to Milestone
qt4-x11 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After latest update of QT4 (05/07/2008), all apps using this lib are causing a segmentation fault.

Revision history for this message
Axel Pospischil (apos) wrote :

Can confirm this for usage with lyx-1.5.3. Program exits with

 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

Program starts, but
 1. Windows inside appear not in the right size (too small)
 2. Open a document causes lyx to segfault

This is a real big problem considering someone is in the middle of an important work. Imagin OpenOffice would stop working from one to the other second.

Revision history for this message
Axel Pospischil (apos) wrote :

Forgot to mention:
  QT Version 4.4.0-1ubuntu1~hardy1

Changed in qt4-x11:
status: New → Confirmed
Revision history for this message
manuel fernandez (mfg) wrote :

Same problem here but even worse because lyx crashes.

Importance for me is crucial or essential!

Revision history for this message
Axel Pospischil (apos) wrote :

This is due to enabled backports updates (unsupported).
See Bug #228067 in qt4-x11 (Ubuntu)

Revision history for this message
Sergey Tachenov (laerel) wrote :

I had reverse situation today. I have installed latest Hardy mainstream libqt4-gui, and every GUI application using it, including qtconfig, was crashing.
After a bit of looking at weird core dumps I suddenly decided to upgrade to version from hardy-backports. Crashes stopped. Everything is working fine now.

Strangely enough, exactly the same software on another machine is running fine. The only difference is that "fine" machine had Gutsy upgraded to Hardy, while the one crashes were happening on had fresh install of Hardy. Versions of all packages were the same on both machines.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.