I have ben having problems with Pidgin not starting. It will show in the task bar and try to load for about a minute then disappear. I tried running in terminal and got this error:
(pidgin:9191): GStreamer-CRITICAL **: gst_caps_unref: assertion `GST_CAPS_REFCOUNT_VALUE (caps) > 0’ failed
Pidgin 2.5.1 has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.
It was working earlier today, and I have had no problems before. restarting/logging out and in makes no difference.
> I have ben having problems with Pidgin not starting. It will show in
> the task bar and try to load for about a minute then disappear. I tried
> running in terminal and got this error:
>
> (pidgin:9191): GStreamer-CRITICAL **: gst_caps_ref: assertion
> `GST_CAPS_REFCOUNT_VALUE (caps) > 0’ failed
(pidgin:9191): GStreamer-CRITICAL **: gst_caps_unref: assertion
`GST_CAPS_REFCOUNT_VALUE (caps) > 0’ failed
> Pidgin 2.5.1 has segfaulted and attempted to dump a core file.
>
> This is a bug in the software and has happened through
>
> no fault of your own.
>
> It was working earlier today, and I have had no problems before.
> restarting/logging out and in makes no difference.
Did you update any package recently from packman repo?
> Looks like I have several. Perhaps uninstalling Pidgin and
> reinstalling will help.
I already saw in your last message that does not helped
But I think this is more related to “gstreamer” than “pidging” itself.
Sometimes, mixing libraries from opensuse repository and packman can be a
bit messy.
> Do you suggest that I delete the packman version?
No, I would open a bugzilla first to be sure where the problem is coming. I
think it can be something with gstreamer but I’m not 100% sure. Only
developers can tell
> What can I do to prevent these kind of conflicts in the future?
It’s difficult to say.
There some multimedia libraries that we (opensuse users) have to download
from packman or videolan repo due to license restrictions but they can
conflict with opensuse stock packages. It’s a kind of “lotto”, we have to
test-and-try and if something goes wrong, just report to get it fixed.
I just got a security update of gstreamer and now pidgin is doing the same thing. i was going to post a bugzilla but I don’t exactly understand what I need installed and what I need to do to get a backtrace. I tried searching for the core file that the pidgin backtrace instructions talk about but could not find it. It may be that my system is not set up to generate a core file but I don’t know how to set it to.
> I just got a security update of gstreamer and now pidgin is doing the
> same thing. i was going to post a bugzilla but I don’t exactly
> understand what I need installed and what I need to do to get a
> backtrace. I tried searching for the core file that the pidgin
> backtrace instructions talk about but could not find it. It may be that
> my system is not set up to generate a core file but I don’t know how to
> set it to.
I think you need the “pidgin-debuginfo” package for you version of pidgin.
I had the same issue after the gstreamer update. I solved it by installing gstreamer 0.10.23 from the Packman repo. Apparently 0.10.21 which came in as an update doesn’t play nice with libpurple.
