Has this changed in the 4 years since? I just tried saned on 12.04, then 14.04,
and the same problem occurs on both of them.
Indeed, ps listing reveals 2 saned processes running, with only 1 of them being
bound to only tcp6.
--
You received this bug notification because you are a member of
** Summary changed:
- ogg123 can't play some flac files
+ ogg123 can't play flac files with ID3 tags
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vorbis-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1250618
Title:
ogg123 can't
** Description changed:
1) Kubuntu saucy (13.10) amd64
2) 1.4.0-1ubuntu3
- ogg123 command from vorbis-tools refuses to play some flac files. mplayer2
has no issue with the same file:
- $ ogg123 /tmp/02.The\ Lioness.flac
+ ogg123 command from vorbis-tools refuses flac files with id3 tags.
Filed ticket upstream:
https://trac.xiph.org/ticket/1988
** Bug watch added: Xiph.org Trac #1988
http://trac.xiph.org/ticket/1988
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vorbis-tools in Ubuntu.
Public bug reported:
1) Kubuntu saucy (13.10) amd64
2) 1.4.0-1ubuntu3
ogg123 command from vorbis-tools refuses to play some flac files. mplayer2 has
no issue with the same file:
$ ogg123 /tmp/02.The\ Lioness.flac
Audio Device: Advanced Linux Sound Architecture (ALSA) output
Error opening
You can get the flac file in question here:
https://mega.co.nz/#!5U5VmSiY!BV6QekSpym-_USdutnWtHHCT45VGEd-
_i0KxPO7Axxs (~35MiB)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vorbis-tools in Ubuntu.
I believe that Redhat's network-scripts are above network-manager and
NM will not touch any interface that is configured using ifcfg and
doesn't have a special line in the file (NM_MANAGED it is, I think).
In (Debian and) Ubuntu, the role of network-scripts is taken by
/etc/network/interfaces. See
I don't know, I've never actually tried to use NM with a virtual interface that
has slave physical interfaces. And yes, it seems to me too that mentioning an
interface in the interfaces file makes NM not touch it. NM has its own
configuration storage, which, as I've read, is not intended for
Probably watching activity on gitweb :) I've learned about bonding
support in dcbw's blog post: http://blogs.gnome.org/dcbw/2011/11/10
/blue-sky-white-sand-and-networkmanager-0-9-2/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
9 matches
Mail list logo
