This bug was fixed in the package qtubuntu-media -
0.7.1+15.04.20141105.2~rtm-0ubuntu1
---------------
qtubuntu-media (0.7.1+15.04.20141105.2~rtm-0ubuntu1) 14.09; urgency=low
[ thomas-voss ]
* Get rid of custom ref-counting and reuse pre-created object. (LP:
#1387959)
-- Ubuntu daily release <ps-jenk...@lists.canonical.com> Wed, 05 Nov 2014
12:10:39 +0000
** Changed in: qtubuntu-media (Ubuntu RTM)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtubuntu-media in Ubuntu.
https://bugs.launchpad.net/bugs/1387959
Title:
[TOPBLOCKER] unity8 crash in image krillin rtm 139
Status in “media-hub” package in Ubuntu:
In Progress
Status in “qtubuntu-media” package in Ubuntu:
Fix Released
Status in “unity8” package in Ubuntu:
Invalid
Status in “media-hub” package in Ubuntu RTM:
In Progress
Status in “qtubuntu-media” package in Ubuntu RTM:
Fix Released
Bug description:
Earlier today, a few QA folks tested image krillin rtm 138 plus silo
13, and found that it fixed the unity8 crash from bug 1382595.
Silo 13 plus silo 10 landed in image 139.
Now, in image 139, unity8 is crashy again. Olli mentioned getting two
crashes within a few minutes, and I got a unity8 crash while trying to
accept an incoming call. I'm not sure if it's the same crash as
before, or if it's a new one.
Attached is the crash dump I got just after hitting 'accept' for an
incoming call. I tried to pre-process it in apport-cli, but it failed
with "Sorry, the program "unity8" closed unexpectedly // Your
computer does not have enough free memory to automatically analyze the
problem and send a report to the developers."
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1387959/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help : https://help.launchpad.net/ListHelp
