Closed GoogleCodeExporter closed 9 years ago
Quod Libet uses a socket, located by default in $HOME/.quodlibet/control, to
implement remote control. Please make sure your $HOME directory is set
correctly in
both the running instance of QL and the shell from which you try to control QL.
If this is not the issue, post another comment and the bug will be reopened.
Original comment by steven.strobe.cc@gmail.com
on 15 Mar 2009 at 1:02
Hi,
thanks for the answer.
I don't know if I get it right, but I have checked $HOME/.quodlibet/ , I found
there
a file witch implement the default shortcuts of quodlibet (as
<control><shift><;>).
They work fine. My problem is that quodlibet is not listed as running and
therefor I
can't manage it using simple command line commands (as quodlibet --next), like
I did
before, with custom shortcuts in my window manager. This allow to manage
quodlibet
even if he don't have the focus.
Original comment by gigotdagneau@gmail.com
on 15 Mar 2009 at 7:33
I do exactly the same thing, and it works for me; if it's still a problem, more
information is needed to fix it. Please check that $HOME/.quodlibet/control
exists
while you are running QL. Also, please close QL and then open up two terminals.
In
the first one, run
$ QUODLIBET_DEBUG=1 quodlibet
and in the second one,
$ quodlibet --play-pause
and see what happens. It's important that they both be launched in terminals
because
I think something is messing with your environment, and that's a simple way to
get
two nearly-identical environments.
Original comment by steven.strobe.cc@gmail.com
on 19 Mar 2009 at 6:43
Hi,
I have no $HOME/.quodlibet/control file, only : accels, config, feeds, queue and
songs. (I am running under gentoo).
I runned both commands in separated terminals, nothing happened. Only those
messages
as output of the first terminal:
<code>
Supported formats: mp3, mp4, wav, wma, xiph
Loaded song library.
Opening audio device.
W: couldn't connect to HAL, disabling MediaDevices browser
</code>
and following in the other terminal:
<code>
Quod Libet is not running.
</code>
Thanks for helping me.
Original comment by gigotdagneau@gmail.com
on 19 Mar 2009 at 7:52
Original issue reported on code.google.com by
gigotdagneau@gmail.com
on 12 Mar 2009 at 2:37