On Mon, 28 Jun 2021 at 16:28:56 +0200, Masaru Nomiya wrote:
Wolfgang Mueller <wm@ariannuccia.de> has written:
On Mon, 28 Jun 2021 at 11:54:21 +0200, Masaru Nomiya wrote:
Wolfgang Mueller <wm@ariannuccia.de> has written:
I recently installed Leap 15.3 on my computers "hp" and "se".
Configuring the sound cards by yast worked on "se" only, whereas on "hp" the following error message appears: ================================================================= An error occurred during the installation of
GP107GL High Definition Audio Controller
The kernel module snd-hda-intel for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters. ================================================================== The same for the other sound card, called "Cannon Lake PCH cAVS".
How can I correct the kernel module snd-hda-intel and provide the correct module, IO, or IRQ parameters?
These will help you.
https://github.com/spotify/linux/blob/master/Documentation/sound/alsa/ALSA-C...
https://github.com/spotify/linux/blob/master/Documentation/sound/alsa/HD-Aud...
The first of these two sites contains a section entitled "Module snd-hda-intel". However, it tells me neither where to find this module, nor how to include it in the kernel. Do you have an idea?
Thank you for your reply, Masaru.
snd-hda-intel is a kernel module which is this: /lib/modules/[kernel-version]-default/kernel/sound/pci/hda/snd-hda-intel.ko
On my computer it is /lib/modules/5.3.18-59.5-default/kernel/sound/pci/hda/snd-hda-intel.ko.xz which has to be unpacked by "unxz". This file is the same than that on my computer "se", where setting up the sound cards has been possible.
To get the sound card's information, execute:
$ /usr/sbin/alsa-info.sh --with-devices
This produces the file 'alsa-info.txt.XXXXX' on /tmp folder. In it, you can get the information for setting up.
It contains a lot of information, but no hint how to set up my sound cards. Please have a look on the file attached below. Best regards, Wolfgang
Hello, In the Message; Subject : Re: Sound card configuration problem Message-ID : <cb75bbe6-f01d-96a5-8a44-83341fda52db@ariannuccia.de> Date & Time: Tue, 29 Jun 2021 10:08:44 +0200 [WM] == Wolfgang Mueller <wm@ariannuccia.de> has written: WM> [1 <text/plain; iso-8859-15 (8bit)>] WM> On Mon, 28 Jun 2021 at 16:28:56 +0200, Masaru Nomiya wrote: [...] WM> >> module, nor how to include it in the kernel. Do you have an idea? WM> Thank you for your reply, Masaru. WM> > snd-hda-intel is a kernel module which is this: WM> > /lib/modules/[kernel-version]-default/kernel/sound/pci/hda/snd-hda-intel.ko WM> On my computer it is WM> /lib/modules/5.3.18-59.5-default/kernel/sound/pci/hda/snd-hda-intel.ko.xz WM> which has to be unpacked by "unxz". No, you can keep it. Of cource, the system can treat snd-hda-intel.ko, too. WM> This file is the same than that on my computer "se", where setting up the sound WM> cards has been possible. WM> > To get the sound card's information, execute: WM> > WM> > $ /usr/sbin/alsa-info.sh --with-devices WM> > WM> > This produces the file 'alsa-info.txt.XXXXX' on /tmp folder. WM> > In it, you can get the information for setting up. WM> It contains a lot of information, but no hint how to set up my sound WM> cards. Please have a look on the file attached below. Thanks. Cards are confilcting. WM> !!Loaded ALSA modules WM> !!------------------- WM> Please do as follows; $ sudo vi /etc/pulse/default.pa load-module module-stream-restore restore_device=false that is, add 'restore_device=false' to the line. then, $ pacmd list-sinks | grep name: Show me this result. Regatds. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
Hello, Sorrry, I've forggoten wo write on procedure. In the Message; Subject : Re: Sound card configuration problem Message-ID : <87v95xgjr6.wl-nomiya@galaxy.dti.ne.jp> Date & Time: [MN] == Masaru Nomiya <nomiya@galaxy.dti.ne.jp> has written: MN> Hello, MN> In the Message; MN> Subject : Re: Sound card configuration problem MN> Message-ID : <cb75bbe6-f01d-96a5-8a44-83341fda52db@ariannuccia.de> MN> Date & Time: Tue, 29 Jun 2021 10:08:44 +0200 MN> [WM] == Wolfgang Mueller <wm@ariannuccia.de> has written: WM> [1 <text/plain; iso-8859-15 (8bit)>] WM> On Mon, 28 Jun 2021 at 16:28:56 +0200, Masaru Nomiya wrote: MN> [...] WM> >> module, nor how to include it in the kernel. Do you have an idea? WM> Thank you for your reply, Masaru. WM> > snd-hda-intel is a kernel module which is this: WM> > /lib/modules/[kernel-version]-default/kernel/sound/pci/hda/snd-hda-intel.ko WM> On my computer it is WM> /lib/modules/5.3.18-59.5-default/kernel/sound/pci/hda/snd-hda-intel.ko.xz WM> which has to be unpacked by "unxz". MN> No, you can keep it. MN> Of cource, the system can treat snd-hda-intel.ko, too. WM> This file is the same than that on my computer "se", where setting up the sound WM> cards has been possible. WM> > To get the sound card's information, execute: WM> > WM> > $ /usr/sbin/alsa-info.sh --with-devices WM> > WM> > This produces the file 'alsa-info.txt.XXXXX' on /tmp folder. WM> > In it, you can get the information for setting up. WM> It contains a lot of information, but no hint how to set up my sound WM> cards. Please have a look on the file attached below. MN> Thanks. MN> Cards are confilcting. WM> !!Loaded ALSA modules WM> !!------------------- MN> WM> MN> Please do as follows; MN> $ sudo vi /etc/pulse/default.pa MN> load-module module-stream-restore restore_device=false MN> that is, add 'restore_device=false' to the line. MN> then, MN> $ pacmd list-sinks | grep name: Please insert MN> then, $ pulseaudio -k <-- this operation MN> $ pacmd list-sinks | grep name: Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ Think. -- The IBM slogan --
On Tue, 29 Jun 2021 at 10:31:08 +0200, Masaru Nomiya wrote:
[...] Please do as follows;
$ sudo vi /etc/pulse/default.pa load-module module-stream-restore restore_device=false
that is, add 'restore_device=false' to the line.
Being not familiar with vi, I have logged in as root and then modified /etc/pulse/default.pa this way: $ cd /etc/pulse $ mv default.pa default.pa.bak $ sed -e 's,^\(load-module module-stream-restore\)$,\1 restore_device=false,' default.pa.bak > default.pa $ diff default.pa default.pa.bak This diff statement produced the response: 25c25 < load-module module-stream-restore restore_device=false --- > load-module module-stream-restore
then,
$ pacmd list-sinks | grep name:
This statement produced the response: "No PulseAudio daemon running, or not running as session daemon."
Please insert
What do you want me to insert?
then,
$ pulseaudio -k <-- this operation
As expected, this statement produced the response: "Failed to kill daemon: No such process"
$ pacmd list-sinks | grep name:
Again, this statement produced the response: "No PulseAudio daemon running, or not running as session daemon." So, I think I have at first to start the PulseAudio daemon before I can do "pacmd list-sinks | grep name:". Thanks a lot, Masaru! Best regard, Wolfgang
On 29/06/2021 12.05, Wolfgang Mueller wrote:
$ pacmd list-sinks | grep name:
Again, this statement produced the response: "No PulseAudio daemon running, or not running as session daemon."
So, I think I have at first to start the PulseAudio daemon before I can do "pacmd list-sinks | grep name:".
It is possible that it failed to start, or that you are not using pulse. You can try first: systemctl --user status pulseaudio.service as user. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Tue, 29 Jun 2021 at 12:47:42 +0200, Carlos E. R. wrote:
On 29/06/2021 12.05, Wolfgang Mueller wrote:
$ pacmd list-sinks | grep name:
Again, this statement produced the response: "No PulseAudio daemon running, or not running as session daemon."
So, I think I have at first to start the PulseAudio daemon before I can do "pacmd list-sinks | grep name:".
It is possible that it failed to start, or that you are not using pulse.
I tried to start it by invoking "start-pulseaudio-x11", getting, however, this response: Connection failure: Connection refused pa_context_connect() failed: Connection refused
You can try first:
systemctl --user status pulseaudio.service
as user.
"systemctl --user status pulseaudio.service" gives the result: Failed to get properties: Process org.freedesktop.systemd1 exited with status 1 The result may be simplified by omitting "--user": "systemctl status pulseaudio.service" gives the result: Unit pulseaudio.service could not be found. Thank you and best regards, Wolfgang
Hello, In the Message; Subject : Re: Sound card configuration problem Message-ID : <20db7ef7-26e9-769d-ce3e-b6921fa503ae@ariannuccia.de> Date & Time: Tue, 29 Jun 2021 13:56:39 +0200 [WM] == Wolfgang Mueller <wm@ariannuccia.de> has written: [...] WM> "systemctl --user status pulseaudio.service" WM> gives the result: WM> Failed to get properties: WM> Process org.freedesktop.systemd1 exited with status 1 WM> The result may be simplified by omitting "--user": WM> "systemctl status pulseaudio.service" WM> gives the result: WM> Unit pulseaudio.service could not be found. 1. $ sudo systemctl enable pulseaudio.service 2. $ sudo systemctl start pulseaudio.service 3. confirm 'enable' $ sudo systemctl status pulseaudio.service If enabled, $ pulseaudio --start 4. confirm 'enable' $ systemctl --user status pulseaudio.service If enabled, just show the results of; 5.1 $ pacmd list-cards 5.2 $ pacmd list snd 5.3 $ pacmd list-sinks 5.4 $ aplay -L Regards, and Good Night. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
On Tue, 29 Jun 2021 15:03:31 +0200, Masaru Nomiya wrote:
Wolfgang Mueller <wm@ariannuccia.de> has written: [...]
"systemctl --user status pulseaudio.service" gives the result: Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
The result may be simplified by omitting "--user":
"systemctl status pulseaudio.service" gives the result: Unit pulseaudio.service could not be found.
1. $ sudo systemctl enable pulseaudio.service
This statement produces the response: "Failed to enable unit: Unit file pulseaudio.service does not exist."
2. $ sudo systemctl start pulseaudio.service
This statement produces an analogous response: "Failed to start pulseaudio.service: Unit pulseaudio.service not found."
3. confirm 'enable' $ sudo systemctl status pulseaudio.service
Again, a failure is reported: "Unit pulseaudio.service could not be found." After these failures, the following statements failed too, as you can imagine.
If enabled, $ pulseaudio --start
4. confirm 'enable' > $ systemctl --user status pulseaudio.service
If enabled, just show the results of;
5.1 $ pacmd list-cards
5.2 $ pacmd list snd
5.3 $ pacmd list-sinks
5.4 $ aplay -L
Regards, and Good Night.
Here in Europe we have still daylight. Best regards, Wolfgang
On 29/06/2021 13.56, Wolfgang Mueller wrote:
On Tue, 29 Jun 2021 at 12:47:42 +0200, Carlos E. R. wrote:
On 29/06/2021 12.05, Wolfgang Mueller wrote:
$ pacmd list-sinks | grep name:
Again, this statement produced the response: "No PulseAudio daemon running, or not running as session daemon."
So, I think I have at first to start the PulseAudio daemon before I can do "pacmd list-sinks | grep name:".
It is possible that it failed to start, or that you are not using pulse.
I tried to start it by invoking "start-pulseaudio-x11", getting, however, this response: Connection failure: Connection refused pa_context_connect() failed: Connection refused
You can try first:
systemctl --user status pulseaudio.service
as user.
"systemctl --user status pulseaudio.service" gives the result: Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
The result may be simplified by omitting "--user":
"systemctl status pulseaudio.service" gives the result: Unit pulseaudio.service could not be found.
It is a user service. Trying to access the root service will fail, it is normally not installed. So "--user" is necesary. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: Sound card configuration problem Message-ID : <00382e64-0fea-e42e-4928-3499b5c899fc@telefonica.net> Date & Time: Tue, 29 Jun 2021 21:17:56 +0200 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: CER> On 29/06/2021 13.56, Wolfgang Mueller wrote: CER> > On Tue, 29 Jun 2021 at 12:47:42 +0200, Carlos E. R. wrote: CER> >> On 29/06/2021 12.05, Wolfgang Mueller wrote: [...] CER> > CER> > "systemctl status pulseaudio.service" CER> > gives the result: CER> > Unit pulseaudio.service could not be found. CER> It is a user service. Trying to access the root service will fail, it is CER> normally not installed. So "--user" is necesary. Certainly, that's it. But, his case in very complicated..... How about this? $ systemctl --user enable/start pulseaudio.service/socket Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ Think. -- The IBM slogan --
On Tue, 29 Jun 2021 at 23:56:40 +0200, Masaru Nomiya wrote:
Carlos E. R. has written:
On 29/06/2021 13.56, Wolfgang Mueller wrote:
[...] "systemctl status pulseaudio.service" gives the result: Unit pulseaudio.service could not be found.
It is a user service. Trying to access the root service will fail, it is normally not installed. So "--user" is necesary.
Certainly, that's it.
But, his case in very complicated..... How about this? $ systemctl --user enable/start pulseaudio.service/socket
This statement produces the response: "Unknown command verb enable/start." Best regards, Wolfgang
Hello, In the Message; Subject : Re: Sound card configuration problem Message-ID : <87f14fa5-1785-ef57-d1fa-56068c139dbc@ariannuccia.de> Date & Time: Wed, 30 Jun 2021 09:25:38 +0200 [WM] == Wolfgang Mueller <wm@ariannuccia.de> has written: WM> On Tue, 29 Jun 2021 at 23:56:40 +0200, Masaru Nomiya wrote: WM> > Carlos E. R. has written: WM> >> On 29/06/2021 13.56, Wolfgang Mueller wrote: WM> >>> [...] WM> >>> "systemctl status pulseaudio.service" WM> >>> gives the result: WM> >>> Unit pulseaudio.service could not be found. WM> >> WM> >> It is a user service. Trying to access the root service will WM> >> fail, it is normally not installed. So "--user" is necesary. WM> > WM> > Certainly, that's it. WM> > WM> > But, his case in very complicated..... WM> > How about this? WM> > $ systemctl --user enable/start pulseaudio.service/socket WM> This statement produces the response: WM> "Unknown command verb enable/start." Ah, as expected.... What messages do you get with this? & pulseaudio Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "No Windows, no gains!" ..... "Why, I am wrong?" -- Bill --
On Wed, 30 Jun 2021 at 10:32:43 +0200, Masaru Nomiya wrote:
Wolfgang Mueller <wm@ariannuccia.de> has written:
On Tue, 29 Jun 2021 at 23:56:40 +0200, Masaru Nomiya wrote:
Carlos E. R. has written:
On 29/06/2021 13.56, Wolfgang Mueller wrote:
[...] "systemctl status pulseaudio.service" gives the result: Unit pulseaudio.service could not be found.
It is a user service. Trying to access the root service will fail, it is normally not installed. So "--user" is necesary.
Certainly, that's it.
But, his case in very complicated..... How about this? $ systemctl --user enable/start pulseaudio.service/socket
This statement produces the response: "Unknown command verb enable/start."
Ah, as expected....
What messages do you get with this? $ pulseaudio
Invoked as "pulseaudio" by root, it says: "W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified)." Invoked as "pulseaudio" by a user, its reply is: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied" If the system did not keep secret the home directory's name, I could do a "chmod 777". Invoked as "sudo pulseaudio" by a user, it produces these 3 lines: [1] "W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified)." [2] "W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11" [3] "W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11" Best regards, Wolfgang
Hello, In the Message; Subject : Re: Sound card configuration problem Message-ID : <1b039eac-2a0e-e6d1-cb0a-ea1146ed50c2@ariannuccia.de> Date & Time: Wed, 30 Jun 2021 12:35:30 +0200 [WM] == Wolfgang Mueller <wm@ariannuccia.de> has written: [...] MN> > What messages do you get with this? MN> > $ pulseaudio WM> Invoked as "pulseaudio" by root, it says: WM> "W: [pulseaudio] main.c: This program is not intended to be run as root (unless WM> --system is specified)." WM> Invoked as "pulseaudio" by a user, its reply is: WM> "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied" WM> If the system did not keep secret the home directory's name, I WM> could do a "chmod 777". WM> Invoked as "sudo pulseaudio" by a user, it produces these 3 lines: WM> [1] "W: [pulseaudio] main.c: This program is not intended to be run as root WM> (unless --system is specified)." WM> [2] "W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: WM> org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon WM> without a $DISPLAY for X11" WM> [3] "W: [pulseaudio] main.c: Unable to contact D-Bus: WM> org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon WM> without a $DISPLAY for X11" Please try as an user, not necessary as a root. Anyway, 1. please check this works or not; $ export DISPLAY=:0 $ pulseaudio 2. if works, goto 3., if not got 5 3. $ echo DISPLAY=:0 >> ~/.bashrc $ source ~/.bashrc after this, $ pulseaudio If works, just show the results of; 4.1 $ pacmd list-cards 4.2 $ pacmd list snd 4.3 $ pacmd list-sinks 4.4 $ aplay -L 5. If you still get the D-Bus related error messages; please show the output of this; $ cat DBUS_SESSION_BUS_ADDRESS Regards. at 8:80 PM JST. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
On Wed, 30 Jun 2021 13:38:50 +0200, Masaru Nomiya wrote:
Wolfgang Mueller has written:
[...] On Tue, 29 Jun 2021 at 23:56:40 +0200, Masaru Nomiya wrote:
What messages do you get with this? $ pulseaudio
Invoked as "pulseaudio" by root, it says: "W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified)."
Invoked as "pulseaudio" by a user, its reply is: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied"
If the system did not keep secret the home directory's name, I could do a "chmod 777".
Invoked as "sudo pulseaudio" by a user, it produces these 3 lines: [1] "W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified)." [2] "W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11" [3] "W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11"
Please try as an user, not necessary as a root.
Anyway,
1. please check this works or not;
$ export DISPLAY=:0
Under tcsh, this is equivalent to "setenv DISPLAY :0".
$ pulseaudio
Response: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied" After this failure, I retried it under bash: $ export DISPLAY=:0 $ pulseaudio Again the same error message: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied"
2. if works, goto 3., if not got 5.
Since it did not work, I skipped the steps 3. and 4.
3. $ echo DISPLAY=:0 >> ~/.bashrc $ source ~/.bashrc
after this,
$ pulseaudio
If works, just show the results of;
4.1 $ pacmd list-cards
4.2 $ pacmd list snd
4.3 $ pacmd list-sinks
4.4 $ aplay -L
5. If you still get the D-Bus related error messages; please show the output of this;
$ cat DBUS_SESSION_BUS_ADDRESS
Response: "cat: DBUS_SESSION_BUS_ADDRESS: No such file or directory"
Regards. at 8:80 PM JST.
Regards, at 3:00 PM CEST (GMT+2), Wolfgang
On 2021-06-30 14:59, Wolfgang Mueller wrote:
Response: "cat: DBUS_SESSION_BUS_ADDRESS: No such file or directory"
Masaru is probably asleep right now so it might be time saving to just comment that DBUS_SESSION_BUS_ADDRESS is a env variable. He probably meant: cat $DBUS_SESSION_BUS_ADDRESS but that is also not right as there is a prefix that doesn't work for cat. I suspect he meant: echo $DBUS_SESSION_BUS_ADDRESS -- /bengan
On Wed, 30 Jun 2021 at 15:29:05 +0200, Bengt Gördén wrote:
On 2021-06-30 14:59, Wolfgang Mueller wrote:
Response: "cat: DBUS_SESSION_BUS_ADDRESS: No such file or directory"
Masaru is probably asleep right now so it might be time saving to just comment that DBUS_SESSION_BUS_ADDRESS is a env variable. He probably meant: cat $DBUS_SESSION_BUS_ADDRESS but that is also not right as there is a prefix that doesn't work for cat. I suspect he meant: echo $DBUS_SESSION_BUS_ADDRESS
Thank you, Bengt! Obviously you guessed Masaru's intentions right: $ echo $DBUS_SESSION_BUS_ADDRESS shows this result (without quote marks): "unix:abstract=/tmp/dbus-zWwqQZkBb8,guid=1ed1405d67854060220a091460dc17bc" But there is no file named /tmp/dbus-zWwqQZkBb8 Best regards, Wolfgang
Hello, I'm so sorry. <(_ _)> In the Message; Subject : Re: Sound card configuration problem Message-ID : <95abbdc5-1a22-0e00-1b7e-d2987ac2af14@bag.org> Date & Time: Wed, 30 Jun 2021 15:29:05 +0200 [BG] == Bengt Gördén <bengan@bag.org> has written: BG> On 2021-06-30 14:59, Wolfgang Mueller wrote: BG> > Response: BG> > "cat: DBUS_SESSION_BUS_ADDRESS: No such file or directory" BG> Masaru is probably asleep right now so it might be time saving to just comment BG> that DBUS_SESSION_BUS_ADDRESS is a env variable. He probably meant: cat BG> $DBUS_SESSION_BUS_ADDRESS but that is also not right as there is BG> a prefix that doesn't work for cat. I suspect he meant: echo BG> $DBUS_SESSION_BUS_ADDRESS That's it! Regards, and Good Night. 23:13 PM JST <-- it's midnight for we elderly. (-: --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
Hello, In the Message; Subject : Re: Sound card configuration problem Message-ID : <897d3827-ee42-c600-eba1-7ab487bffeba@ariannuccia.de> Date & Time: Wed, 30 Jun 2021 14:59:39 +0200 [WM] == Wolfgang Mueller <wm@ariannuccia.de> has written: [...] WM> > Anyway, WM> > WM> > 1. please check this works or not; WM> > WM> > $ export DISPLAY=:0 WM> Under tcsh, this is equivalent to "setenv DISPLAY :0". WM> > $ pulseaudio WM> Response: WM> "E: [pulseaudio] core-util.c: Home directory not accessible: WM> Permission denied" It's a root permission issue, there could be 2 cases. 1. permission of home sirectory You can check this by; $ ls -l /home In may case, the output is; drwxr-xr-x 151 masaru users 12288 6月 30 22:31 masaru 2. Another case is the permission of ~/.config/pulse, or ~/.config/pulse/* $ ls -l ~/.config | grep pulse in ma case, the result is; drwx------ 2 masaru users 4096 11月 13 2020 pulse $ ls -l ~/.config/pulse/* | grep root As you see, there doesn't exist the word 'root'. If not like these, please do $ sudo chown -R $USER:$USER $HOME/ and/or $ sudo rm -rf ~/.config/pulse Regrds, 10:46 PM JST(+0800) --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ Think. -- The IBM slogan --
On Wed, 30 Jun 2021 at 15:46:59 +0200, Masaru Nomiya wrote:
Wolfgang Mueller <wm@ariannuccia.de> has written:
On Wed, 30 Jun 2021 13:38:50 +0200, Masaru Nomiya wrote:
Anyway,
1. please check if this works or not; $ export DISPLAY=:0
Under tcsh, this is equivalent to "setenv DISPLAY :0".
$ pulseaudio
Response: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied"
It's a root permission issue, there could be 2 cases.
1. permission of home directory
You can check this by; $ ls -l /home In my case, the output is; drwxr-xr-x 151 masaru users 12288 Jun 30 22:31 masaru
2. Another case is the permission of ~/.config/pulse, or ~/.config/pulse/* $ ls -l ~/.config | grep pulse in my case, the result is; drwx------ 2 masaru users 4096 Jun 13 2020 pulse
$ ls -l ~/.config/pulse/* | grep root
As you see, there doesn't exist the word 'root'. If not like these, please do
$ sudo chown -R $USER:$USER $HOME/
and/or
$ sudo rm -rf ~/.config/pulse
As root I did: $ chmod 777 /home /home/wolfgang /home/wolfgang/.config /home/wolfgang/.config/pulse $ ls -ldG /home /home/wolfgang /home/wolfgang/.config /home/wolfgang/.config/pulse obtaining this result: drwxrwxrwx 10 root 4096 Mar 3 12:52 /home drwxrwxrwx 43 wolfgang 4096 Jun 27 13:15 /home/wolfgang drwxrwxrwx 32 wolfgang 4096 Jun 29 10:09 /home/wolfgang/.config drwxrwxrwx 2 wolfgang 4096 Nov 17 2019 /home/wolfgang/.config/pulse Now, I tried again: $ pulseaudio getting the same result as before: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied" Afterwards I reset the permissions of the directories mentioned above because leaving them open is dangerous. Anyway, it is now clear that the "Home directory" mentioned by the pulseaudio error message is none of them. It is a mystery...
Regards, 10:46 PM JST(+0800)
Here in Germany it is now 7:45 p.m. CEST (+0200), too early for going to bed. Anyway, good night and sweet dreams! Bye, Wolfgang
On Wed, 30 Jun 2021 19:42:54 +0200 Wolfgang Mueller <wm@ariannuccia.de> wrote:
On Wed, 30 Jun 2021 at 15:46:59 +0200, Masaru Nomiya wrote:
Wolfgang Mueller <wm@ariannuccia.de> has written:
On Wed, 30 Jun 2021 13:38:50 +0200, Masaru Nomiya wrote:
Anyway,
1. please check if this works or not; $ export DISPLAY=:0
Under tcsh, this is equivalent to "setenv DISPLAY :0".
$ pulseaudio
Response: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied"
It's a root permission issue, there could be 2 cases.
1. permission of home directory
You can check this by; $ ls -l /home In my case, the output is; drwxr-xr-x 151 masaru users 12288 Jun 30 22:31 masaru
2. Another case is the permission of ~/.config/pulse, or ~/.config/pulse/* $ ls -l ~/.config | grep pulse in my case, the result is; drwx------ 2 masaru users 4096 Jun 13 2020 pulse
$ ls -l ~/.config/pulse/* | grep root
As you see, there doesn't exist the word 'root'. If not like these, please do
$ sudo chown -R $USER:$USER $HOME/
and/or
$ sudo rm -rf ~/.config/pulse
As root I did: $ chmod 777 /home /home/wolfgang /home/wolfgang/.config /home/wolfgang/.config/pulse $ ls -ldG /home /home/wolfgang /home/wolfgang/.config /home/wolfgang/.config/pulse
obtaining this result: drwxrwxrwx 10 root 4096 Mar 3 12:52 /home drwxrwxrwx 43 wolfgang 4096 Jun 27 13:15 /home/wolfgang drwxrwxrwx 32 wolfgang 4096 Jun 29 10:09 /home/wolfgang/.config drwxrwxrwx 2 wolfgang 4096 Nov 17 2019 /home/wolfgang/.config/pulse
Now, I tried again: $ pulseaudio
getting the same result as before: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied"
Afterwards I reset the permissions of the directories mentioned above because leaving them open is dangerous. Anyway, it is now clear that the "Home directory" mentioned by the pulseaudio error message is none of them. It is a mystery...
Regards, 10:46 PM JST(+0800)
Here in Germany it is now 7:45 p.m. CEST (+0200), too early for going to bed. Anyway, good night and sweet dreams!
So try the suggestion I made earlier !!!
Bye, Wolfgang
Hello, In the Message; Subject : Re: Sound card configuration problem Message-ID : <20210630202423.103b9aa9@acer-suse.lan> Date & Time: Wed, 30 Jun 2021 20:24:23 +0100 [DH] == Dave Howorth <dave@howorth.org.uk> has written: [...] WM> > As root I did: WM> > $ chmod 777 /home /home/wolfgang /home/wolfgang/.config WM> > /home/wolfgang/.config/pulse WM> > $ ls -ldG /home /home/wolfgang /home/wolfgang/.config WM> > /home/wolfgang/.config/pulse WM> > WM> > obtaining this result: WM> > drwxrwxrwx 10 root 4096 Mar 3 12:52 /home WM> > drwxrwxrwx 43 wolfgang 4096 Jun 27 13:15 /home/wolfgang WM> > drwxrwxrwx 32 wolfgang 4096 Jun 29 10:09 /home/wolfgang/.config WM> > drwxrwxrwx 2 wolfgang 4096 Nov 17 2019 /home/wolfgang/.config/pulse WM> > WM> > Now, I tried again: WM> > $ pulseaudio WM> > WM> > getting the same result as before: WM> > "E: [pulseaudio] core-util.c: Home directory not accessible: WM> > Permission denied" WM> > WM> > Afterwards I reset the permissions of the directories mentioned WM> > above because leaving them open is dangerous. Anyway, it is now WM> > clear that the "Home directory" mentioned by the pulseaudio error WM> > message is none of them. It is a mystery... WM> > WM> > > Regards, 10:46 PM JST(+0800) WM> > WM> > Here in Germany it is now 7:45 p.m. CEST (+0200), too early for WM> > going to bed. Anyway, good night and sweet dreams! DH> So try the suggestion I made earlier !!! That's it. Before doing so, please check ls -ldG /home/wolfgang/.config/pulse/* Doesn't exist this? -rw-r--r-- 1 root root ... ~/config/pulse/default.pa Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
On Thu, 1 Jul 2021 at 02:01:33 +0200, Masaru Nomiya wrote:
Dave Howorth <dave@howorth.org.uk> has written:
On Wed, 30 Jun 2021 at 19:42:54 +0200, Wolfgang Mueller wrote:
As root I did: $ chmod 777 /home /home/wolfgang /home/wolfgang/.config /home/wolfgang/.config/pulse $ ls -ldG /home /home/wolfgang /home/wolfgang/.config /home/wolfgang/.config/pulse
obtaining this result: drwxrwxrwx 10 root 4096 Mar 3 12:52 /home drwxrwxrwx 43 wolfgang 4096 Jun 27 13:15 /home/wolfgang drwxrwxrwx 32 wolfgang 4096 Jun 29 10:09 /home/wolfgang/.config drwxrwxrwx 2 wolfgang 4096 Nov 17 2019 /home/wolfgang/.config/pulse
Now, I tried again: $ pulseaudio
getting the same result as before: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied"
Afterwards I reset the permissions of the directories mentioned above because leaving them open is dangerous. Anyway, it is now clear that the "Home directory" mentioned by the pulseaudio error message is none of them. It is a mystery... [...]
So try the suggestion I made earlier !!!
That's it.
Before doing so, please check ls -ldG /home/wolfgang/.config/pulse/*
-rw-r--r-- 1 wolfgang 28672 Nov 15 2019 /home/wolfgang/.config/pulse/1d0b2d2b960f4b0ba4d4ced74c4cb6cb-card-database.tdb and a lot of further files, all dating from November 15, 2019, when I configured the sound cards under Leap 15.2. Then they worked, and I fear I will have to downgrade my installation from Leap 15.3 to Leap 15.2 for making them work again.so
Doesn't exist this? -rw-r--r-- 1 root root ... ~/config/pulse/default.pa
No, it does not. I listed /root/.config/pulse, too, getting this results: -rw------- 1 root 24576 Jan 13 17:35 1d0b2d2b960f4b0ba4d4ced74c4cb6cb-card-database.tdb -rw------- 1 root 1 Jan 13 17:35 1d0b2d2b960f4b0ba4d4ced74c4cb6cb-default-sink -rw------- 1 root 1 Jan 13 17:35 1d0b2d2b960f4b0ba4d4ced74c4cb6cb-default-source -rw------- 1 root 8192 Jan 13 17:35 1d0b2d2b960f4b0ba4d4ced74c4cb6cb-device-volumes.tdb lrwxrwxrwx 1 root 23 Jan 13 15:49 1d0b2d2b960f4b0ba4d4ced74c4cb6cb-runtime -> /tmp/pulse-CcctT9RwKSB1 -rw------- 1 root 696 Jan 13 17:35 1d0b2d2b960f4b0ba4d4ced74c4cb6cb-stream-volumes.tdb -rw------- 1 root 24576 Jun 30 12:07 c088ad9ed9df4a62afb10e897491ba6b-card-database.tdb -rw------- 1 root 1 Jun 30 14:25 c088ad9ed9df4a62afb10e897491ba6b-default-sink -rw------- 1 root 1 Jun 30 14:25 c088ad9ed9df4a62afb10e897491ba6b-default-source -rw------- 1 root 8192 Jun 30 12:07 c088ad9ed9df4a62afb10e897491ba6b-device-volumes.tdb lrwxrwxrwx 1 root 23 Jun 28 10:43 c088ad9ed9df4a62afb10e897491ba6b-runtime -> /tmp/pulse-PKdhtXMmr18n -rw------- 1 root 696 Jun 29 17:06 c088ad9ed9df4a62afb10e897491ba6b-stream-volumes.tdb -rw------- 1 root 256 Jan 13 17:35 cookie Having installed Leap 15.3 in June only, I can't explain the January dated files. Anyway, the link target /tmp/pulse-CcctT9RwKSB1 does not exist. The link target /tmp/pulse-PKdhtXMmr18n is an empty directory. Best regards, Wolfgang
On Wed, 30 Jun 2021 12:35:30 +0200 Wolfgang Mueller <wm@ariannuccia.de> wrote:
If the system did not keep secret the home directory's name, I could do a "chmod 777".
Try $ pulseaudio -vvv if you want to discover the secret. Bengt already answered another point.
On Wed, 30 Jun 2021 at 15:56:56 +0200, Dave Howorth wrote:
On Wed, 30 Jun 2021 12:35:30 +0200 Wolfgang Mueller <wm@ariannuccia.de> wrote:
If the system did not keep secret the home directory's name, I could do a "chmod 777".
Try $ pulseaudio -vvv
if you want to discover the secret.
I invoked it as root and as normal user wolfgang, see attachments. Whereas invoked by root, the output seems to be correct, invoking it by user wolfgang produces the well-known error message: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied"
Bengt already answered another point.
I already followed his suggestions. Best regards, Wolfgang
* Wolfgang Mueller <wm@ariannuccia.de> [07-15-21 20:09]:
On Wed, 30 Jun 2021 at 15:56:56 +0200, Dave Howorth wrote:
On Wed, 30 Jun 2021 12:35:30 +0200 Wolfgang Mueller <wm@ariannuccia.de> wrote:
If the system did not keep secret the home directory's name, I could do a "chmod 777".
Try $ pulseaudio -vvv
if you want to discover the secret.
I invoked it as root and as normal user wolfgang, see attachments.
250k deleted Please don't send large files/attachments to everyone on the list. Post them on a file sharing site or host them yourself. Everyone is not interested in your files and many still have slow and/or measured service and you cost them money. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
250k deleted Instead of this comment ( what is 250k these days ?) teach people how to use
Op vrijdag 16 juli 2021 03:29:59 CEST schreef Patrick Shanahan: paste sites......... -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
* Knurpht-openSUSE <knurpht@opensuse.org> [07-15-21 21:38]:
250k deleted Instead of this comment ( what is 250k these days ?) teach people how to use
Op vrijdag 16 juli 2021 03:29:59 CEST schreef Patrick Shanahan: paste sites.........
I believe that is what the comment suggests. Have you made any attempt? Or just don't care about other people. or are you going to ban me again? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 16/07/2021 03.35, Knurpht-openSUSE wrote:
250k deleted Instead of this comment ( what is 250k these days ?) teach people how to use
Op vrijdag 16 juli 2021 03:29:59 CEST schreef Patrick Shanahan: paste sites.........
One of my Internet connections is limited to 10 GB/month. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
On Fri, 16 Jul 2021 at 03:29:59 +0200, Patrick Shanahan wrote:
Wolfgang Mueller <wm@ariannuccia.de> [07-15-21 20:09]: [...]
I invoked it as root and as normal user wolfgang, see attachments.
250k deleted
Please don't send large files/attachments to everyone on the list. Post them on a file sharing site or host them yourself. Everyone is not interested in your files and many still have slow and/or measured service and you cost them money.
You are right: I have to apologize for those large attachments. Maybe you have already observed that in my more recent postings, I use links to my site http://ariannuccia.de/ instead of attachments. By the way, you cite my posting with a wrong date ([07-15-21 20:09], see above), which makes somewhat difficult finding the cited posting. It would have been helpful if you had cited it with the correct date, which was Wed, 30 Jun 2021 at 15:56:56 +0200, corresponding to [06-30-21 13:56] in your notation. Best regards, Wolfgang
On 16/07/2021 10.32, Wolfgang Mueller wrote:
On Fri, 16 Jul 2021 at 03:29:59 +0200, Patrick Shanahan wrote:
Wolfgang Mueller <> [07-15-21 20:09]: [...]
By the way, you cite my posting with a wrong date ([07-15-21 20:09], see above), which makes somewhat difficult finding the cited posting. It would have been helpful if you had cited it with the correct date, which was Wed, 30 Jun 2021 at 15:56:56 +0200, corresponding to [06-30-21 13:56] in your notation.
It is the arrival date. Your post was at mx2.opensuse.org on Thu, 1 Jul 2021 10:12:26 +0000 (UTC), but it arrived to the next hop, mailman3.infra.opensuse.org on Fri, 16 Jul 2021 00:08:50 +0000 (UTC) No idea why. Somehow Patrick has his mail program configured to use the arrival date instead of the sent date, which is strange. Ah! You noticed the delay at the time, and reposted with an explanation: ]> This message is being sent the second time since the original message has been blocked by the list moderator because of exceeding the 200 KB maximum size. I moved the attachments, responsible for the excessive length, to my web site where they may be visited (see below). So, the fault was not yours, but of the system, that does not allow you to cancel a post waiting for moderation. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
* Carlos E. R. <robin.listas@telefonica.net> [07-16-21 06:13]:
On 16/07/2021 10.32, Wolfgang Mueller wrote:
On Fri, 16 Jul 2021 at 03:29:59 +0200, Patrick Shanahan wrote:
Wolfgang Mueller <> [07-15-21 20:09]: [...]
By the way, you cite my posting with a wrong date ([07-15-21 20:09], see above), which makes somewhat difficult finding the cited posting. It would have been helpful if you had cited it with the correct date, which was Wed, 30 Jun 2021 at 15:56:56 +0200, corresponding to [06-30-21 13:56] in your notation.
It is the arrival date.
Your post was at mx2.opensuse.org on Thu, 1 Jul 2021 10:12:26 +0000 (UTC), but it arrived to the next hop, mailman3.infra.opensuse.org on Fri, 16 Jul 2021 00:08:50 +0000 (UTC)
No idea why.
Somehow Patrick has his mail program configured to use the arrival date instead of the sent date, which is strange.
Ah! You noticed the delay at the time, and reposted with an explanation:
]> This message is being sent the second time since the original message has been blocked by the list moderator because of exceeding the 200 KB maximum size. I moved the attachments, responsible for the excessive length, to my web site where they may be visited (see below).
So, the fault was not yours, but of the system, that does not allow you to cancel a post waiting for moderation.
this *should* end this off-subject discussion. I tried to be direct and non-punishing and was broght to task by one of the board who dislikes me and has responded in such on multiple occasions. This is *his* problem and if he gets me banned again, so be it. (Some poeple have no respect). -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On Fri, 16 Jul 2021 08:35:39 -0400 Patrick Shanahan <paka@opensuse.org> wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-16-21 06:13]:
On 16/07/2021 10.32, Wolfgang Mueller wrote:
On Fri, 16 Jul 2021 at 03:29:59 +0200, Patrick Shanahan wrote:
Wolfgang Mueller <> [07-15-21 20:09]: [...]
By the way, you cite my posting with a wrong date ([07-15-21 20:09], see above), which makes somewhat difficult finding the cited posting. It would have been helpful if you had cited it with the correct date, which was Wed, 30 Jun 2021 at 15:56:56 +0200, corresponding to [06-30-21 13:56] in your notation.
It is the arrival date.
Your post was at mx2.opensuse.org on Thu, 1 Jul 2021 10:12:26 +0000 (UTC), but it arrived to the next hop, mailman3.infra.opensuse.org on Fri, 16 Jul 2021 00:08:50 +0000 (UTC)
No idea why.
Somehow Patrick has his mail program configured to use the arrival date instead of the sent date, which is strange.
Ah! You noticed the delay at the time, and reposted with an explanation: ]> This message is being sent the second time since the original message has been blocked by the list moderator because of exceeding the 200 KB maximum size. I moved the attachments, responsible for the excessive length, to my web site where they may be visited (see below).
So, the fault was not yours, but of the system, that does not allow you to cancel a post waiting for moderation.
this *should* end this off-subject discussion. I tried to be direct and non-punishing and was broght to task by one of the board who dislikes me and has responded in such on multiple occasions. This is *his* problem and if he gets me banned again, so be it. (Some poeple have no respect).
Well, no. You were the one that quoted the wrong date. The fault was not Wolfgang's sure, but you should be able to read date stamps. Not that I think being able to read date stamps is essential as a condition of using this mailing list :)
* Dave Howorth <dave@howorth.org.uk> [07-16-21 16:13]:
On Fri, 16 Jul 2021 08:35:39 -0400 Patrick Shanahan <paka@opensuse.org> wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-16-21 06:13]:
On 16/07/2021 10.32, Wolfgang Mueller wrote:
On Fri, 16 Jul 2021 at 03:29:59 +0200, Patrick Shanahan wrote:
Wolfgang Mueller <> [07-15-21 20:09]: [...]
By the way, you cite my posting with a wrong date ([07-15-21 20:09], see above), which makes somewhat difficult finding the cited posting. It would have been helpful if you had cited it with the correct date, which was Wed, 30 Jun 2021 at 15:56:56 +0200, corresponding to [06-30-21 13:56] in your notation.
It is the arrival date.
Your post was at mx2.opensuse.org on Thu, 1 Jul 2021 10:12:26 +0000 (UTC), but it arrived to the next hop, mailman3.infra.opensuse.org on Fri, 16 Jul 2021 00:08:50 +0000 (UTC)
No idea why.
Somehow Patrick has his mail program configured to use the arrival date instead of the sent date, which is strange.
Ah! You noticed the delay at the time, and reposted with an explanation: ]> This message is being sent the second time since the original message has been blocked by the list moderator because of exceeding the 200 KB maximum size. I moved the attachments, responsible for the excessive length, to my web site where they may be visited (see below).
So, the fault was not yours, but of the system, that does not allow you to cancel a post waiting for moderation.
this *should* end this off-subject discussion. I tried to be direct and non-punishing and was broght to task by one of the board who dislikes me and has responded in such on multiple occasions. This is *his* problem and if he gets me banned again, so be it. (Some poeple have no respect).
Well, no. You were the one that quoted the wrong date. The fault was not Wolfgang's sure, but you should be able to read date stamps.
Please explain to me the significance of the subject date stamp. The post contained 255k and was just posted to the list, Received: by wahoo.wahoo.no-ip.org (Postfix, from userid 1000) id 44D10A60C6; Thu, 15 Jul 2021 20:09:55 -0400 (EDT)
Not that I think being able to read date stamps is essential as a condition of using this mailing list :)
the thread now has 42 posts and this is the eighth not dealing with the posted subject. Feel free to respond off-list as I doubt anyone now gives a ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 16/07/2021 23.07, Patrick Shanahan wrote:
* Dave Howorth <dave@howorth.org.uk> [07-16-21 16:13]:
On Fri, 16 Jul 2021 08:35:39 -0400 Patrick Shanahan <paka@opensuse.org> wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-16-21 06:13]:
On 16/07/2021 10.32, Wolfgang Mueller wrote:
On Fri, 16 Jul 2021 at 03:29:59 +0200, Patrick Shanahan wrote:
Wolfgang Mueller <> [07-15-21 20:09]: [...]
By the way, you cite my posting with a wrong date ([07-15-21 20:09], see above), which makes somewhat difficult finding the cited posting. It would have been helpful if you had cited it with the correct date, which was Wed, 30 Jun 2021 at 15:56:56 +0200, corresponding to [06-30-21 13:56] in your notation.
It is the arrival date.
Your post was at mx2.opensuse.org on Thu, 1 Jul 2021 10:12:26 +0000 (UTC), but it arrived to the next hop, mailman3.infra.opensuse.org on Fri, 16 Jul 2021 00:08:50 +0000 (UTC)
No idea why.
Somehow Patrick has his mail program configured to use the arrival date instead of the sent date, which is strange.
Ah! You noticed the delay at the time, and reposted with an explanation: ]> This message is being sent the second time since the original message has been blocked by the list moderator because of exceeding the 200 KB maximum size. I moved the attachments, responsible for the excessive length, to my web site where they may be visited (see below).
So, the fault was not yours, but of the system, that does not allow you to cancel a post waiting for moderation.
this *should* end this off-subject discussion. I tried to be direct and non-punishing and was broght to task by one of the board who dislikes me and has responded in such on multiple occasions. This is *his* problem and if he gets me banned again, so be it. (Some poeple have no respect).
Well, no. You were the one that quoted the wrong date. The fault was not Wolfgang's sure, but you should be able to read date stamps.
Please explain to me the significance of the subject date stamp. The post contained 255k and was just posted to the list,
No, Patrick. The post was held for moderation for about two weeks because it was too big, and released to the list probably by some error of the moderator, instead of deleted. It was not Wolfgang fault. You did not know all this, but maybe you'd have guessed if you had seen the sent date. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
This message is being sent the second time since the original message has been blocked by the list moderator because of exceeding the 200 KB maximum size. I moved the attachments, responsible for the excessive length, to my web site where they may be visited (see below). On Wed, 30 Jun 2021 at 15:56:56 +0200, Dave Howorth wrote:
On Wed, 30 Jun 2021 12:35:30 +0200 Wolfgang Mueller <wm@ariannuccia.de> wrote:
If the system did not keep secret the home directory's name, I could do a "chmod 777".
Try $ pulseaudio -vvv
if you want to discover the secret.
I invoked it as root and as normal user wolfgang, see http://ariannuccia.de/temp/pulseaudio-vvv.root and http://ariannuccia.de/temp/pulseaudio-vvv.wolfgang, respectively. Invoked by root, the output seems to be correct, but invoking it by user wolfgang produces the well-known error message: "E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied"
Bengt already answered another point.
I already followed his suggestions. Best regards, Wolfgang
participants (7)
-
Bengt Gördén -
Carlos E. R. -
Dave Howorth -
Knurpht-openSUSE -
Masaru Nomiya -
Patrick Shanahan -
Wolfgang Mueller