unity8 crashed with SIGABRT on Qt 5.3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity8 (Ubuntu) |
Fix Released
|
High
|
Albert Astals Cid |
Bug Description
This was tried to be retraced with lp:daisy added with the landing-005 PPA sources but it wasn't very successful.
The easiest way to get Unity8 to crash with Qt 5.3 seems to be rapidly swiping up and down in the apps scope.
--
Refer to constantly updated info on the front page of https:/
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity8 7.88+14.
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.3-0ubuntu1
Architecture: armhf
CurrentDesktop: Unity
Date: Tue Jun 10 06:26:08 2014
Disassembly: => 0xb63198e6: Cannot access memory at address 0xb63198e6
ExecutablePath: /usr/bin/unity8
ExecutableTimes
InstallationDate: Installed on 2014-06-09 (1 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140609)
ProcCmdline: unity8
ProcCwd: /home/phablet
Signal: 6
SourcePackage: unity8
Stacktrace:
#0 0xb63198e6 in ?? ()
No symbol table info available.
#1 0xb63280fe in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
StacktraceSource:
#0 0xb63198e6 in ?? ()
#1 0xb63280fe in ?? ()
StacktraceTop:
?? ()
?? ()
Title: unity8 crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video
Related branches
Changed in unity8 (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Michał Sawicz (saviq) |
Changed in unity8 (Ubuntu): | |
status: | New → In Progress |
Changed in unity8 (Ubuntu): | |
status: | Fix Committed → Fix Released |
Hmm weird, no crash reason in the log :/