-
The attached (trivial) patch makes appuifw.Listbox throw a ValueError when it gets passed an empty list. This mimics PyS60 1.4.5 exactly.
2009-11-03 16:50:41 UTC in PyS60 Emulation Library
-
Indeed, that's what I thought.
Having multple exclusive connections as a feature would be nice, thanks!
2009-09-17 07:43:15 UTC in QjackCtl
-
I've added a patchbay configuration xml that shows the problem, no Mplayer involved :-)
To reproduce, start "japa -J" (or any other client that eats data, like jack-rack. You'll have to slightly change the patchbay then, of course).
Then, just jack.play to play any file, which should immediately show the problem: Every few hundred ms, a tiny fragment of sound is heard.
I hope you'll be...
2009-09-16 19:53:04 UTC in QjackCtl
-
Hmm, apparently my explanation wasn't clear enough. AFAICS, the mplayer case is just an example. I don't think mplayer's autoconnect is relevant to the bug (only to my discovering it).
What I suppose is happening is that exclusive mode does not remove any connections that are not in the patchbay, but it removes any connections that are not the last connection made in the patchbay...
2009-09-16 08:31:10 UTC in QjackCtl
-
I've been trying to use the "exclusive" checkbox in the patchbay, but there seems to be some brokenness there. I'm not 100% sure what "exclusive mode" means, but I expected to to prevent the application in question from making links itself.
I'll explain my situation: I'm playing audio with Mplayer, which finds itself a bunch of physical ports and connects itself to them. Since I want to play...
2009-09-15 07:59:06 UTC in QjackCtl
-
To see how I implemented this, see the following patch: http://git.stderr.nl/gitweb?p=servers.git;a=commitdiff;h=2f8315532658e5ad1acea72b357a5dc4878a4a93;hp=a31720f9f2b8f7e92d5e265bbe728e2756a7b7f6
It only changes iptables-multiport and requires the Debian jail.conf with two other changes (before this one in the same repository), but it serves well to illustrate my point.
2009-09-10 11:24:22 UTC in Fail2Ban
-
Currently, the default iptables-* actions of fail2ban always add a rule to the INPUT chain. This rule jumps to the relevant fail2ban chain which contains the actual bans, so not everything ends up in the INPUT chain, but the main entrypoint for fail2ban does.
This conflicts with my firewall, vuurmuur (and will probably conflict with others as well, see Debian #515599). When vuurmuur restarts...
2009-09-10 10:10:41 UTC in Fail2Ban
-
Uh, I don't actually think that this is something for fail2ban. fail2ban is designed to ban specific IP's when they generate failed login attempts. If you just want to statically ban a range of addresses, you should add such a rule to your regular firewall. I'm not so sure how this geoiplookup thing works, it might not give you one big range of addresses for each country, but can only do a...
2009-09-10 09:22:42 UTC in Fail2Ban
