/usr/bin/unity8-dash:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Canonical System Image |
Critical
|
kevin gunn | ||
| | qtubuntu (Ubuntu) |
Critical
|
Nick Dedekind | ||
Bug Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+15.
Related branches
- Daniel d'Andrada (community): Approve on 2015-11-11
- PS Jenkins bot: Approve (continuous-integration) on 2015-11-09
- Albert Astals Cid (community): Needs Information on 2015-09-29
-
Diff: 34 lines (+10/-6)1 file modifiedsrc/ubuntumirclient/clipboard.cpp (+10/-6)
| Albert Astals Cid (aacid) wrote : | #1 |
| Jean-Baptiste Lallement (jibel) wrote : | #2 |
Trace in top 10 crashes on stable phones. Adding a C.S.I. task.
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → kevin gunn (kgunn72) |
| importance: | Undecided → Critical |
| milestone: | none → ww40-2015 |
| status: | New → Confirmed |
| Nick Dedekind (nick-dedekind) wrote : | #3 |
Don't think we can trust this stacktrace. Seems impossible to get there.
| Nick Dedekind (nick-dedekind) wrote : | #4 |
Have we got an crash dump files?
| Brian Murray (brian-murray) wrote : | #5 |
The Error Tracker does not keep core files after a retrace has successfully completed and it does not ask for core files for a crash which has a good stacktrace address signature and for which we already have a complete stacktrace. So we don't have a crash dump file on hand, nor would it be particularly easy to get one.
| Changed in unity8 (Ubuntu): | |
| status: | New → In Progress |
| Changed in qtubuntu (Ubuntu): | |
| status: | New → In Progress |
| Changed in canonical-devices-system-image: | |
| status: | Confirmed → In Progress |
| Changed in qtubuntu (Ubuntu): | |
| assignee: | nobody → Nick Dedekind (nick-dedekind) |
| Changed in unity8 (Ubuntu): | |
| assignee: | nobody → Nick Dedekind (nick-dedekind) |
| Changed in qtubuntu (Ubuntu): | |
| importance: | Undecided → Critical |
| Changed in unity8 (Ubuntu): | |
| importance: | Undecided → Critical |
| status: | In Progress → Opinion |
| no longer affects: | unity8 (Ubuntu) |
| Changed in canonical-devices-system-image: | |
| milestone: | ww40-2015 → ww46-2015 |
| Changed in canonical-devices-system-image: | |
| milestone: | ww46-2015 → ww02-2016 |
| Launchpad Janitor (janitor) wrote : | #6 |
This bug was fixed in the package qtubuntu - 0.62+16.
---------------
qtubuntu (0.62+16.
[ Albert Astals Cid ]
* Improvements from running clazy over the code
[ Alberto Aguirre ]
* Add support for Qt popups and dialog windows.
[ Gerry Boland ]
* Fix inconsistent mouse wheel scrolling behavior
[ Lukáš Tinkl ]
* Fix inconsistent mouse wheel scrolling behavior
[ Nick Dedekind ]
* Added check for valid mime data. (LP: #1493530)
-- Gerry Boland <email address hidden> Tue, 17 Nov 2015 14:49:33 +0000
| Changed in qtubuntu (Ubuntu): | |
| status: | In Progress → Fix Released |
| Changed in canonical-devices-system-image: | |
| status: | In Progress → Fix Committed |
| Changed in canonical-devices-system-image: | |
| status: | Fix Committed → Fix Released |


Why is this 0x2 in
#8 operator<< (t=0xb3d01078 "Attempted to deliver an event to a non-existent window, ignoring.", this=0x2) at /usr/include/ arm-linux- gnueabihf/ qt5/QtCore/ qdebug. h:114
Or shall we not trust it?