Possible problem with unity8 AP:s with Qt 5.4.1

Bug #1431225 reported by Timo Jyrinki on 2015-03-12
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity8 (Ubuntu)
High
Unassigned

Bug Description

I'm getting at least the following crash: http://people.canonical.com/~tjyrinki/qt5/_usr_bin_unity8.32011.crash

There's also a symptom that indicators + clock is drawn on the screen, but the background is black and it's hanged in there. No CPU usage either.

It's possible this is a regression caused by either debian/patches/Lock-dispatchLock-before-the-regular-lock.patch (qtbase) or debian/patches/Fix-crash-in-overdraw-and-change-visualizers.patch (qtdeclarative).

Michał Sawicz (saviq) on 2015-03-12
Changed in unity8 (Ubuntu):
status: New → In Progress
assignee: nobody → Michał Sawicz (saviq)
importance: Undecided → High
Michał Sawicz (saviq) wrote :

This was a problem with a backported patch after all.

Changed in unity8 (Ubuntu):
status: In Progress → Invalid
assignee: Michał Sawicz (saviq) → nobody
Timo Jyrinki (timo-jyrinki) wrote :

Indeed, Lock-dispatchLock-before-the-regular-lock.patch now removed.

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

Other bug subscribers