Two underscores in .desktop file name causes assumption that this is an appId and app is rejected.
Bug #1329141 reported by
Leo Arias
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Application Launcher |
Fix Released
|
Critical
|
Unassigned | ||
Ubuntu UI Toolkit |
Fix Released
|
Critical
|
Cris Dywan | ||
unity-mir |
Won't Fix
|
Undecided
|
Unassigned | ||
qtmir (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
qtubuntu (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
On the daily image testing for mako, image#78, one of the lifecycle management tests in unity failed because of a qmlscene crash (see attachment).
21:15:34.162 INFO _launcher:116 - Attempting to launch application 'tmp991xm1vf' with URIs '' via upstart-app-launch
21:15:36.367 INFO _launcher:116 - Attempting to launch application 'tmpbeb_op_3' with URIs '' via upstart-app-launch
21:16:08.689 ERROR _launcher:202 - Timed out waiting for Application with app_id 'tmpbeb_op_3' to stop.
http://
Related branches
lp://staging/~ubuntu-sdk-team/ubuntu-ui-toolkit/noScores
- PS Jenkins bot: Needs Fixing (continuous-integration)
- Leo Arias (community): Approve
- Zoltan Balogh: Approve
-
Diff: 49 lines (+16/-4)2 files modifiedtests/autopilot/ubuntuuitoolkit/fixture_setup.py (+12/-4)
tests/autopilot/ubuntuuitoolkit/tests/__init__.py (+4/-0)
no longer affects: | unity8 |
Changed in ubuntu-ui-toolkit: | |
importance: | Undecided → Critical |
tags: | added: lt-category-noimpact lt-date-20140717 lt-prio-high |
tags: | added: lt-blocker |
Changed in ubuntu-ui-toolkit: | |
assignee: | nobody → Christian Dywan (kalikiana) |
no longer affects: | unity8 |
Changed in ubuntu-ui-toolkit: | |
status: | New → Fix Released |
Changed in ubuntu-ui-toolkit: | |
status: | Fix Released → Fix Committed |
Changed in ubuntu-ui-toolkit: | |
status: | Fix Committed → Fix Released |
Changed in unity8 (Ubuntu): | |
status: | New → Invalid |
Changed in unity-mir: | |
status: | New → Won't Fix |
affects: | qtmir → qtmir (Ubuntu) |
Changed in qtmir (Ubuntu): | |
status: | New → Confirmed |
Changed in qtmir (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
Doesn't look like something UAL would be effecting. Seems to be a crash in the QML Scene binary itself.