Timo, do you know what Touch will use instead grilo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116098
Title:
[MIR] grilo
To manage notifications about this bug go to:
https://bugs.launchpad.ne
When you say that cache keeps the FD open, I guess you mean libsoup.
Have you really checked that indeed libsoup is keeping the FD open? Or
is just a theory? Which version of libsoup are you using? This shouldn't
happen (I've asked a libsoup maintainer), so if libsoup keeps the
descriptors open,
Each time you start grilo, and thus lastfm album, it creates a cache on
/tmp/grilo-plugin-cache-XXX, with each "XXX" different on each run.
When we exit, for different reasons, we don't remove those directories.
So they remain there. But they shouldn't be keep open: the OS should
free the descript
> There is no way to tell libsoup to close the fds it keeps open that I can
> see. Unless libsoup is fixed there are only two ways
> to work around this:
That's my point: it shouldn't be happening. I've asked a libsoup
maintainer, and he told me that libsoup shouldn't keep the files opened.
Hence
Hm..
In the example I only see one fd opened. Shouldn't be there *lot* of
descriptors opened?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224410
Title:
Last.fm plugin causes file descriptor star
But are you using threads? Nor grilo or soup-cache are thread safe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224410
Title:
Last.fm plugin causes file descriptor starvation
To manage notifi
Great.
I'll check it and fix in upstream. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224410
Title:
Last.fm plugin causes file descriptor starvation
To manage notifications about this b
The patch you attached is not entirely correct: the stream must be
unreffed later, after closing it.
I'm attaching a new version of the patch. Could you verify if this patch
fixes the problem? If so i'll push it upstream.
** Patch added: "unref-stream.patch"
https://bugs.launchpad.net/ubuntu/
Fixed upstream.
commit a6d96cd56dca6232ffdd92678b4c73adc5466b94
Author: Juan A. Suarez Romero
Date: Fri Sep 13 16:00:19 2013 +
net: unref stream after using it
https://bugs.launchpad.net/bugs/1224410
libs/net/grl-net-wc.c | 1 +
1 file changed, 1 insertion(+)
--
You receiv
The test suite in grilo is more than broken: as it is right now, it
tests mostly nothing.
It is not a matter of activating and fixing the tests: we need to remove
those tests and write a new one from scratch.
We have started to add more tests in the case of plugins, but didn't do
it yet in grilo
Florian: I don't think rhythmbox is filtering the bad plugins, though
any maintainer can confirm it. I think they just filter out those
plugins not interesting for rhythmbox, maybe because there's another
plugin in rhythmbox already providing such content, or just because the
the content provided i
Also, if something is working bad, it doesn't mean that the problem is
in the grilo plugins. Note that Totem and in Rythmbox also have use
Grilo through a totem-grilo or rhythmbox-grilo plugin. So the problem
can be there.
Grilo provides a test-ui that is useful to check if the problem is in
Grilo
The point is that the misbehaving could be in either the grilo plugins,
or in totem itself. So if the problem is in Totem, and you remove
plugins from the system, then other applications that work fine with
such plugins won't have the opportunity to use them.
On the other hand, such bugs could be
This bug has been closed due lack of activity.
Is anyone working on it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116098
Title:
[MIR] grilo
To manage notifications about this bug go to:
https
This is fixed upstream.
See https://bugzilla.gnome.org/show_bug.cgi?id=710185
** Bug watch added: GNOME Bug Tracker #710185
https://bugzilla.gnome.org/show_bug.cgi?id=710185
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
It is not that we need to finish them: we need to write them from
scratch. The tests you see were just an attempt to start, but never
success.
So forget about there "tests" directory: i'm going to remove that for
next release.
But, if the question is: "grilo does not have any test, and should", m
I think Vala 0.22 is already added in upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116098
Title:
[MIR] grilo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
17 matches
Mail list logo
