On Wednesday, July 10, 2013 11:03:14 AM Eric Viseur wrote:
> Just solved it, a much easier way. Thanks you for your advices, I directed
> me to taking a closer look to the logs. It lead me to discover that PA
> indeed started, but actually couldn't reach the sound card.
>
> What I did was simply
Just solved it, a much easier way. Thanks you for your advices, I directed
me to taking a closer look to the logs. It lead me to discover that PA
indeed started, but actually couldn't reach the sound card.
What I did was simply add my lowpriv user to the group audio, then start
PulseAudio, unmut
On Tuesday, July 09, 2013 04:01:47 PM Eric Viseur wrote:
> I'm currently working on a virtualization project using F18. One of the use
> cases is booting on the multi-user systemd target, then starting the Spice
> client in a very restricted X environment by simply issuing
>
> $ xinit /usr/bin/sp
Eric Viseur wrote:
> Hi,
>
> I'm currently working on a virtualization project using F18. One of the
> use cases is booting on the multi-user systemd target, then starting the
> Spice client in a very restricted X environment by simply issuing
>
> *$ xinit /usr/bin/spicec (some parameters)*
>
Sadly the daemon refuses to start. When started from console without the
log-level=0, the daemon seems to start, but I still can't get any sound out
of the box.
Eric Viseur
2013/7/9 Reindl Harald
>
>
> Am 09.07.2013 16:01, schrieb Eric Viseur:
> > I'm currently working on a virtualization pro
Am 09.07.2013 16:01, schrieb Eric Viseur:
> I'm currently working on a virtualization project using F18. One of the use
> cases is booting on the multi-user
> systemd target, then starting the Spice client in a very restricted X
> environment by simply issuing
>
> /$ xinit /usr/bin/spicec (so
