Miro segfaults every couple minutes: g_object_ref: assertion `object->ref_count > 0' failed

*bump*

I've noticed this for a long, long time, and it's made Miro unusable. At first I couldn't pinpoint the cause -- crashes seemed to happen no matter what you were doing with Miro at the time -- but after removing all my podcast subscriptions, it didn't crash for at least half an hour. I added a couple audio podcasts from the Miro Guide, changed the podcast "Check for new content" setting to "Manually," and it remained stable for a while, even as I played a video I had manually downloaded with a .torrent file. Then it crashed again, with the same terminal output.

I plan to leave Miro running with *no* subscriptions for a while to see if that prevents it from crashing.

I've also filed an upstream bug: http://bugzilla.pculture.org/show_bug.cgi?id=18908

Status changed to 'Confirmed' because the bug affects multiple users.

Nope, scratch that -- I had Miro playing an audio file with no podcast subscriptions, and it crashed with the same output.

The easiest workaround for this seems to be running Miro in Windows...

this is fixed in Miro 5. Out soon.

Janet

On Sun, Apr 29, 2012 at 5:49 PM, Alexander <email address hidden>wrote:

> The easiest workaround for this seems to be running Miro in Windows...
>
> --
> You received this bug notification because you are subscribed to Miro.
> https://bugs.launchpad.net/bugs/954496
>
> Title:
> Miro segfaults every couple minutes: g_object_ref: assertion
> `object->ref_count > 0' failed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/democracy/+bug/954496/+subscriptions
>

But the big question is, will it actually be delivered as update or do we have to wait 6 months and abandon LTS release to get this one piece of software working...

@alexander-
There are PPAs:
https://launchpad.net/~pcf/+archive/miro-releases
https://launchpad.net/~pcf/+archive/miro-testing

Having PPA's is not an excuse not to fix bugs.

not sure what you mean here? this bug is fixed in Miro 5.

Janet

On Tue, May 8, 2012 at 9:56 AM, Alexander <email address hidden> wrote:

> Having PPA's is not an excuse not to fix bugs.
>
> --
> You received this bug notification because you are subscribed to Miro.
> https://bugs.launchpad.net/bugs/954496
>
> Title:
> Miro segfaults every couple minutes: g_object_ref: assertion
> `object->ref_count > 0' failed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/democracy/+bug/954496/+subscriptions
>

I'm meaning actually delivering the update for Precise users.

would you like it on magnetic tape and mailed to your home address?

On Tue, May 8, 2012 at 11:02 AM, Alexander <email address hidden>wrote:

> I'm meaning actually delivering the update for Precise users.
>
> --
> You received this bug notification because you are subscribed to Miro.
> https://bugs.launchpad.net/bugs/954496
>
> Title:
> Miro segfaults every couple minutes: g_object_ref: assertion
> `object->ref_count > 0' failed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/democracy/+bug/954496/+subscriptions
>

Just uploading it to Precise updates would be enough ;)

(but I'm done with complaining, I'm just extremely disappointed at bad quality and gigantic amount of blocker bugs in Precise which are not getting fixed even they were reported months before the release. Likely I'll just go back to Windows 7, there developers at least care enough to fix bugs)

If someone gets me a patch for the issue, I'll push it to precise if it's not too invasive. https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
We'll also need a test case for this.

Applying a "patch" when it's something that was fixed in a version is stupid unless there's a lot of dependencies. There's a valid complaint there, all things considered. It's one of the big gripes I've got with Ubuntu- might as well not even HAVE LTS versions with the attitude espoused in this bug thread. My fix? Get the PPA and REMEMBER the wrong-headed attitudes (This isn't support and it's not what you need to be doing in a distribution... Before you comment, I've done embedded distributions for years now...some publicly available, some not so much so.)

When Miro 5 makes it into later versions of Ubuntu, we can backport it to precise as a backport. You can use the requestbackport tool in ubuntu-dev-tools to request that backport when appropriate. That tool will let you know the level of testing required for the backport (install/run for itself and its reverse dependencies). We generally don't push major new versions into a stable release except for the backports pocket as it's difficult to be sure that the new version won't introduce more bugs than the old one had. Backports is opt-in, so if a user would like a newer version of an application, they can try it. The purpose of backports though is for new features, not to fix bugs. A targeted fix as a Stable Release Update is much more likely to fix the issue at hand without causing other issues (that's why there's a verification period in the proposed repository).
Miro is not directly supported by anyone in Ubuntu; that is, there is no one specifically claiming to support it. Anyone may propose bug fixes assuming they meet the Stable Release Update criteria. LTS in this context refers how long the core infrastructure for the release will be supported (mainly for security updates).