This bug was fixed in the package pidgin - 1:2.10.11-0ubuntu4.1
---
pidgin (1:2.10.11-0ubuntu4.1) wily; urgency=medium
* debian/patches/hg_gst_leak.patch:
"When receiving an error or stream finished message, we can free the
Gstreamer pipeline so we don't leak it for each
** Changed in: pidgin (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479715
Title:
Crash due to fd leak when playing sounds in pidgin
To manage
Okay got my dev pc back and tested this.
The test case in the description is passing with the wily-proposed
package, 2.10.11-0ubuntu4.1
Had to adjust the fd limit i originally suggested for the test to be
more reliable - 20 was a bit too low and was sometimes failing during
startup even, so I
Hello errors.ubuntu.com, or anyone else affected,
Accepted pidgin into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pidgin/1:2.10.11-0ubuntu4.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
Thanks for the report and sorry for the delay, I'm updating xenial and
uploaded a SRU for wily
** Also affects: pidgin (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: pidgin (Ubuntu Wily)
Importance: Undecided => High
** Changed in: pidgin (Ubuntu Wily)
I haven't had access to my dev computer for a few weeks so I couldn't
test that wily-proposed package yet. I would appreciate if someone else
did - the test case in the description is fairly easy to set up, IMO.
However, note that bug #1529445 is not the same thing as this bug - the
wily-proposed
> I have no idea what it takes to get through that into a regular
update.
it needs somebody to install the update and verify it works as it
should/fixes the problem it's supposed to/doesn't create regression and
then comment back on launchpad saying that...
--
You received this bug notification
A fix for this has been sitting in wily-proposed for about 3 weeks now.
I have no idea what it takes to get through that into a regular update.
It's been handled as Bug #1529445 so look there for more details. Maybe
someone knows how to move it forward through the process?
--
You received this
Disabling all sounds but "Message received" and "Attention received" is the
best workaround for now - the amount of sounds are reduced to a fraction
compared to enabling online notifications and messages sent sounds.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It could, but it would be unpleasant, as people like, when thet get an
audible "ping" when they've got a message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479715
Title:
Crash due to fd leak
Would disabling sound in Pidgin be a usefull workarround?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479715
Title:
Crash due to fd leak when playing sounds in pidgin
To manage notifications
I see it nominated for wily, but it occurs in wily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479715
Title:
Crash due to fd leak when playing sounds in pidgin
To manage notifications about
That's how bugs work here. They start as something for development
versions only and then they are nominated to be fixed in stable
releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479715
I ran into the same issue.
To improve searchability for this, the messages you see on the console
from this are:
ERROR: cannot create wakeup pipe
(Pidgin:8924): GStreamer-CRITICAL **: gst_poll_get_read_gpollfd:
assertion 'set != NULL' failed
(Pidgin:8924): GStreamer-CRITICAL **:
Created bug 1529445, which is about a different fd leak in gstreamer
1.6.0 itself that can result in the exact same crash in pidgin as this
bug.
It's not as straightforward as this bug in that it doesn't leak
constantly for all users, but requires, for example, not having a sound
card or some
** Changed in: pidgin (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479715
Title:
Crash due to fd leak when playing sounds in pidgin
To manage
The attachment "remove-gstreamer-pipeline-after-playing-a-sound-
902b1fd.diff" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pidgin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479715
Title:
18 matches
Mail list logo
