unity-2d-launcher crashed with SIGSEGV in QPainter::fillRect()

Bug #805587 reported by Jean-Baptiste Lallement
84
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Qt
New
Undecided
auto-samuel.rodal
unity-2d
Fix Released
Critical
Alberto Mardegan
qt4-x11 (Ubuntu)
Fix Released
High
Alberto Mardegan
Oneiric
Fix Released
High
Alberto Mardegan

Bug Description

Oneiric Desktop 20110704

TEST CASE
1. Start Oneiric ISO in kvm
2. Once the system is up, move the mouse over the launcher then out.

Result:
This crash

Same crash with unity-2d-panel is the user clicks on the panel.
Related issue bug 759803

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-launcher 3.8.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic i686
Architecture: i386
Date: Mon Jul 4 16:49:03 2011
ExecutablePath: /usr/bin/unity-2d-launcher
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110704.1)
ProcCmdline: unity-2d-launcher
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x10ed806: movntdq %xmm0,(%edi)
 PC (0x010ed806) ok
 source "%xmm0" ok
 destination "(%edi)" (0xb4cd2000) in non-writable VMA region: 0xb4cd2000-0xb4d27000 r--p /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-M.ttf
SegvReason: writing VMA /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-M.ttf
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 ?? () from /usr/lib/libQtGui.so.4
 ?? () from /usr/lib/libQtGui.so.4
 ?? () from /usr/lib/libQtGui.so.4
 ?? () from /usr/lib/libQtGui.so.4
 QPainter::fillRect(QRect const&, QBrush const&) () from /usr/lib/libQtGui.so.4
Title: unity-2d-launcher crashed with SIGSEGV in QPainter::fillRect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x010ed806 in ?? ()
 No symbol table info available.
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-2d (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

unity-2d-launcher: installed version 3.8.8-0ubuntu1, latest version: 3.8.10-0ubuntu1
multiarch-support: installed version 2.13-6ubuntu2, latest version: 2.13-8ubuntu3
libc-bin: installed version 2.13-6ubuntu2, latest version: 2.13-8ubuntu3
libc6-dbg: installed version 2.13-6ubuntu2, latest version: 2.13-8ubuntu3
libc6: installed version 2.13-6ubuntu2, latest version: 2.13-8ubuntu3
libunity-2d-private0: installed version 3.8.8-0ubuntu1, latest version: 3.8.10-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Here is the trace.

visibility: private → public
Changed in unity-2d (Ubuntu Oneiric):
importance: Undecided → High
status: Invalid → Confirmed
assignee: nobody → Canonical Desktop Experience Team (canonical-dx-team)
Changed in unity-2d:
milestone: none → 3.8.12
importance: Undecided → Critical
Revision history for this message
David Barth (dbarth) wrote :
Changed in unity-2d:
assignee: nobody → Florian Boucault (fboucault)
Changed in unity-2d:
status: New → Confirmed
Changed in unity-2d:
milestone: 3.8.12 → 3.8.14
Changed in unity-2d:
milestone: 3.8.14 → 3.8.16
Revision history for this message
Horst Schirmeier (horst) wrote :

Still present in Alpha 3.

Changed in unity-2d:
milestone: 4.0 → 4.2
Revision history for this message
Florian Boucault (fboucault) wrote :

I believe it's been fixed by yesterday's release. Horst, Jibel, can you check again please? Thanks a lot!

Changed in unity-2d:
assignee: Florian Boucault (fboucault) → Alberto Mardegan (mardy)
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

This specific crash with the launcher is fixed. I'm closing this report.

Changed in unity-2d (Ubuntu Oneiric):
status: Confirmed → Fix Released
Changed in unity-2d:
status: Confirmed → Fix Released
Revision history for this message
Benjamin Drung (bdrung) wrote :

I ran into this bug with unity-2d-launcher 4.2.0-0ubuntu1 (see bug #835474 for the crash data).

Changed in unity-2d (Ubuntu Oneiric):
status: Fix Released → Confirmed
Changed in unity-2d:
status: Fix Released → Confirmed
Changed in unity-2d:
milestone: 4.2 → 4.4
Changed in unity-2d:
milestone: 4.4 → 4.6
Revision history for this message
Alberto Mardegan (mardy) wrote :

Thanks for reporting this bug. In order to be able to investigate it, I'd like to ask to whoever can reproduce it, to provide the following information:

- Is the crash easily reproducible in your machine? Does it happen all the time?
- Please attach the output of the xdpyinfo program

Changed in unity-2d (Ubuntu Oneiric):
status: Confirmed → Incomplete
Changed in unity-2d:
status: Confirmed → Incomplete
Revision history for this message
nutznboltz (nutznboltz-deactivatedaccount) wrote :

@Alberto I have a bug report like this one but with xdpyinfo output attached.
LP: #843432

Revision history for this message
nutznboltz (nutznboltz-deactivatedaccount) wrote :

Also
LP: #843448

Revision history for this message
Alberto Mardegan (mardy) wrote :

@nutznboltz: thanks! It seems the bug happens when the screen is set to 24 bits of depth. Can you please confirm, by testing if the bug disappears when using a different bit depth (or setting up KVM to emulate a different graphics card, such as "vga")?

tags: added: 24bit
Revision history for this message
Alex (psyalex) wrote :

The bug does not happen on my machine when I start KVM with option "-std vga" or "-std vmware".

Changed in unity-2d:
milestone: 4.6 → 4.8
Changed in unity-2d:
milestone: 4.8 → 4.10
tags: added: rls-mgr-o-tracking
tags: added: testcase
Changed in unity-2d:
milestone: 4.10 → 4.12
David Barth (dbarth)
Changed in unity-2d (Ubuntu Oneiric):
assignee: Canonical Desktop Experience Team (canonical-dx-team) → Alberto Mardegan (mardy)
Alberto Mardegan (mardy)
Changed in unity-2d:
status: Incomplete → In Progress
affects: unity-2d (Ubuntu Oneiric) → qt4-x11 (Ubuntu Oneiric)
Changed in qt4-x11 (Ubuntu):
status: Incomplete → Triaged
Alberto Mardegan (mardy)
Changed in unity-2d:
milestone: 4.12 → 4.14
milestone: 4.14 → 4.12
Changed in unity-2d:
status: In Progress → Fix Committed
Changed in unity-2d:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qt4-x11 - 4:4.7.4-0ubuntu7

---------------
qt4-x11 (4:4.7.4-0ubuntu7) oneiric; urgency=low

  * debian/patches/kubuntu_96_fix_qml_crash.diff:
    - unity-2d-panel crashed with SIGSEGV in QPainter::drawTiledPixmap()
      (LP: #804784)
    - unity-2d-launcher crashed with SIGSEGV in QPainter::fillRect()
      (LP: #805587)
 -- Didier Roche <email address hidden> Thu, 29 Sep 2011 13:31:46 +0200

Changed in qt4-x11 (Ubuntu Oneiric):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

  • auto-samuel.rodal Edit

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