[mir-only] unity8 crash in unity-mir's ApplicationManager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Application Launcher |
Expired
|
Undecided
|
Unassigned | ||
unity-mir (Ubuntu) |
Incomplete
|
Undecided
|
Gerry Boland | ||
unity8 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Core was generated by `unity8'.
Program terminated with signal 11, Segmentation fault.
#0 0x40a97464 in strlen () from /lib/arm-
(gdb) bt
#0 0x40a97464 in strlen () from /lib/arm-
#1 0x41188d12 in g_strjoinv () from /lib/arm-
#2 0x45d7b95e in upstart_
#3 0x45c6653e in TaskController:
#4 0x45c604c4 in Application:
#5 0x45c60656 in Application:
#6 0x45c5d45a in ApplicationMana
#7 0x45c68f70 in ApplicationMana
#8 0x45c69032 in ApplicationMana
#9 0x402299f0 in ?? () from /usr/lib/
#10 0x402299f0 in ?? () from /usr/lib/
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
affects: | unity8 (Ubuntu) → unity-mir (Ubuntu) |
Changed in unity-mir (Ubuntu): | |
status: | New → Incomplete |
Changed in unity8: | |
status: | New → Incomplete |
Changed in upstart-app-launch: | |
status: | New → Incomplete |
affects: | unity8 → unity8 (Ubuntu) |
Problem either in Unity-Mir passing a bad string to upstart-app-launch, or a bug in upstart-app-launch.