On Tue, 10 Oct 2023 at 13:08:05 +0200, Masaru Nomiya wrote:

Hello,

In the Message;

Subject : Sound under Tumbletweed Message-ID : Date & Time: Tue, 10 Oct 2023 12:24:25 +0200

[WM] == Wolfgang Mueller has written:

WM> On Monday last week, I have installed Tumbletweed with KDE WM> Plasma. In the first two days, the sound worked fine, but WM> then it stopped working and a red diagonal stroke appeared WM> across the speaker icon on the panel. When I click on it, WM> a window pops up, entitled "Audio volume" and saying: "No WM> output or input devices found", but not giving me any chance WM> of specifying such a device.

WM> Since under Tumbletweed, Yast does not contain any possibility WM> of sound configuration, I don't know what to do for making the WM> two sound cards, or at least one of them, work.

pavucontrol (not pavucontrol-qt) will help you a lot.

Having installed pavucontrol, I invoked it. The response was: "Establishing connection to PulseAudio. Please wait..."

Kind Regards & Good Night.

I obviously have to wait for the connection to PulseAudio until tomorrow or even longer. So, good night and sweet dreams! Bye, Wolfgang

On Sat, 14 Oct 2023 at 03:33:56 +0200, Masaru Nomiya wrote:

Hello,

In the Message;

Subject : Re: Sound under Tumbletweed Message-ID : <5fa0be59-8a8b-4752-95dc-82d458d3fd07@ariannuccia.de> Date & Time: Tue, 10 Oct 2023 13:59:13 +0200

[WM] == Wolfgang Mueller has written:

WM> On Tue, 10 Oct 2023 at 13:08:05 +0200, Masaru Nomiya wrote: [...] MN>> pavucontrol (not pavucontrol-qt) will help you a lot.

WM> Having installed pavucontrol, I invoked it. The response was: WM> "Establishing connection to PulseAudio. Please wait..."

Oh, dear.

The pulseaudio daemon isn't running.

Presumably,

$ pulseaudio --check

won't return 0.

If so, please do;

$ pulseaudio -D

First of all, thanks a lot, Masaru! I followed your advises: "pulseaudio --check" does not give any response. Then I tried "pulseaudio -D" as root, getting the reply: "This program is not intended to be run as root (unless --system is specified). E: [pulseaudio] main.c: Daemon startup failed." So, I tried "pulseaudio -D" as a normal user, getting the reply: "E: [pulseaudio] main.c: Daemon startup failed.", keeping secret the reason of this failure. Finally, I tried "pulseaudio -D --system" as root, getting this answer "W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set. W: [pulseaudio] main.c: Running in system mode, but --disallow-module- loading not set. N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode. N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time." But even now, "pulseaudio --check" does not give any response. Bye, Wolfgang

Hello, In the Message; Subject : Re: Sound under Tumbletweed Message-ID : Date & Time: Sat, 14 Oct 2023 09:29:41 -0500 [DCR] == "David C. Rankin" has written: [...] WM> > But even now, "pulseaudio --check" does not give any response. DCR> I've found wireplumber (wpctl status) from pipewire helpful as well, e.g. DCR> $ wpctl status DCR> Which may help point you to an issue with your sound setup from DCR> another starting point. Wolfgang uses pulseaudio system, not pipewire system. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Maddox hopes that empowering users to pick their own algorithms will get them to think more about what’s involved in making them. " -- Bluesky's Custom Algorithms Could Be the Future of Social Media --

Hello, In the Message; Subject : Re: Sound under Tumbletweed Message-ID : <7e62b6de-f88f-4970-be42-0e265bb83e72@vink-slott.dk> Date & Time: Sat, 21 Oct 2023 14:15:03 +0200 [KVS] == Klaus Vink Slott via openSUSE Users has written: KVS> Hi KVS> Den 15.10.2023 kl. 06.11 skrev Masaru Nomiya: KVS> > Wolfgang uses pulseaudio system, not pipewire system. KVS> I don't see Wolfgang stating that in this tread? According to KVS> https://en.opensuse.org/openSUSE:Pipewire KVS> "Since the 20220708 openSUSE Tumbleweed release, new KVS> installations use PipeWire as the default audio engine" KVS> If using pipewire under KDE, I find qpwgraph very good at KVS> illustrating what is goin on. No, I don't think so. First, I installed 20230806 Tumbleweed on my Laptop for testing, and the default engine was pulseaudio. Second, the pipewire system does not have the pulseaudio command, so this is not possible; In the Message; Subject : Re: Sound under Tumbletweed Message-ID : <3545082d-d25a-45ca-9fa4-e6eded713dd3@ariannuccia.de> Date & Time: Sat, 14 Oct 2023 13:56:48 +0200 [WM] == Wolfgang Mueller has written: [...] WM> Then I tried "pulseaudio -D" as root, getting the reply: WM> "This program is not intended to be run as root (unless --system is specified). WM> E: [pulseaudio] main.c: Daemon startup failed." WM> So, I tried "pulseaudio -D" as a normal user, getting the reply: WM> "E: [pulseaudio] main.c: Daemon startup failed.", keeping secret the reason of WM> this failure. WM> Finally, I tried "pulseaudio -D --system" as root, getting this answer WM> "W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set. WM> W: [pulseaudio] main.c: Running in system mode, but --disallow-module- loading WM> not set. WM> N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode. WM> N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle WM> time." WM> But even now, "pulseaudio --check" does not give any response. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Maddox hopes that empowering users to pick their own algorithms will get them to think more about what’s involved in making them. " -- Bluesky's Custom Algorithms Could Be the Future of Social Media --

On Sun, 15 Oct 2023 at 06:07:59 +0200, Masaru Nomiya wrote:

Hello,

Sorry for late reply.

Don't worry. Given the time lag between Japan and Europe, delays are inevitable.

In the Message;

Subject : Re: Sound under Tumbletweed Message-ID : <3545082d-d25a-45ca-9fa4-e6eded713dd3@ariannuccia.de> Date & Time: Sat, 14 Oct 2023 13:56:48 +0200

[WM] == Wolfgang Mueller has written:

[...] MN> > The pulseaudio daemon isn't running. MN> > MN> > Presumably, MN> > MN> > $ pulseaudio --check MN> > MN> > won't return 0. MN> > MN> > If so, please do; MN> > MN> > $ pulseaudio -D

WM> First of all, thanks a lot, Masaru! I followed your advises:

WM> "pulseaudio --check" does not give any response. [...] WM> So, I tried "pulseaudio -D" as a normal user, getting the reply: WM> "E: [pulseaudio] main.c: Daemon startup failed.", keeping secret WM> the reason of this failure. [...]

Please don't do it as root.

Anyway, your system seems to be going haywire.

How about this?

1. $ ps aux | grep pulseaudio

2. kill all pulseaudio processes, just like this;

(ex.) masaru 2473 0.0 0.0 50376 26824 ? S

$ kill -9 2473

There was nothing to be killed, because pulseaudio did not run on my system.

3. rm -rf ~/.config/pulse

This directory contained one file only: ~/.config/pulse/cookie. Anyway, I removed it.

4. $ pulseaudio -v -D

This command produced the response: "E: [pulseaudio] main.c: Daemon startup failed." Bye, Wolfgang