On Saturday 2013-08-31 17:16, Mantas Mikulėnas wrote:
>
>...sometimes I think Xorg should start at :1 instead, and reserve :0
>for annoying cronjobs and services that have DISPLAY=":0" hardcoded,
>to remind everyone that they're using a multi-user OS.
Go one step further and just pick a :random n
A somewhat more informative reply...
On Sat, Aug 31, 2013 at 4:35 PM, Jan Engelhardt wrote:
>
> On Saturday 2013-08-31 14:28, killermoehre wrote:
>>Doesn't Amarok starts if you prefix it with the right DISPLAY variable?
>>Like »DISPLAY=:0 amarok«. This should work from cron, too.
>
> Normally, yo
On Sat, Aug 31, 2013 at 4:35 PM, Jan Engelhardt wrote:
>
> On Saturday 2013-08-31 14:28, killermoehre wrote:
>>Doesn't Amarok starts if you prefix it with the right DISPLAY variable?
>>Like »DISPLAY=:0 amarok«. This should work from cron, too.
>
> Normally, you also need to set XAUTHORITY= to the
On Saturday 2013-08-31 14:28, killermoehre wrote:
>Am 31.08.2013 11:09, schrieb Manuel Amador (Rudd-O):
>> Based on systemd's related sibling loginctl, I managed to accomplish the
>> holy grail of the 90's: get Amarok to play music on my desktop sessiom
>> from a crontab (motivated by the missus'
Am 31.08.2013 11:09, schrieb Manuel Amador (Rudd-O):
> Based on systemd's related sibling loginctl, I managed to accomplish the
> holy grail of the 90's: get Amarok to play music on my desktop sessiom
> from a crontab (motivated by the missus' desire to have an alarm in the
> home theater that requ
Based on systemd's related sibling loginctl, I managed to accomplish the
holy grail of the 90's: get Amarok to play music on my desktop sessiom
from a crontab (motivated by the missus' desire to have an alarm in the
home theater that requires her to walk downstairs, to adapt to her
polyphasic sleep
