That does not seem to work either. I just copied my .lircrc (which is
full of irexec-stuff) into the file ~/.lirc/irexec and restarted, but it
didn't start irexec. Where is this feature even documented? How is a
regular user supposed to learn this? I'm back to launching irexec
manually from my
Mario Limonciello schrieb:
Otto Kekäläinen wrote:
I wondered for long why my Lirc installation does not work even though
all settings were correct and my ~/.lircrc was set up correctly. Finally
I realized, that irexec does not start automatically.
I fixed it by adding command irexec -d
Just Mythbuntu.
On Sun, Oct 12, 2008 at 04:36, laga [EMAIL PROTECTED] wrote:
Mario Limonciello schrieb:
Otto Kekäläinen wrote:
I wondered for long why my Lirc installation does not work even though
all settings were correct and my ~/.lircrc was set up correctly. Finally
I realized,
I wondered for long why my Lirc installation does not work even though
all settings were correct and my ~/.lircrc was set up correctly. Finally
I realized, that irexec does not start automatically.
I fixed it by adding command irexec -d into Gnome's session-system.
I think that Lirc should be
Otto Kekäläinen wrote:
I wondered for long why my Lirc installation does not work even though
all settings were correct and my ~/.lircrc was set up correctly. Finally
I realized, that irexec does not start automatically.
I fixed it by adding command irexec -d into Gnome's session-system.
The LIRC application won't be aware of userspace config files -
particularly if operating with NFS mounted home directories. This will
*always* have to be done by the user's login session. For your
particular application of this problem, i'd recommend adapting your
startup script that starts the
On Wed, 2008-09-24 at 05:52 +, Mario Limonciello wrote:
The LIRC application won't be aware of userspace config files
What userspace config files?
particularly if operating with NFS mounted home directories.
Recall, my MO is a STB. If there is anything NFS mounted there at all
it's a
ISTM that irexec startup could happen in at least two places, either
through a user logging (or being logged) in or through an STB startup
type method.
It may be that there is overlap between the STB startup and a user
logging in, however unless a user logging in means an automatic launch
of
** Changed in: lirc (Ubuntu)
Status: New = Confirmed
--
startup script does not start irexec
https://bugs.launchpad.net/bugs/224208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I saw your discussion in #ubuntu-mythtv at some point, and I believe I remember
it being dismissed.
I do support such an idea (so long as it is optional, and an opt in sort of
thing). Yeah, there is a mailing list, very low traffic.
https://lists.ubuntu.com/mailman/listinfo/Ubuntu-mythtv
10 matches
Mail list logo
