Is there some way of restoring system sound, short of rebooting ?
On Fri, 24 Jan 2025, Roger Price wrote:
Is there some way of restoring system sound, short of rebooting ?
I need to be more precise, It's the cron job which is blocked, manual operation
still works correctly:
rprice@maria ~ /usr/local/bin/bark.sh 5
bark.sh starts ... XDG_RUNTIME_DIR=/run/user/2108
bark.sh calls Biff ... XDG_RUNTIME_DIR=/run/user/2108
Playing Sparc Audio '/mnt/home/rprice/bark/h5.au' : Mu-Law, Rate 8000 Hz, Mono
I hear the bark.
On Fri, 24 Jan 2025, Roger Price wrote:
rprice@maria ~ /usr/local/bin/bark.sh 5
bark.sh starts ... XDG_RUNTIME_DIR=/run/user/2108
bark.sh calls Biff ... XDG_RUNTIME_DIR=/run/user/2108
Playing Sparc Audio '/mnt/home/rprice/bark/h5.au' : Mu-Law, Rate 8000 Hz, Mono
I hear the bark.
What is it using to play the .au file? OSS, ALSA, or something
else?
I would guess that VLC is triggering the start of PulseAudio,
and after that PA has disabled OSS.
After VLC runs, does aplay work to play sounds?
On Fri, 24 Jan 2025, Dan Ritter wrote:
On Fri, 24 Jan 2025, Roger Price wrote:
rprice@maria ~ /usr/local/bin/bark.sh 5
bark.sh starts ... XDG_RUNTIME_DIR=/run/user/2108
bark.sh calls Biff ... XDG_RUNTIME_DIR=/run/user/2108
Playing Sparc Audio '/mnt/home/rprice/bark/h5.au' : Mu-Law, Rate 8000 Hz, Mono
I hear the bark.
What is it using to play the .au file? OSS, ALSA, or something
else?
rprice@maria ~ aplay -v ~/bark/h5.au
ALSA <-> PulseAudio PCM I/O Plugin
I would guess that VLC is triggering the start of PulseAudio,
and after that PA has disabled OSS.
After VLC runs, does aplay work to play sounds?
Yes and no. Yes - I can manually run aplay and hear the sound. No - a cron job
cannot use aplay and gets the error message:
OK, PulseAudio takes over ALSA, and from then on, only sessions
with PA active can play sounds. That means that your shell can
do it, but your cron can't.
Add this to your cron invocation or bark.sh.
export PULSE_RUNTIME_PATH="/run/user/$(id -u)/pulse/"
I added export PULSE_RUNTIME_PATH="/run/user/$(id -u)/pulse" to bark.sh . File /run/user/2108/pulse contains value 1309 and command
rprice@maria ~ ps -ef | grep pulse
rprice 1309 1293 0 2024 ? 05:45:10 /usr/bin/pulseaudio
--daemonize=no --log-target=journal
confirms that this is pulseaudio. But I still do not hear any sound from the cron job, which reports
From: Cron Daemon <root@maria.rogerprice.org>
Subject: Cron <rprice@maria> /mnt/home/rprice/bark/bark.sh S45
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
aplay: main:831: audio open error: Device or resource busy
2) At least one of my environment variables is required:
hobbit:~$ aplay /usr/share/sounds/alsa/Side_Left.wav
Playing WAVE '/usr/share/sounds/alsa/Side_Left.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
hobbit:~$ env - aplay /usr/share/sounds/alsa/Side_Left.wav
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
aplay: main:831: audio open error: No such file or directory
So then the question is *which* environment variable it is. I would
suspect it's one of the XDG_ variables, but I'm not in the mood to go
through them one by one to see which one makes the audio start working.
On 1/24/25 09:47, Greg Wooledge wrote:
2) At least one of my environment variables is required:
So then the question is *which* environment variable it is. I would suspect it's one of the XDG_ variables,
I did it the other way, by seeing which I remove to make the audio stop working. Probably easier in case there were more than one. Anyhow my testing shows the critical variable to be XDG_RUNTIME_DIR .
On Fri, 24 Jan 2025, eben@gmx.us wrote:
On 1/24/25 09:47, Greg Wooledge wrote:
2) At least one of my environment variables is required:
So then the question is *which* environment variable it is. I would
suspect it's one of the XDG_ variables,
I did it the other way, by seeing which I remove to make the audio stop
working. Probably easier in case there were more than one. Anyhow my
testing shows the critical variable to be XDG_RUNTIME_DIR .
I found that XDG_RUNTIME_DIR is necessary but not sufficient. I added XDG_RUNTIME_DIR="/run/user/$(id -u)" to my personal crontab, but this did not solve the problem. I added
export XDG_RUNTIME_DIR="/run/user/$(id -u)"
to bark.sh, but this also failed to solve the problem. Roger
Maybe a difference in some software? I ran
eben@cerberus:~$ env - XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/aplay /export/media/sounds/woow1.wav
Playing WAVE '/export/media/sounds/woow1.wav' : Unsigned 8 bit, Rate 11025 Hz, Mono
and it worked.
env - XDG_RUNTIME_DIR=/run/user/1000 aplay /usr/share/sounds/alsa/Side_Left.wavjob 2 at Fri Jan 24 14:16:00 2025
<EOT>
On Fri, Jan 24, 2025 at 13:52:00 -0500, eben@gmx.us wrote:
Maybe a difference in some software? I ran
eben@cerberus:~$ env - XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/aplay /export/media/sounds/woow1.wav
Playing WAVE '/export/media/sounds/woow1.wav' : Unsigned 8 bit, Rate 11025 Hz, Mono
and it worked.
On Fri, Jan 24, 2025 at 13:52:00 -0500, eben@gmx.us wrote:
Maybe a difference in some software? I ran
eben@cerberus:~$ env - XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/aplay
/export/media/sounds/woow1.wav
Playing WAVE '/export/media/sounds/woow1.wav' : Unsigned 8 bit, Rate 11025 >>> Hz, Mono
and it worked.
That works for me too, but not in cron. Could you create a temporary personal
cron job with crontab -e which sets
XDG_RUNTIME_DIR="/run/user/$(id -u)"
and runs
M H * * * aplay /usr/share/sounds/alsa/Side_Left.wav
where M is the minute 0-59 and H is the hour 0-23. I shall do exactly the same. Roger
In viewing the full header of the above message (to try to find which
country or timezone, is the origin of the message sent to the mailing list, for an extraneous reason), I observed a weird thing, that makes me wonder whether the mailing list and/or Debian, is, as is apparently shown,
connected to the infamous NSA.
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
Could someone please clarify the apparent involvement of the NSA in this mailing list?
Or, is the mailing list simply under surveillance by the NSA?
Thank you in anticipation.
..
Bret Busby
Armadale
West Australia
(UTC+0800)
..............
On Fri, Jan 24, 2025 at 13:52:00 -0500, eben@gmx.us wrote:
Maybe a difference in some software? I ran
eben@cerberus:~$ env - XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/aplay
/export/media/sounds/woow1.wav
Playing WAVE '/export/media/sounds/woow1.wav' : Unsigned 8 bit, Rate 11025 >>> Hz, Mono
and it worked.
That works for me too, but not in cron. Could you create a temporary personal
cron job with crontab -e which sets
XDG_RUNTIME_DIR="/run/user/$(id -u)"
and runs
M H * * * aplay /usr/share/sounds/alsa/Side_Left.wav
where M is the minute 0-59 and H is the hour 0-23. I shall do exactly the same. Roger
That works for me too, but not in cron. Could you create a temporary personal
cron job with crontab -e which sets
XDG_RUNTIME_DIR="/run/user/$(id -u)"
and runs
M H * * * aplay /usr/share/sounds/alsa/Side_Left.wav
where M is the minute 0-59 and H is the hour 0-23. I shall do exactly the same. Roger
OK. My crontab has this:
XDG_RUNTIME_DIR="/run/user/$(id -u)"
# m h dom mon dow command
* * 24 1 * aplay /export/media/sounds/woow1.wav
At the minute, no sound. I tried
id=$(id -u)
XDG_RUNTIME_DIR=/run/user/$id
and
id=1000
XDG_RUNTIME_DIR=/run/user/$id
and no dice.
I tried
XDG_RUNTIME_DIR=/run/user/1000
and it worked. Maybe this cron doesn't do variables in assignments?
I suspect it's coincidental / benign or a joke, given that it's a Microsoft-ism
here.
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
On Sat, 25 Jan 2025, Bret Busby wrote:Okay...
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
This comes from a customized-hdrs entry in my .pinerc added as a joke by a friend many years ago. I am a long time pine user, and it has been carried on
unwittingly from one OS release to the next. After all these years, you are the
first to have remarked publicly. No government organisation has tried to contact me openly.
I hope you were not too frightened, but vigilance is a fine quality.
Roger
OK. My crontab has this:
XDG_RUNTIME_DIR="/run/user/$(id -u)"
# m h dom mon dow command
* * 24 1 * aplay /export/media/sounds/woow1.wav
At the minute, no sound. I tried
id=$(id -u)
XDG_RUNTIME_DIR=/run/user/$id
and
id=1000
XDG_RUNTIME_DIR=/run/user/$id
and no dice. I tried
XDG_RUNTIME_DIR=/run/user/1000
and it worked. Maybe this cron doesn't do variables in assignments?
I suspect it's coincidental / benign or a joke, given that it's a Microsoft-ism
here.
(Or maybe that's what they want you to think ;-) )
On Sat, 25 Jan 2025, Bret Busby wrote:
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
This comes from a customized-hdrs entry in my .pinerc added as a joke by a friend many years ago. I am a long time pine user, and it has been carried on
unwittingly from one OS release to the next. After all these years, you are the
first to have remarked publicly. No government organisation has tried to contact me openly.
I hope you were not too frightened, but vigilance is a fine quality.
Roger
On Fri, 24 Jan 2025, eben@gmx.us wrote:
That works for me too, but not in cron. Could you create a temporary personal
cron job with crontab -e which sets
XDG_RUNTIME_DIR="/run/user/$(id -u)"
and runs
M H * * * aplay /usr/share/sounds/alsa/Side_Left.wav
where M is the minute 0-59 and H is the hour 0-23. I shall do exactly the >>> same. Roger
OK. My crontab has this:
XDG_RUNTIME_DIR="/run/user/$(id -u)"
# m h dom mon dow command
* * 24 1 * aplay /export/media/sounds/woow1.wav
At the minute, no sound. I tried
id=$(id -u)
XDG_RUNTIME_DIR=/run/user/$id
and
id=1000
XDG_RUNTIME_DIR=/run/user/$id
and no dice.
I suspect that in a personal crontab entry $(id -u) may not refer to the user but maybe to root. Perhaps there is another way to get the user's uid.
I tried
XDG_RUNTIME_DIR=/run/user/1000
and it worked. Maybe this cron doesn't do variables in assignments?
Could you now run VLC for a short while and then rerun the personal crontab test with uid 1000 ?. Thanks, Roger
On Sat, 25 Jan 2025, Bret Busby wrote:
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
This comes from a customized-hdrs entry in my .pinerc added as a joke
by a friend many years ago. I am a long time pine user, and it has
been carried on unwittingly from one OS release to the next. After
all these years, you are the first to have remarked publicly. No
government organisation has tried to contact me openly.
I hope you were not too frightened, but vigilance is a fine quality.
Roger
On Fri, 24 Jan 2025 23:31:44 +0100 (CET)
Roger Price <roger@rogerprice.org> wrote:
On Sat, 25 Jan 2025, Bret Busby wrote:
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
This comes from a customized-hdrs entry in my .pinerc added as a joke
by a friend many years ago. I am a long time pine user, and it has
been carried on unwittingly from one OS release to the next. After
all these years, you are the first to have remarked publicly. No
government organisation has tried to contact me openly.
I hope you were not too frightened, but vigilance is a fine quality.
Roger
Are you also responsible for this?
"X-Message-Flag: Cannot contact reaper.nsa.gov. Trying bucket.cia.gov.."
Or:
"X-Message-Flag: WARNING: Danger from LLM misuse - find shelter!"
On Fri, 24 Jan 2025 23:31:44 +0100 (CET)
Roger Price <roger@rogerprice.org> wrote:
"X-Message-Flag: Cannot contact reaper.nsa.gov. Trying bucket.cia.gov.."
In viewing the full header of the above message (to try to find
which country or timezone, is the origin of the message sent
to the mailing list, for an extraneous reason), I observed a
weird thing, that makes me wonder whether the mailing list and/or
Debian, is, as is apparently shown, connected to the infamous NSA.
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
Could someone please clarify the apparent
involvement of the NSA in this mailing list?
Or, is the mailing list simply under surveillance by the NSA?
..
Bret Busby
Armadale
West Australia
(UTC+0800)
X-Message-Flag
The header field "X-Message-Flag" is used by Microsoft
mail clients and can contain a custom text. Mail clients from
Microsoft (such as Outlook) use this header field when converting
Message objects used by Microsoft products to MIME messages.
I suspect it's coincidental / benign or a
joke, given that it's a Microsoft-ism here.
(Or maybe that's what they want you to think ;-) )
With every good wish, as ever,
Andrew Cater
(amacater@debian.org)
On Fri, Jan 24, 2025, 5:05 PM Bret Busby <bret@busby.net> wrote:
On 25/1/25 06:31, Andrew M.A. Cater wrote:
<snip>
I suspect it's coincidental / benign or a joke, given that it's aMicrosoft-ism
here.
(Or maybe that's what they want you to think ;-) )
Ah, yes.
"We live in interesting times, where the only thing to fear, is the government"
Fool :-D
Fear the people who _own_ the government.
Are you also responsible for this?
"X-Message-Flag: Cannot contact reaper.nsa.gov. Trying bucket.cia.gov.."
Or:
"X-Message-Flag: WARNING: Danger from LLM misuse - find shelter!"
On Sat, Jan 25, 2025 at 06:12:30AM +0800, Bret Busby wrote:
In viewing the full header of the above message (to try to find
which country or timezone, is the origin of the message sent
to the mailing list, for an extraneous reason), I observed a
weird thing, that makes me wonder whether the mailing list and/or
Debian, is, as is apparently shown, connected to the infamous NSA.
"X-Message-Flag Supplemental report sent to reaper.nsa.gov. rc=0"
Could someone please clarify the apparent
involvement of the NSA in this mailing list?
Or, is the mailing list simply under surveillance by the NSA?
..
Bret Busby
Armadale
West Australia
(UTC+0800)
* Andrew M.A. Cater <amacater@einval.com> [25-01/24=Fri 22:31 +0000]:
X-Message-Flag
The header field "X-Message-Flag" is used by Microsoft
mail clients and can contain a custom text. Mail clients from
Microsoft (such as Outlook) use this header field when converting
Message objects used by Microsoft products to MIME messages.
I suspect it's coincidental / benign or a
joke, given that it's a Microsoft-ism here.
(Or maybe that's what they want you to think ;-) )
With every good wish, as ever,
Andrew Cater
(amacater@debian.org)
Air quality in Seattle is monitored by volunteers who buy and
operate monitoring stations, and publish their observations
every hour. They can name their stations whatever they want, so
usually pick nearby street names or other geographic features.
One monitoring station is named "FBI Surveillance Van".
On Sat, 25 Jan 2025 08:49:06 +0100 (CET)
Roger Price <debian@rogerprice.org> wrote:
Are you also responsible for this?
"X-Message-Flag: Cannot contact reaper.nsa.gov. Trying
bucket.cia.gov.." Or:
"X-Message-Flag: WARNING: Danger from LLM misuse - find shelter!"
Not at all. This is the first time I have seen these. Did you see
them in the debian-user mailing list ? Roger
Yup. In the last 180 days' traffic.
Are you also responsible for this?
"X-Message-Flag: Cannot contact reaper.nsa.gov. Trying
bucket.cia.gov.." Or:
"X-Message-Flag: WARNING: Danger from LLM misuse - find shelter!"
Not at all. This is the first time I have seen these. Did you see
them in the debian-user mailing list ? Roger
On 2025-01-25, Bret Busby <bret@busby.net> wrote:
Someone has already claimed ownership of the first of the two; about
bucketing the CIA.
OT.
OK. My crontab has this:
XDG_RUNTIME_DIR="/run/user/$(id -u)"
At the minute, no sound. I tried
id=$(id -u)
XDG_RUNTIME_DIR=/run/user/$id
and
id=1000
XDG_RUNTIME_DIR=/run/user/$id
and no dice. I tried
XDG_RUNTIME_DIR=/run/user/1000
and it worked.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 02:30:23 |
| Calls: | 10,385 |
| Calls today: | 2 |
| Files: | 14,057 |
| Messages: | 6,416,582 |