Audacity VS 'locale'?
Audacity is refusing to launch (AGAIN) on both Slowroll AND Tumbleweed, looks like maybe because of 'LOCALE' (AGAIN) ..but why does a freakin' wave editor need 'locale' at all and why do I keep running into locale problems on opensuse (no issues on Artix, Devuan, Slackware, AvLinux)? https://paste.opensuse.org/pastes/d108bcf3f42e
On 2024-03-12 23:31, Ben T. Fender wrote:
Audacity is refusing to launch (AGAIN) on both Slowroll AND Tumbleweed, looks like maybe because of 'LOCALE' (AGAIN) ..but why does a freakin' wave editor need 'locale' at all and why do I keep running into locale problems on opensuse (no issues on Artix, Devuan, Slackware, AvLinux)?
All applications need to read the locale, no matter what they do. They print messages and menus and options. In your case, it appears to be trying "/usr/lib/locale/C.UTF-8/", which does not exist. I have "/usr/lib/locale/C.utf8/" instead. (that's the no-locale locale, by the way). -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Tue, 12 Mar 2024 23:52:41 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-03-12 23:31, Ben T. Fender wrote:
Audacity is refusing to launch (AGAIN) on both Slowroll AND Tumbleweed, looks like maybe because of 'LOCALE' (AGAIN) ..but why does a freakin' wave editor need 'locale' at all and why do I keep running into locale problems on opensuse (no issues on Artix, Devuan, Slackware, AvLinux)?
All applications need to read the locale, no matter what they do. They print messages and menus and options.
In your case, it appears to be trying "/usr/lib/locale/C.UTF-8/", which does not exist. I have "/usr/lib/locale/C.utf8/" instead.
I copied the folder to C.UTF-8, renamed old one C.utf8-was
(that's the no-locale locale, by the way).
/etc/locale-conf had "LANG=en_GB.UTF-8" (or such for Britain) which I sure as puck never put there! Changed to LANG=en_US.UTF-8 so now it's an IDENTIFICATION issue, there's always something screwed up, it's like a *recurring nightmare* and by the time I get it fixed, if at all, I'm too tired for my guitar session openat(AT_FDCWD, "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.utf8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.utf-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.UTF8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = 13 the "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION" file is right there, same file that was in the badly named original folder
On 2024-03-13 00:56, Ben T. Fender wrote:
Tue, 12 Mar 2024 23:52:41 +0100 "Carlos E. R." <> :
On 2024-03-12 23:31, Ben T. Fender wrote:
Audacity is refusing to launch (AGAIN) on both Slowroll AND Tumbleweed, looks like maybe because of 'LOCALE' (AGAIN) ..but why does a freakin' wave editor need 'locale' at all and why do I keep running into locale problems on opensuse (no issues on Artix, Devuan, Slackware, AvLinux)?
All applications need to read the locale, no matter what they do. They print messages and menus and options.
In your case, it appears to be trying "/usr/lib/locale/C.UTF-8/", which does not exist. I have "/usr/lib/locale/C.utf8/" instead.
I copied the folder to C.UTF-8, renamed old one C.utf8-was
That's ugly hack. You should at worst have used symlinks.
(that's the no-locale locale, by the way).
/etc/locale-conf had "LANG=en_GB.UTF-8" (or such for Britain) which I sure as puck never put there! Changed to LANG=en_US.UTF-8
so now it's an IDENTIFICATION issue, there's always something screwed up, it's like a *recurring nightmare* and by the time I get it fixed, if at all, I'm too tired for my guitar session
Well, you are using Factory aka Tumbleweed. Factory is constantly changing by definition. You are expected to cope with the changes yourself.
openat(AT_FDCWD, "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.utf8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.utf-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.UTF8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = 13
the "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION" file is right there, same file that was in the badly named original folder
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Le 13/03/2024 à 04:41, Carlos E. R. a écrit :
Well, you are using Factory aka Tumbleweed. Factory is constantly changing by definition. You are expected to cope with the changes yourself.
I also do and have no problem with audacity :-( jdd -- https://artdagio.fr
Wed, 13 Mar 2024 04:41:25 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-03-13 00:56, Ben T. Fender wrote:
Tue, 12 Mar 2024 23:52:41 +0100 "Carlos E. R." <> :
On 2024-03-12 23:31, Ben T. Fender wrote:
Audacity is refusing to launch (AGAIN) on both Slowroll AND Tumbleweed, looks like maybe because of 'LOCALE' (AGAIN) ..but why does a freakin' wave editor need 'locale' at all and why do I keep running into locale problems on opensuse (no issues on Artix, Devuan, Slackware, AvLinux)?
All applications need to read the locale, no matter what they do. They print messages and menus and options.
In your case, it appears to be trying "/usr/lib/locale/C.UTF-8/", which does not exist. I have "/usr/lib/locale/C.utf8/" instead.
I copied the folder to C.UTF-8, renamed old one C.utf8-was
That's ugly hack.
Now I really don't know where to hide in shame!
You should at worst have used symlinks.
Why? When I have to deal with a file of which I may have to swing two versions I copy both and change one or the other to the required name depending on the state of TS/Resolution. For example I may have /etc/hosts-distro, /etc/hosts-antigoogle and then copy one or the other in as /etc/hosts. It ain't pretty but then neither were some of my girlfriends.
(that's the no-locale locale, by the way).
/etc/locale-conf had "LANG=en_GB.UTF-8" (or such for Britain) which I sure as puck never put there! Changed to LANG=en_US.UTF-8
so now it's an IDENTIFICATION issue, there's always something screwed up, it's like a *recurring nightmare* and by the time I get it fixed, if at all, I'm too tired for my guitar session
Well, you are using Factory aka Tumbleweed. Factory is constantly changing by definition. You are expected to cope with the changes yourself.
Yeh, yeh, I've also read that the only prerequisite for a package to land in a TW repo is for it to have been successfully compiled. But this page seems to be a little more forgiving :-) https://get.opensuse.org/tumbleweed/
openat(AT_FDCWD, "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.utf8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.utf-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/C.UTF8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = 13
the "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION" file is right there, same file that was in the badly named original folder
-- Cheers / Saludos,
Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-03-13 12:25, Ben T. Fender wrote:
Wed, 13 Mar 2024 04:41:25 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-03-13 00:56, Ben T. Fender wrote:
Tue, 12 Mar 2024 23:52:41 +0100 "Carlos E. R." <> :
On 2024-03-12 23:31, Ben T. Fender wrote:
Audacity is refusing to launch (AGAIN) on both Slowroll AND Tumbleweed, looks like maybe because of 'LOCALE' (AGAIN) ..but why does a freakin' wave editor need 'locale' at all and why do I keep running into locale problems on opensuse (no issues on Artix, Devuan, Slackware, AvLinux)?
All applications need to read the locale, no matter what they do. They print messages and menus and options.
In your case, it appears to be trying "/usr/lib/locale/C.UTF-8/", which does not exist. I have "/usr/lib/locale/C.utf8/" instead.
I copied the folder to C.UTF-8, renamed old one C.utf8-was
That's ugly hack.
Now I really don't know where to hide in shame!
You should at worst have used symlinks.
Why? When I have to deal with a file of which I may have to swing two versions I copy both and change one or the other to the required name depending on the state of TS/Resolution. For example I may have /etc/hosts-distro, /etc/hosts-antigoogle and then copy one or the other in as /etc/hosts. It ain't pretty but then neither were some of my girlfriends.
This is not the same case, of having two configs. There a single configuration, identical, just with a different name. You are trying to fool an application that tries to find the wrong file name. The normal hack is to have a symlink: /usr/lib/locale/C.utf8/ → /usr/lib/locale/C.UTF-8/ It uses just a few bytes, when listing the directory you see the change, and if there is an update, the copy is also updated. You can do similarly with hosts; One day you have: /etc/hosts → /etc/hosts-distro and another day you have: /etc/hosts → /etc/hosts-antigoogle Just by doing a listing you know in which configuration state is your machine, and updates go to the correct version file.
(that's the no-locale locale, by the way).
/etc/locale-conf had "LANG=en_GB.UTF-8" (or such for Britain) which I sure as puck never put there! Changed to LANG=en_US.UTF-8
so now it's an IDENTIFICATION issue, there's always something screwed up, it's like a *recurring nightmare* and by the time I get it fixed, if at all, I'm too tired for my guitar session
Well, you are using Factory aka Tumbleweed. Factory is constantly changing by definition. You are expected to cope with the changes yourself.
Yeh, yeh, I've also read that the only prerequisite for a package to land in a TW repo is for it to have been successfully compiled. But this page seems to be a little more forgiving :-)
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Audacity VS 'locale'? Message-ID : <20240312183138.f471bce69e7077d62577251e@trixtar.org> Date & Time: Tue, 12 Mar 2024 18:31:38 -0400 [BTF] == "Ben T. Fender" <slowroller@trixtar.org> has written: BTF> Audacity is refusing to launch (AGAIN) on both BTF> Slowroll AND Tumbleweed, looks like maybe because BTF> of 'LOCALE' (AGAIN) ..but why does a freakin' wave BTF> editor need 'locale' at all and why do I keep BTF> running into locale problems on opensuse (no issues BTF> on Artix, Devuan, Slackware, AvLinux)? BTF> https://paste.opensuse.org/pastes/d108bcf3f42e It is not a locale issue. How about installing ladspa-caps? Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
Wed, 13 Mar 2024 16:40:11 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Audacity VS 'locale'? Message-ID : <20240312183138.f471bce69e7077d62577251e@trixtar.org> Date & Time: Tue, 12 Mar 2024 18:31:38 -0400
[BTF] == "Ben T. Fender" <slowroller@trixtar.org> has written:
BTF> Audacity is refusing to launch (AGAIN) on both BTF> Slowroll AND Tumbleweed, looks like maybe because BTF> of 'LOCALE' (AGAIN) ..but why does a freakin' wave BTF> editor need 'locale' at all and why do I keep BTF> running into locale problems on opensuse (no issues BTF> on Artix, Devuan, Slackware, AvLinux)?
BTF> https://paste.opensuse.org/pastes/d108bcf3f42e
It is not a locale issue.
How about installing ladspa-caps?
Thanks, it IS installed but the problem is somewhere else. -- Interests: dogs, music/guitar, nature, animals, trees, diesels, tractors, theology, biology, economy, bacteriae skunks, and humanity ..in that order.
Hello, In the Message; Subject : Re: Audacity VS 'locale'? Message-ID : <20240313073052.91bf564bfc3f94a46917aa56@trixtar.org> Date & Time: Wed, 13 Mar 2024 07:30:52 -0400 [BTF] == "Ben T. Fender" <slowroller@trixtar.org> has written: [...] BTF>>> https://paste.opensuse.org/pastes/d108bcf3f42e MN> > It is not a locale issue. MN> > How about installing ladspa-caps? BTF> Thanks, it IS installed but the problem is somewhere else. Please show the results of; $ rpm -qa *ladspa* But, it's time to go to bed for me. Kind Regards & Good Night. --- ┏━━┓彡 野宮 賢 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 --
* Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-13-24 03:41]:
Hello,
In the Message;
Subject : Audacity VS 'locale'? Message-ID : <20240312183138.f471bce69e7077d62577251e@trixtar.org> Date & Time: Tue, 12 Mar 2024 18:31:38 -0400
[BTF] == "Ben T. Fender" <slowroller@trixtar.org> has written:
BTF> Audacity is refusing to launch (AGAIN) on both BTF> Slowroll AND Tumbleweed, looks like maybe because BTF> of 'LOCALE' (AGAIN) ..but why does a freakin' wave BTF> editor need 'locale' at all and why do I keep BTF> running into locale problems on opensuse (no issues BTF> on Artix, Devuan, Slackware, AvLinux)?
BTF> https://paste.opensuse.org/pastes/d108bcf3f42e
It is not a locale issue.
How about installing ladspa-caps?
fwiw: I have Audacity installed in Tw and do not have ladspa-caps or any *ladspa* app and audacity runs fine. -- (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 oftc
Hello, In the Message; Subject : Re: Audacity VS 'locale'? Message-ID : <20240313124519.GY7115@wahoo.no-ip.org> Date & Time: Wed, 13 Mar 2024 08:45:19 -0400 [PS] == Patrick Shanahan <paka@opensuse.org> has written: PS> * Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-13-24 03:41]: [...] MN> > It is not a locale issue. MN> > MN> > How about installing ladspa-caps? PS> fwiw: I have Audacity installed in Tw and do not have ladspa-caps or any PS> *ladspa* app and audacity runs fine. Do you? In the log shown by Ben, this is where the error begins; [...] openat(AT_FDCWD, "/lib64/glibc-hwcaps/x86-64-v2/caps.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [...] Here, caps.so is the ladspa-caps file. In fact, Audacity has included ladspa since Version 2.0.6; * (Linux) Self-compiled builds of Audacity now search for system LADSPA effects in /usr/lib/ladspa. And, this is the current state; * The following plugin formats are now realtime capable: VST3, LV2, LADSPA, Audio Units. ( <-- from 3.2.0) But I am suspicious of this ladspa. In other words, on my Tumbleweed, when I start up audacity (openSUSE's and my own build's), I get an error messasge 'error initializing audio', and even after startup, when I try to play a music file, I get a message to change the sampling rate, and when I change the sampling rate, there is no change in the situation. I will uninstall ladspa and see how it works when I have more time. Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say." -- Google Splits Up a Key AI Ethics Watchdog --
Thu, 14 Mar 2024 13:16:29 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240313124519.GY7115@wahoo.no-ip.org> Date & Time: Wed, 13 Mar 2024 08:45:19 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
PS> * Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-13-24 03:41]: [...] MN> > It is not a locale issue. MN> > MN> > How about installing ladspa-caps?
PS> fwiw: I have Audacity installed in Tw and do not have ladspa-caps or any PS> *ladspa* app and audacity runs fine.
Do you?
In the log shown by Ben, this is where the error begins;
[...] openat(AT_FDCWD, "/lib64/glibc-hwcaps/x86-64-v2/caps.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [...]
On my TW ladspa is installed, there are 3 directories under /lib64/glibc-hwcaps/ x86-64_v2 ..empty x86-64_v3 .. contains NO caps.so x86-64_v4 ..empty this doesn't change after also installing: ladspa-32bit ladspa-lsp-plugins ladspa-rnnoise liblrdf2-32bit lv2-swh-plugins rubberband-ladspa-32bit
Hello, In the Message; Subject : Re: Audacity VS 'locale'? Message-ID : <20240314064950.8a5ed2a6a0c15f475aa4da91@trixtar.org> Date & Time: Thu, 14 Mar 2024 06:49:50 -0400 "Ben T. Fender" <slowroller@trixtar.org> has written:
Thu, 14 Mar 2024 13:16:29 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> : [...] MN> > In the log shown by Ben, this is where the error begins;
MN> > [...] MN> > openat(AT_FDCWD, "/lib64/glibc-hwcaps/x86-64-v2/caps.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) MN> > [...]
On my TW ladspa is installed, there are 3 directories under /lib64/glibc-hwcaps/
x86-64_v2 ..empty x86-64_v3 .. contains NO caps.so x86-64_v4 ..empty
this doesn't change after also installing: ladspa-32bit ladspa-lsp-plugins ladspa-rnnoise liblrdf2-32bit lv2-swh-plugins rubberband-ladspa-32bit
Yes, caps.so is /usr/lib64/ladspa/caps.so. But your and my problems are not related to ladspa. In other words, uninstalling all ladspa-related files does not change the situation. Since Patrik's TW has no problem, you should try installing of TW snapshop is a simple solution? Just one thing, can you tell me from what update the problem started? Kind Regards & Good Night. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
Thu, 14 Mar 2024 20:43:05 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240314064950.8a5ed2a6a0c15f475aa4da91@trixtar.org> Date & Time: Thu, 14 Mar 2024 06:49:50 -0400
"Ben T. Fender" <slowroller@trixtar.org> has written:
Thu, 14 Mar 2024 13:16:29 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> : [...] MN> > In the log shown by Ben, this is where the error begins;
MN> > [...] MN> > openat(AT_FDCWD, "/lib64/glibc-hwcaps/x86-64-v2/caps.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) MN> > [...]
On my TW ladspa is installed, there are 3 directories under /lib64/glibc-hwcaps/
x86-64_v2 ..empty x86-64_v3 .. contains NO caps.so x86-64_v4 ..empty
this doesn't change after also installing: ladspa-32bit ladspa-lsp-plugins ladspa-rnnoise liblrdf2-32bit lv2-swh-plugins rubberband-ladspa-32bit
Yes, caps.so is /usr/lib64/ladspa/caps.so.
But your and my problems are not related to ladspa. In other words, uninstalling all ladspa-related files does not change the situation.
Since Patrik's TW has no problem, you should try installing of TW snapshop is a simple solution?
Just one thing, can you tell me from what update the problem started?
No, I didn't log it cause I was anything but surprised :-( What's more, for the first time (because I'm now using what are actually two versions of TW instead of Leap & TW) both of them have the Failing-Audacity problem and since I'm on one or the other I hardly ever know which one I'm working with at the moment. A (now late) friend of mine had an antique auto colection of about a dozen very rare rides. He would sometimes drive one to work because they 'needed to get oiled'. When I asked him how he picks one he said "the first one I manage to start". I have 6 or 7 distros installed precisely to make sure that when I sit down for a guitar session at least one of them will have all it's freakin' sound and music act together; well today Devuan is *the ONLY one* of the lot! I'm about to buy me a Mac and be done with Linux.
On 2024-03-14 16:10, Ben T. Fender wrote:
Thu, 14 Mar 2024 20:43:05 +0900 Masaru Nomiya <...> :
Just one thing, can you tell me from what update the problem started?
No, I didn't log it cause I was anything but surprised :-(
What's more, for the first time (because I'm now using what are actually two versions of TW instead of Leap & TW) both of them have the Failing-Audacity problem and since I'm on one or the other I hardly ever know which one I'm working with at the moment.
A (now late) friend of mine had an antique auto colection of about a dozen very rare rides. He would sometimes drive one to work because they 'needed to get oiled'. When I asked him how he picks one he said "the first one I manage to start". I have 6 or 7 distros installed precisely to make sure that when I sit down for a guitar session at least one of them will have all it's freakin' sound and music act together; well today Devuan is *the ONLY one* of the lot! I'm about to buy me a Mac and be done with Linux.
Why don't you get an install that works with your music gadgets, and stop upgrading it? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Thu, 14 Mar 2024 16:17:22 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-03-14 16:10, Ben T. Fender wrote:
Thu, 14 Mar 2024 20:43:05 +0900 Masaru Nomiya <...> :
Just one thing, can you tell me from what update the problem started?
No, I didn't log it cause I was anything but surprised :-(
What's more, for the first time (because I'm now using what are actually two versions of TW instead of Leap & TW) both of them have the Failing-Audacity problem and since I'm on one or the other I hardly ever know which one I'm working with at the moment.
A (now late) friend of mine had an antique auto colection of about a dozen very rare rides. He would sometimes drive one to work because they 'needed to get oiled'. When I asked him how he picks one he said "the first one I manage to start". I have 6 or 7 distros installed precisely to make sure that when I sit down for a guitar session at least one of them will have all it's freakin' sound and music act together; well today Devuan is *the ONLY one* of the lot! I'm about to buy me a Mac and be done with Linux.
Why don't you get an install that works with your music gadgets, and stop upgrading it?
good question, a bunch of freshies, all tweaked once and working, and an update embargo!
On 3/14/24 08:43, Ben T. Fender wrote:
Thu, 14 Mar 2024 16:17:22 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-03-14 16:10, Ben T. Fender wrote:
Thu, 14 Mar 2024 20:43:05 +0900 Masaru Nomiya <...> :
Just one thing, can you tell me from what update the problem started? No, I didn't log it cause I was anything but surprised :-(
What's more, for the first time (because I'm now using what are actually two versions of TW instead of Leap & TW) both of them have the Failing-Audacity problem and since I'm on one or the other I hardly ever know which one I'm working with at the moment.
A (now late) friend of mine had an antique auto colection of about a dozen very rare rides. He would sometimes drive one to work because they 'needed to get oiled'. When I asked him how he picks one he said "the first one I manage to start". I have 6 or 7 distros installed precisely to make sure that when I sit down for a guitar session at least one of them will have all it's freakin' sound and music act together; well today Devuan is *the ONLY one* of the lot! I'm about to buy me a Mac and be done with Linux. Why don't you get an install that works with your music gadgets, and stop upgrading it?
good question, a bunch of freshies, all tweaked once and working, and an update embargo!
Of course, you should do this only with a machine that's isolated from the Internet after you set it up. Otherwise you could become vulnerable to malware. We all like to think that Linux is impervious to malware, but that's only wishful thinking. When I first started with SuSE in 1998 I had my home machine running SuSE 5.2 and I didn't start the firewall because the docs were in German. Alas, I got zero-click compromised via a mountd vulnerability. I noticed it right away so no damage was done, but I learned a valuable lesson. Regards, Lew
Thu, 14 Mar 2024 16:19:02 -0700 Lew Wolfgang <wolfgang@sweet-haven.com> :
On 3/14/24 08:43, Ben T. Fender wrote:
Thu, 14 Mar 2024 16:17:22 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-03-14 16:10, Ben T. Fender wrote:
Thu, 14 Mar 2024 20:43:05 +0900 Masaru Nomiya <...> :
Just one thing, can you tell me from what update the problem started? No, I didn't log it cause I was anything but surprised :-(
What's more, for the first time (because I'm now using what are actually two versions of TW instead of Leap & TW) both of them have the Failing-Audacity problem and since I'm on one or the other I hardly ever know which one I'm working with at the moment.
A (now late) friend of mine had an antique auto colection of about a dozen very rare rides. He would sometimes drive one to work because they 'needed to get oiled'. When I asked him how he picks one he said "the first one I manage to start". I have 6 or 7 distros installed precisely to make sure that when I sit down for a guitar session at least one of them will have all it's freakin' sound and music act together; well today Devuan is *the ONLY one* of the lot! I'm about to buy me a Mac and be done with Linux. Why don't you get an install that works with your music gadgets, and stop upgrading it?
good question, a bunch of freshies, all tweaked once and working, and an update embargo!
Of course, you should do this only with a machine that's isolated from the Internet after you set it up. Otherwise you could become vulnerable to malware. We all like to think that Linux is impervious to malware, but that's only wishful thinking. When I first started with SuSE in 1998 I had my home machine running SuSE 5.2 and I didn't start the firewall because the docs were in German. Alas, I got zero-click compromised via a mountd vulnerability. I noticed it right away so no damage was done, but I learned a valuable lesson.
With ssd's and the time to recover a reasonably sized partition from a dd backup falling through the floor I'm actually thinking of starting every session with dd, and minutes later booting a sterile copy of the original installation (sterile meaning never before connected to anything). Not so much for so-called security as for my required apps all working, my interest in security is academic and mostly a question of principle, not of need.
On 2024-03-14 11:49, Ben T. Fender wrote:
Thu, 14 Mar 2024 13:16:29 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240313124519.GY7115@wahoo.no-ip.org> Date & Time: Wed, 13 Mar 2024 08:45:19 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
PS> * Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-13-24 03:41]: [...] MN> > It is not a locale issue. MN> > MN> > How about installing ladspa-caps?
PS> fwiw: I have Audacity installed in Tw and do not have ladspa-caps or any PS> *ladspa* app and audacity runs fine.
Do you?
In the log shown by Ben, this is where the error begins;
[...] openat(AT_FDCWD, "/lib64/glibc-hwcaps/x86-64-v2/caps.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [...]
On my TW ladspa is installed, there are 3 directories under /lib64/glibc-hwcaps/
x86-64_v2 ..empty x86-64_v3 .. contains NO caps.so x86-64_v4 ..empty
this doesn't change after also installing: ladspa-32bit ladspa-lsp-plugins ladspa-rnnoise liblrdf2-32bit lv2-swh-plugins rubberband-ladspa-32bit
On another post, you said: ]> openat(AT_FDCWD, ]> "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ]> ENOENT (No such file or directory) openat(AT_FDCWD, ]> "/usr/lib/locale/C.utf8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ]> ENOENT (No such file or directory) openat(AT_FDCWD, ]> "/usr/lib/locale/C/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT ]> (No such file or directory) openat(AT_FDCWD, ]> "/usr/lib/locale/C.utf-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ]> ENOENT (No such file or directory) openat(AT_FDCWD, ]> "/usr/lib/locale/C.UTF8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = 13 ]> ]> the "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION" file is right there, ]> same file that was in the badly named original folder Do we have a situation that files that are in fact present are not found? :-? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Thu, 14 Mar 2024 14:11:40 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-03-14 11:49, Ben T. Fender wrote:
Thu, 14 Mar 2024 13:16:29 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240313124519.GY7115@wahoo.no-ip.org> Date & Time: Wed, 13 Mar 2024 08:45:19 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
PS> * Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-13-24 03:41]: [...] MN> > It is not a locale issue. MN> > MN> > How about installing ladspa-caps?
PS> fwiw: I have Audacity installed in Tw and do not have ladspa-caps or any PS> *ladspa* app and audacity runs fine.
Do you?
In the log shown by Ben, this is where the error begins;
[...] openat(AT_FDCWD, "/lib64/glibc-hwcaps/x86-64-v2/caps.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [...]
On my TW ladspa is installed, there are 3 directories under /lib64/glibc-hwcaps/
x86-64_v2 ..empty x86-64_v3 .. contains NO caps.so x86-64_v4 ..empty
this doesn't change after also installing: ladspa-32bit ladspa-lsp-plugins ladspa-rnnoise liblrdf2-32bit lv2-swh-plugins rubberband-ladspa-32bit
On another post, you said:
]> openat(AT_FDCWD, ]> "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ]> ENOENT (No such file or directory) openat(AT_FDCWD, ]> "/usr/lib/locale/C.utf8/LC_IDENTIFICATION", O_RDONLY| O_CLOEXEC) = -1 ]> ENOENT (No such file or directory) openat(AT_FDCWD, ]> "/usr/lib/locale/C/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT ]> (No such file or directory) openat(AT_FDCWD, ]> "/usr/lib/locale/C.utf-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ]> ENOENT (No such file or directory) openat(AT_FDCWD, ]> "/usr/lib/locale/C.UTF8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = 13 ]> ]> the "/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION" file is right there, ]> same file that was in the badly named original folder
Do we have a situation that files that are in fact present are not found?
:-?
Yeh, in this case because the file is definitely there. But THIS is a locale problem that I can't seem to be able get rid of and which is *either persistant or recurrent* independant of Audacity. The other one with ladpsa is in fact a missing file (see my other reply). BOTH Audacity and Locale issues of one sort or another are on-and-off plagues since Adam and Eve. I'm sure I could do a fresh install and Audacity would work just fine, but only for a finite number of updates after which it would start failing again. Since I also tried the flatpack version of Audacity and it failed too it seems that the problem either has nothing to do with Audacity or the flatpack is also a few bricks short of a load. (?) Suse seem to have their share of problems with sound stuff, but even AvLinux and 'buntu-Studio do and those are dedicated 'studio' distros. It was Leap-14.5 or 15.0 that (ONCE!) had it all together but that was a mistake that wasn't supposed to happen. My XONAR card has 1/4" jacks and that version of Leap made it possible to hear my guitar plugged into the card without ANY other intervention, which is the way it SHOULD be, I mean if I plug something in it's because I want to hear the pucking thing! But some update took care of THAT 'irregularity' and it hasn't happened since :-)
Hello, I'M NOT A SPAMMER! BTW, I don't have gray brain cells, but I thought of myself as Poirot; Hint 1. I was curious about this email; Subject : Lost all multimedia playing Message-ID : <49402d2b-a192-43de-904e-d8a351329d8e@chem.u-szeged.hu> Date & Time: Sun, 10 Mar 2024 14:55:24 +0100 Hint 2. When I saw the above email and ran $ pactl info, it returned the following error message that the situation was not normal; Connection failure: Connection refused pa_context_connect() failed: Connection refused Hint 3. Patrick's message; In the Message; Subject : Re: Audacity VS 'locale'? Message-ID : <20240313124519.GY7115@wahoo.no-ip.org> Date & Time: Wed, 13 Mar 2024 08:45:19 -0400 [PS] == Patrick Shanahan <paka@opensuse.org> has written: [...] PS> fwiw: I have Audacity installed in Tw and do not have ladspa-caps or any PS> *ladspa* app and audacity runs fine. Maybe Patrick is not using pipewire?, I thought to myself. So, I replaced pipewire system to pulseaudio system. BINGO〜! Audacity works flawlessly like a charm! Many thanks, Patrick. In short, there is a bug in the current pipewire. Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "A bachelor’s degree still holds prestige as a ticket to the middle class, but its value has received increasing scrutiny. In the last several years, rising tuition and student loan debt have led more Americans to reconsider an investment in postsecondary education." -- Washington Post --
Fri, 15 Mar 2024 20:47:27 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
I'M NOT A SPAMMER!
BTW, I don't have gray brain cells, but I thought of myself as Poirot;
Hint 1. I was curious about this email;
Subject : Lost all multimedia playing Message-ID : <49402d2b-a192-43de-904e-d8a351329d8e@chem.u-szeged.hu> Date & Time: Sun, 10 Mar 2024 14:55:24 +0100
Hint 2. When I saw the above email and ran $ pactl info, it returned the following error message that the situation was not normal;
Connection failure: Connection refused pa_context_connect() failed: Connection refused
Hint 3. Patrick's message;
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240313124519.GY7115@wahoo.no-ip.org> Date & Time: Wed, 13 Mar 2024 08:45:19 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
[...] PS> fwiw: I have Audacity installed in Tw and do not have ladspa-caps or any PS> *ladspa* app and audacity runs fine.
Maybe Patrick is not using pipewire?, I thought to myself.
So, I replaced pipewire system to pulseaudio system.
BINGO～!
Audacity works flawlessly like a charm!
Many thanks, Patrick.
In short, there is a bug in the current pipewire.
That could be, and nice work inspector Clouseau and good for you but in my case it's still no cigar. I killed pipewire and reinstalled pulse but still get exactly the same audacity errors as before (I won't bother people with a repost of trace).
* Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-15-24 07:48]:
Hello,
I'M NOT A SPAMMER!
BTW, I don't have gray brain cells, but I thought of myself as Poirot;
Hint 1. I was curious about this email;
Subject : Lost all multimedia playing Message-ID : <49402d2b-a192-43de-904e-d8a351329d8e@chem.u-szeged.hu> Date & Time: Sun, 10 Mar 2024 14:55:24 +0100
Hint 2. When I saw the above email and ran $ pactl info, it returned the following error message that the situation was not normal;
Connection failure: Connection refused pa_context_connect() failed: Connection refused
Hint 3. Patrick's message;
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240313124519.GY7115@wahoo.no-ip.org> Date & Time: Wed, 13 Mar 2024 08:45:19 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
[...] PS> fwiw: I have Audacity installed in Tw and do not have ladspa-caps or any PS> *ladspa* app and audacity runs fine.
Maybe Patrick is not using pipewire?, I thought to myself.
So, I replaced pipewire system to pulseaudio system.
BINGO〜!
Audacity works flawlessly like a charm!
Many thanks, Patrick.
In short, there is a bug in the current pipewire.
:)
which pipewire /usr/bin/pipewire
rpm -qa *pipewire* libpipewire-0_3-0-1.0.4-1.1.x86_64 kpipewire6-imports-6.0.1-1.1.x86_64 pipewire-libjack-0_3-1.0.4-1.1.x86_64 pipewire-spa-tools-1.0.4-1.1.x86_64 pipewire-pulseaudio-1.0.4-1.1.x86_64 pipewire-aptx-1.0.1-1699.1.pm.1.x86_64 pipewire-modules-0_3-1.0.4-1.1.x86_64 gstreamer-plugin-pipewire-1.0.4-1.1.x86_64 pipewire-alsa-1.0.4-1.1.x86_64 kpipewire-imports-5.27.10-1.3.x86_64 pipewire-spa-plugins-0_2-1.0.4-1.1.x86_64 pipewire-tools-1.0.4-1.1.x86_64 pipewire-1.0.4-1.1.x86_64
rpm -qa *pulseaudio* pulseaudio-bash-completion-17.0-4.1.x86_64 pipewire-pulseaudio-1.0.4-1.1.x86_64 pulseaudio-utils-17.0-4.1.x86_64 pulseaudio-setup-17.0-4.1.x86_64 I do utilize pipewire :) -- (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 oftc
Hello, I've been struggled, but no avail. I can't figure out the cause. In the Message; Subject : Re: Audacity VS 'locale'? Message-ID : <20240315172443.GI7115@wahoo.no-ip.org> Date & Time: Fri, 15 Mar 2024 13:24:43 -0400 [PS] == Patrick Shanahan <paka@opensuse.org> has written: [...] PS> > In short, there is a bug in the current pipewire. PS> :) Ask google. She shows many you bug reports. PS> > which pipewire PS> /usr/bin/pipewire PS> > rpm -qa *pipewire* [...] PS> pulseaudio-setup-17.0-4.1.x86_64 PS> I do utilize pipewire :) On second thought, I reverted back to the pulseaudio system and re-installed the pipewire system to try to find the cause, and the problem reappeared. It turns out that pipewire is causing the problem with the use of pulse, and $ pactl info is the canary of this issue. Many users are suffering from the $ pactl info error, but no solution has been provided. Maybe the audacity developers know this. I mean, they are developing with the latest wxWidgets, etc., but not pipewire, which kodi, audacious, mpd, etc., are actively using. I'll leave this problem for a while. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
Sun, 17 Mar 2024 17:36:07 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
On second thought, I reverted back to the pulseaudio system and re-installed the pipewire system to try to find the cause, and the problem reappeared.
It turns out that pipewire is causing the problem with the use of pulse, and $ pactl info is the canary of this issue.
Many users are suffering from the $ pactl info error, but no solution has been provided.
Maybe the audacity developers know this. I mean, they are developing with the latest wxWidgets, etc., but not pipewire, which kodi, audacious, mpd, etc., are actively using.
I'll leave this problem for a while.
I won't. Remains to test it on MicroOS; I installed mOS last night but the boot failed (other topic).
* Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-17-24 04:37]:
Hello,
I've been struggled, but no avail.
I can't figure out the cause.
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240315172443.GI7115@wahoo.no-ip.org> Date & Time: Fri, 15 Mar 2024 13:24:43 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
[...] PS> > In short, there is a bug in the current pipewire.
wrong attribution, nowhere did is say there is a bug in the current pipewire
PS> :)
Ask google.
She shows many you bug reports.
PS> > which pipewire PS> /usr/bin/pipewire
PS> > rpm -qa *pipewire* [...] PS> pulseaudio-setup-17.0-4.1.x86_64
PS> I do utilize pipewire :)
On second thought, I reverted back to the pulseaudio system and re-installed the pipewire system to try to find the cause, and the problem reappeared.
It turns out that pipewire is causing the problem with the use of pulse, and $ pactl info is the canary of this issue.
I have pulseaudio-utils-17.0-4.1.x86_64 installed which contains pactl
pactl info Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 233 Tile Size: 65472 User Name: paka Host Name: crash.wahoo.no-ip.org Server Name: PulseAudio (on PipeWire 1.0.4) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 48000Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-0000_00_1b.0.analog-stereo Default Source: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor Cookie: d231:7b68
Many users are suffering from the $ pactl info error, but no solution has been provided.
I do not know this to be correct.
Maybe the audacity developers know this. I mean, they are developing with the latest wxWidgets, etc., but not pipewire, which kodi, audacious, mpd, etc., are actively using.
I have audacity performing correctly for me on six very different varied architect and aged boxes with very similar setups all with pipewire. -- (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 oftc
Sun, 17 Mar 2024 09:46:45 -0400 Patrick Shanahan <paka@opensuse.org> :
* Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-17-24 04:37]:
Hello,
I've been struggled, but no avail.
I can't figure out the cause.
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240315172443.GI7115@wahoo.no-ip.org> Date & Time: Fri, 15 Mar 2024 13:24:43 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
[...] PS> > In short, there is a bug in the current pipewire.
wrong attribution, nowhere did is say there is a bug in the current pipewire
PS> :)
Ask google.
She shows many you bug reports.
PS> > which pipewire PS> /usr/bin/pipewire
PS> > rpm -qa *pipewire* [...] PS> pulseaudio-setup-17.0-4.1.x86_64
PS> I do utilize pipewire :)
On second thought, I reverted back to the pulseaudio system and re-installed the pipewire system to try to find the cause, and the problem reappeared.
It turns out that pipewire is causing the problem with the use of pulse, and $ pactl info is the canary of this issue.
I have pulseaudio-utils-17.0-4.1.x86_64 installed which contains pactl
pactl info Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 233 Tile Size: 65472 User Name: paka Host Name: crash.wahoo.no-ip.org Server Name: PulseAudio (on PipeWire 1.0.4) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 48000Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-0000_00_1b.0.analog-stereo Default Source: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor Cookie: d231:7b68
Many users are suffering from the $ pactl info error, but no solution has been provided.
I do not know this to be correct.
Maybe the audacity developers know this. I mean, they are developing with the latest wxWidgets, etc., but not pipewire, which kodi, audacious, mpd, etc., are actively using.
I have audacity performing correctly for me on six very different varied architect and aged boxes with very similar setups all with pipewire.
It's the 'mix' that seems to be a problem but my qualifications don't suffice to deal with it, I've tried with both as well as with and without either ..NO audacity (except on my Devuan system) message-id on alt.os.linux <l5oeffF9et1U1@mid.individual.net>
On 2024-03-17 14:46, Patrick Shanahan wrote:
* Masaru Nomiya <nomiya@lake.dti.ne.jp> [03-17-24 04:37]:
Hello,
I've been struggled, but no avail.
I can't figure out the cause.
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <20240315172443.GI7115@wahoo.no-ip.org> Date & Time: Fri, 15 Mar 2024 13:24:43 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
[...] PS> > In short, there is a bug in the current pipewire.
wrong attribution, nowhere did is say there is a bug in the current pipewire
It is not attributed to you. There is a double ">>", albeit with somewhat broken and unusual formatting. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: Audacity VS 'locale'? Message-ID : <3d1390f8-7bc5-404d-b981-21e2e6b51086@telefonica.net> Date & Time: Sun, 17 Mar 2024 16:22:46 +0100 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: CER> On 2024-03-17 14:46, Patrick Shanahan wrote: [...] MN>>> In short, there is a bug in the current pipewire. PS>> wrong attribution, nowhere did is say there is a bug in the current PS>> pipewire CER> It is not attributed to you. There is a double ">>", albeit with CER> somewhat broken and unusual formatting. Thanks, Carlos. I'm sorry if I misled you, Patrick. Anyway, today I found out two things. The Audacity problem was caused by the portaudio library of my own build being too new, and I solved it by replacing it with the one provided by openSUSE. Of course, this has nothing to do with pipewire. However, it has been reported that there can be problems between pipewire and Audacity, and I suspect that Ben's problem is along these lines and is related to the $ pactl info returning an error. I also had a question about KDE theming, so I checked it out with installing Tumbleweed on my laptop. It turns out that $ pactl info should return results like Patrick showed, and that the absence of /run/user/1000/pulse/native on my PC is an anomaly. I thiink Ben is the same? By the way, there are pid files under /run/user/1000/pulse as well as native file, and I was surprised to find out that they are from pipewire-pulse by checking with # ps ax | grep pid's value. In my case, pipewire installation requires pipewire-pulse installation, but when installed, pipewire-pulse.service is automatically masked and disabled. So I followed Patrick's suggestion and re-installed pipewire and pulseaudio. Sure enough, it installed fine, but $ pactl info still returns an error.... (_ _? It's late, so I'll continue tomorrow. Best Regards & Good Night. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
Mon, 18 Mar 2024 20:59:50 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <3d1390f8-7bc5-404d-b981-21e2e6b51086@telefonica.net> Date & Time: Sun, 17 Mar 2024 16:22:46 +0100
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
CER> On 2024-03-17 14:46, Patrick Shanahan wrote: [...] MN>>> In short, there is a bug in the current pipewire.
PS>> wrong attribution, nowhere did is say there is a bug in the current PS>> pipewire
CER> It is not attributed to you. There is a double ">>", albeit with CER> somewhat broken and unusual formatting.
Thanks, Carlos.
I'm sorry if I misled you, Patrick.
Anyway, today I found out two things.
The Audacity problem was caused by the portaudio library of my own build being too new, and I solved it by replacing it with the one provided by openSUSE. Of course, this has nothing to do with pipewire.
However, it has been reported that there can be problems between pipewire and Audacity, and I suspect that Ben's problem is along these lines and is related to the $ pactl info returning an error.
I also had a question about KDE theming, so I checked it out with installing Tumbleweed on my laptop. It turns out that $ pactl info should return results like Patrick showed, and that the absence of /run/user/1000/pulse/native on my PC is an anomaly. I thiink Ben is the same?
By the way, there are pid files under /run/user/1000/pulse as well as native file, and I was surprised to find out that they are from pipewire-pulse by checking with # ps ax | grep pid's value.
I see both of them on my TW
On 2024-03-18 12:59, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Audacity VS 'locale'? Message-ID : <3d1390f8-7bc5-404d-b981-21e2e6b51086@telefonica.net> Date & Time: Sun, 17 Mar 2024 16:22:46 +0100
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
CER> On 2024-03-17 14:46, Patrick Shanahan wrote: [...] MN>>> In short, there is a bug in the current pipewire.
PS>> wrong attribution, nowhere did is say there is a bug in the current PS>> pipewire
CER> It is not attributed to you. There is a double ">>", albeit with CER> somewhat broken and unusual formatting.
Thanks, Carlos.
I'm sorry if I misled you, Patrick.
Anyway, today I found out two things.
Welcome. I just solved an issue I had in Thunderbird with your messages. Thunderbird displayed them with a strange font that made reading them harder. I'm writing this OT to the thread info so others that have that issue see it. Thunderbird, Settings, General section, Fonts & Colours. Here I have "default font" Dejavu Sans, size 15. Then click on Advanced. The settings for "Latin" are, and were: Proportional: Sans Serif size 15 Serif: Dejavu Serif Sans-serif: Dejavu Sans Monospace: Dejavu Sans Mono 13 The trick is selecting for Japanese the same set. I had different (I did not record what). I don't know a way to select the same fonts for all languages in a single operation. ... -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: Audacity VS 'locale'? - font issue in TB with some messages solved Message-ID : <51255762-72ae-4468-adf4-81702973c839@telefonica.net> Date & Time: Mon, 18 Mar 2024 14:08:57 +0100 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: [...] MN>> Thanks, Carlos. MN>> I'm sorry if I misled you, Patrick. MN>> Anyway, today I found out two things. CER> Welcome. CER> I just solved an issue I had in Thunderbird with your messages. Thunderbird CER> displayed them with a strange font that made reading them CER> harder. I'm writing this OT to the thread info so others that CER> have that issue see it. I think that's a good idea. CER> Thunderbird, Settings, General section, Fonts & Colours. Here I CER> have "default font" Dejavu Sans, size 15. Then click on Advanced. CER> The settings for "Latin" are, and were: CER> Proportional: Sans Serif size 15 CER> Serif: Dejavu Serif CER> Sans-serif: Dejavu Sans CER> Monospace: Dejavu Sans Mono 13 CER> The trick is selecting for Japanese the same set. I had different (I did not CER> record what). I don't know a way to select the same fonts for CER> all languages in a single operation. In Japan, the Noto Sans and Noto Serif fonts, created in cooperation between Google and Adobe, seem to be well received. To us Japanese, Japanese is an ordinary language, but in the computer world, it is a special language, and this continues to create no small problems in various information systems....... Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say." -- Google Splits Up a Key AI Ethics Watchdog --
...
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
...
CER> I just solved an issue I had in Thunderbird with your messages. Thunderbird CER> displayed them with a strange font that made reading them CER> harder. I'm writing this OT to the thread info so others that CER> have that issue see it.
I think that's a good idea.
CER> Thunderbird, Settings, General section, Fonts & Colours. Here I CER> have "default font" Dejavu Sans, size 15. Then click on Advanced.
CER> The settings for "Latin" are, and were:
CER> Proportional: Sans Serif size 15 CER> Serif: Dejavu Serif CER> Sans-serif: Dejavu Sans CER> Monospace: Dejavu Sans Mono 13
As long as we are off topic anyway - anyone knows when TB actually uses monospace font? Is it possible to configure TB to display all messages using monospace?
CER> The trick is selecting for Japanese the same set.
The problem is that Sans-serif is a generic name which may resolve to different fonts for different encodings. Again - anyone knows a good universal font covering most of the UNICODE? Arguably, it is a bug of the mail client. As long as the message does not contain Japanese characters, it should *NOT* mark this message as having Japanese encoding.
I had different (I did not CER> record what). I don't know a way to select the same fonts for CER> all languages in a single operation.
In Japan, the Noto Sans and Noto Serif fonts, created in cooperation between Google and Adobe, seem to be well received.
I guess I should look at it, not sure what is used as default right now.
To us Japanese, Japanese is an ordinary language, but in the computer world, it is a special language, and this continues to create no small problems in various information systems.......
Best Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp
Ah, OK, so the message does contain Japanese characters. Maybe signature can be reconsidered taking in account the wider audience of this list.
Hello, In the Message; Subject : Re: Audacity VS 'locale'? - font issue in TB with some messages solved Message-ID : <CAA91j0XbW0F6nAfpq5AQWZ58=rN+xvDU6B=BN9MZ2YjtNMO5TA@mail.gmail.com> Date & Time: Tue, 19 Mar 2024 11:09:54 +0300 [AB] == Andrei Borzenkov <arvidjaar@gmail.com> has written: [...] AB> The problem is that Sans-serif is a generic name which may resolve to AB> different fonts for different encodings. Again - anyone knows a good AB> universal font covering most of the UNICODE? Noto Sans and Noto Serif. AB> Arguably, it is a bug of the mail client. As long as the message does AB> not contain Japanese characters, it should *NOT* mark this message as AB> having Japanese encoding. As Carlos correctly presents, the garbled characters are caused by the inclusion of characters that cannot be displayed by the mail software. [...] MN>> In Japan, the Noto Sans and Noto Serif fonts, created in cooperation MN>> between Google and Adobe, seem to be well received. AB> I guess I should look at it, not sure what is used as default AB> right now. I don't know what you are talking about? Best 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 Tue, Mar 19, 2024 at 11:29 AM Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote:
AB> Arguably, it is a bug of the mail client. As long as the message does AB> not contain Japanese characters, it should *NOT* mark this message as AB> having Japanese encoding.
As Carlos correctly presents, the garbled characters are caused by the inclusion of characters that cannot be displayed by the mail software.
And why do you feel it necessary to include Japanese characters in the posts to the English-speaking mailing list? You're just making it harder for everyone else.
Hello, In the Message; Subject : Re: Audacity VS 'locale'? - font issue in TB with some messages solved Message-ID : <CAA91j0XZoKB9cJmMyi1aw6kkSxPADkK7jr7sD5fA6nTOKC-A0w@mail.gmail.com> Date & Time: Tue, 19 Mar 2024 11:53:07 +0300 [AB] == Andrei Borzenkov <arvidjaar@gmail.com> has written: AB> On Tue, Mar 19, 2024 at 11:29 AM Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote: [...] AB> > As Carlos correctly presents, the garbled characters are caused by the AB> > inclusion of characters that cannot be displayed by the mail software. AB> And why do you feel it necessary to include Japanese characters in the AB> posts to the English-speaking mailing list? You're just making it AB> harder for everyone else. Are you only on this mailing list? I am on many mailing lists, where people from many different countries enter their names in their own language, and my Emacs-based MUA displays them as they appear. Your saying, in English, was criticized a long time ago (especially by the French people) and has been greatly relaxed, no? I remember those days...... Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say." -- Google Splits Up a Key AI Ethics Watchdog --
On 2024-03-19 10:27, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Audacity VS 'locale'? - font issue in TB with some messages solved Message-ID : <CAA91j0XZoKB9cJmMyi1aw6kkSxPADkK7jr7sD5fA6nTOKC-A0w@mail.gmail.com> Date & Time: Tue, 19 Mar 2024 11:53:07 +0300
[AB] == Andrei Borzenkov <...> has written:
AB> On Tue, Mar 19, 2024 at 11:29 AM Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote: [...] AB> > As Carlos correctly presents, the garbled characters are caused by the AB> > inclusion of characters that cannot be displayed by the mail software.
AB> And why do you feel it necessary to include Japanese characters in the AB> posts to the English-speaking mailing list? You're just making it AB> harder for everyone else.
Are you only on this mailing list?
I am on many mailing lists, where people from many different countries enter their names in their own language, and my Emacs-based MUA displays them as they appear.
I have no objection to people adding somekind of salutation or signature in their own language and lettering. It adds colour :-) But perhaps you could convince your EMACS to use UTF-8, which is the default on openSUSE, anyway. That should solve any font conversion issue, too. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On Tue, 19 Mar 2024 11:09:54 +0300 Andrei Borzenkov <arvidjaar@gmail.com> wrote:
Arguably, it is a bug of the mail client. As long as the message does not contain Japanese characters, it should *NOT* mark this message as having Japanese encoding.
The counter argument is that the MUA is correctly following the headers in the mail. Specifically Content-Type: text/plain; charset=ISO-2022-JP
On 2024-03-19 09:09, Andrei Borzenkov wrote:
...
[CER] == "Carlos E. R." <...> has written:
...
CER> I just solved an issue I had in Thunderbird with your messages. Thunderbird CER> displayed them with a strange font that made reading them CER> harder. I'm writing this OT to the thread info so others that CER> have that issue see it.
I think that's a good idea.
CER> Thunderbird, Settings, General section, Fonts & Colours. Here I CER> have "default font" Dejavu Sans, size 15. Then click on Advanced.
CER> The settings for "Latin" are, and were:
CER> Proportional: Sans Serif size 15 CER> Serif: Dejavu Serif CER> Sans-serif: Dejavu Sans CER> Monospace: Dejavu Sans Mono 13
As long as we are off topic anyway - anyone knows when TB actually uses monospace font? Is it possible to configure TB to display all messages using monospace?
It displays monospace if the mail is plain text for me, not if it is html. The setting is in the same "Fonts $ Colors" zone, button "advanced": Font Control [X] Allow messages to use other fonts [X] Use fixed width font for plain text messages
CER> The trick is selecting for Japanese the same set.
The problem is that Sans-serif is a generic name which may resolve to different fonts for different encodings. Again - anyone knows a good universal font covering most of the UNICODE?
Probably the Dejavu one, but I'm not certain.
Arguably, it is a bug of the mail client. As long as the message does not contain Japanese characters, it should *NOT* mark this message as having Japanese encoding.
But it does. Content-Type: text/plain; charset=ISO-2022-JP Thunderbird has to abide by that.
I had different (I did not CER> record what). I don't know a way to select the same fonts for CER> all languages in a single operation.
In Japan, the Noto Sans and Noto Serif fonts, created in cooperation between Google and Adobe, seem to be well received.
I guess I should look at it, not sure what is used as default right now.
I don't know how, but each of the languages seem to have a different choice; but this is an old TB profile I have.
To us Japanese, Japanese is an ordinary language, but in the computer world, it is a special language, and this continues to create no small problems in various information systems.......
Best Regards.
Computers are a western invention. The IBM PC only contemplated USA ASCII initially. It also caused problems in Europe, apparently all of our languages have a few letters not included in the USA ASCI char set (initially 7 bits).
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp
Ah, OK, so the message does contain Japanese characters. Maybe signature can be reconsidered taking in account the wider audience of this list.
He could just set UTF-8. My own email in reply here is: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 No idea why TB resorts to base64, that is not needed and can cause problems for/with some people. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: Audacity VS 'locale'? Message-ID : <87a5mvagy1.wl-nomiya@lake.dti.ne.jp> Date & Time: Mon, 18 Mar 2024 20:59:50 +0900 [MN] == Masaru Nomiya <nomiya@lake.dti.ne.jp> has written: [...] MN> So I followed Patrick's suggestion and re-installed pipewire and MN> pulseaudio. Sure enough, it installed fine, but $ pactl info still MN> returns an error.... (_ _? [...] It was due to a wrong setting in pipewire-pulse.conf. After correcting this, $ pactl info now shows the correct results, and Audasity works fine even with the portaudio library I built. Thanks to Patrick. However, my problem is not a common one. That is, my solution will not work for Ben. But I think that many of the reported problems are caused by communication problems between pulseaudio and pipewire..... BTW, what is the results of these? 1. $ ldd /usr/bin/pipewire* | grep pulse 2. $ find /etc -name pipewire* -o -name *pulse* 3. $ find ~/.config -name pipewire -o -name *pulse* Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
Tue, 19 Mar 2024 17:13:58 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
But I think that many of the reported problems are caused by communication problems between pulseaudio and pipewire.....
BTW, what is the results of these?
1. $ ldd /usr/bin/pipewire* | grep pulse
ldd /usr/bin/pipewire* | grep pulse /usr/bin/pipewire-pulse:
2. $ find /etc -name pipewire* -o -name *pulse*
~ find /etc -name pipewire* -o -name *pulse* /etc/pulse find: ‘/etc/apache2/ssl.key’: Permission denied find: ‘/etc/sudoers.d’: Permission denied /etc/systemd/user/sockets.target.wants/pipewire.socket /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket /etc/systemd/user/pipewire.service.wants /etc/systemd/user/pipewire-session-manager.service find: ‘/etc/credstore.encrypted’: Permission denied find: ‘/etc/sanlock’: Permission denied find: ‘/etc/firewalld’: Permission denied find: ‘/etc/redis’: Permission denied find: ‘/etc/pesign’: Permission denied find: ‘/etc/credstore’: Permission denied /etc/profile.d/pulseaudio.sh /etc/profile.d/pulseaudio.csh /etc/alternatives/pulsemixer find: ‘/etc/lvm/backup’: Permission denied find: ‘/etc/lvm/archive’: Permission denied find: ‘/etc/lvm/cache’: Permission denied find: ‘/etc/polkit-1/rules.d’: Permission denied find: ‘/etc/audit’: Permission denied find: ‘/etc/ppp’: Permission denied find: ‘/etc/libvirt’: Permission denied find: ‘/etc/ssl/private’: Permission denied /etc/pipewire find: ‘/etc/cups/ssl’: Permission denied /etc/apulse.conf find: ‘/etc/wdmd.d’: Permission denied find: ‘/etc/keys’: Permission denied find: ‘/etc/xen’: Permission denied /etc/ld.so.conf.d/pipewire-jack-x86_64.conf find: ‘/etc/rear’: Permission denied # find /etc -name pipewire* -o -name *pulse* /etc/pulse /etc/systemd/user/sockets.target.wants/pipewire.socket /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket /etc/systemd/user/pipewire.service.wants /etc/systemd/user/pipewire-session-manager.service /etc/profile.d/pulseaudio.sh /etc/profile.d/pulseaudio.csh /etc/alternatives/pulsemixer /etc/pipewire /etc/apulse.conf /etc/ld.so.conf.d/pipewire-jack-x86_64.conf
3. $ find ~/.config -name pipewire -o -name *pulse*
~ find ~/.config -name pipewire -o -name *pulse* /home/u3/.config/gconf/system/pulseaudio /home/u3/.config/pulse
Hello, In the Message; Subject : Re: Solved!, but.... (Was: Re: Audacity VS 'locale'?) Message-ID : <20240319063013.ca59db8a3d8ea948e63abc6c@trixtar.org> Date & Time: Tue, 19 Mar 2024 06:30:13 -0400 [BTF] == bent fender <slowroller@trixtar.org> has written: [...] BTF> ~ find ~/.config -name pipewire -o -name *pulse* BTF> /home/u3/.config/gconf/system/pulseaudio BTF> /home/u3/.config/pulse How about these? 4. $ ldd /usr/lib64/libpulse.so.0.* | grep pulse 5. $ ls -l /run/user/1000/pulse 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 --
Tue, 19 Mar 2024 20:03:27 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Solved!, but.... (Was: Re: Audacity VS 'locale'?) Message-ID : <20240319063013.ca59db8a3d8ea948e63abc6c@trixtar.org> Date & Time: Tue, 19 Mar 2024 06:30:13 -0400
[BTF] == bent fender <slowroller@trixtar.org> has written:
[...] BTF> ~ find ~/.config -name pipewire -o -name *pulse* BTF> /home/u3/.config/gconf/system/pulseaudio BTF> /home/u3/.config/pulse
How about these?
When do you go to bed again? :-)
4. $ ldd /usr/lib64/libpulse.so.0.* | grep pulse
~ ldd /usr/lib64/libpulse.so.0.* | grep pulse libpulsecommon-17.0.so => /usr/lib64/pulseaudio/libpulsecommon-17.0.so (0x00007f4786868000)
5. $ ls -l /run/user/1000/pulse
~ ls -l /run/user/1003/pulse total 4 srw-rw-rw- 1 u3 MoX 0 Mar 19 07:01 native -rw-r--r-- 1 u3 MoX 5 Mar 19 07:02 pid
Hello, In the Message; Subject : Re: Solved!, but.... (Was: Re: Audacity VS 'locale'?) Message-ID : <20240319085116.a05cddda71ca57525e4bbbb9@trixtar.org> Date & Time: Tue, 19 Mar 2024 08:51:16 -0400 [BTF] == bent fender <slowroller@trixtar.org> has written: BTF> Tue, 19 Mar 2024 20:03:27 +0900 BTF> Masaru Nomiya <nomiya@lake.dti.ne.jp> : [...] BTF> > How about these? BTF> When do you go to bed again? :-) I went to bed right after writing the e-mail. (^^;; BTF> ~ ldd /usr/lib64/libpulse.so.0.* | grep pulse BTF> libpulsecommon-17.0.so => /usr/lib64/pulseaudio/libpulsecommon-17.0.so (0x00007f4786868000) BTF> ~ ls -l /run/user/1003/pulse BTF> total 4 BTF> srw-rw-rw- 1 u3 MoX 0 Mar 19 07:01 native BTF> -rw-r--r-- 1 u3 MoX 5 Mar 19 07:02 pid Well, pipewire-pulseaudio seems to be working fine. I think it is supposed to be like this; get pid's value $ cat /run/user/1000/pulse/pid 2911 $ ps ax | grep 2911 2911 ? S<sl 0:00 /usr/bin/pipewire-pulse 19798 pts/0 SN+ 0:00 grep --color=auto 291 Does this work fine? $ pw-play /usr/share/sounds/Oxygen-Sys-Log-In-Short.ogg Please upload the resulting st.log somewhere; $ strace pactl info > st.log 2>&1 Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: m.nomiya+suse @ gmail.com ┃＼／彡 ┗━━┛ "A bachelor’s degree still holds prestige as a ticket to the middle class, but its value has received increasing scrutiny. In the last several years, rising tuition and student loan debt have led more Americans to reconsider an investment in postsecondary education." -- Washington Post --
Wed, 20 Mar 2024 06:53:05 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Does this work fine? $ pw-play /usr/share/sounds/Oxygen-Sys-Log-In-Short.ogg
plays OK
Please upload the resulting st.log somewhere; $ strace pactl info > st.log 2>&1
https://paste.opensuse.org/pastes/609e9a024426 I just did my 1st install of MxLinux, Audacity is no problem there.
Hello, In the Message; Subject : Re: Solved!, but.... (Was: Re: Audacity VS 'locale'?) Message-ID : <20240319221641.bc3048ce02263ddd8ba75cab@trixtar.org> Date & Time: Tue, 19 Mar 2024 22:16:41 -0400 [BTF] == bent fender <slowroller@trixtar.org> has written: BTF> Wed, 20 Mar 2024 06:53:05 +0900 BTF> Masaru Nomiya <nomiya@lake.dti.ne.jp> : MN> > Does this work fine? MN> > $ pw-play /usr/share/sounds/Oxygen-Sys-Log-In-Short.ogg BTF> plays OK MN> > Please upload the resulting st.log somewhere; MN> > $ strace pactl info > st.log 2>&1 BTF> https://paste.opensuse.org/pastes/609e9a024426 Thanks. There is no problem with pipewire at all, it is Audacity itself that is not starting. Please show the message when you start audacity in the terminal. Kind 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 --
Wed, 20 Mar 2024 12:33:11 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Please show the message when you start audacity in the terminal.
There is no mesage and no audacity, sometimes a microsecond flash of the audacity splash-screen near the very end of the launch attempt and that is all.
On 2024-03-20 12:58, bent fender wrote:
Wed, 20 Mar 2024 12:33:11 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Please show the message when you start audacity in the terminal.
There is no mesage and no audacity, sometimes a microsecond flash of the audacity splash-screen near the very end of the launch attempt and that is all.
Just in case there is a misunderstanding: The idea is to open a terminal, and type in it "audacity" and enter. Often graphical programs write something to the terminal when crashing. You could also try "audacity --test", it should do a diagnostic. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Wed, 20 Mar 2024 13:29:31 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-03-20 12:58, bent fender wrote:
Wed, 20 Mar 2024 12:33:11 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Please show the message when you start audacity in the terminal.
There is no mesage and no audacity, sometimes a microsecond flash of the audacity splash-screen near the very end of the launch attempt and that is all.
Just in case there is a misunderstanding:
The idea is to open a terminal, and type in it "audacity" and enter. Often graphical programs write something to the terminal when crashing.
You could also try "audacity --test", it should do a diagnostic.
done better than that but I'm swamped right now, later. (freshie TW on laptop, audacity works)
* Bengt Gördén <bengan@bag.org> [03-20-24 11:47]:
On 2024-03-20 13:27, bent fender wrote:
(freshie TW on laptop, audacity works)
So, it was just a rotten TW on your part then?
ie: mis-configured -- (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 oftc
Wed, 20 Mar 2024 12:04:50 -0400 Patrick Shanahan <paka@opensuse.org> :
* Bengt Gördén <bengan@bag.org> [03-20-24 11:47]:
On 2024-03-20 13:27, bent fender wrote:
(freshie TW on laptop, audacity works)
So, it was just a rotten TW on your part then?
the only thing that was on my part was the subject header
ie: mis-configured
https://imgur.com/AUBPWAI.png https://paste.opensuse.org/pastes/13b81a1c5fb1 to recap :-) fresh install on laptop: Audacity works fresh updated install on laptop: Audacity works updated TW install on laptop using home folder from desktop TW: Audacity works updated TW & Slowroll on desktp: Audacity bombs You two can make whatever you like of that NB1 the plugins annunciation minds me of earlier discussions about *caps.so* so I wonder where exactly and how does Audacity store the users' decision about accepting or rejecting these plugins? NB2 the fresh install strace is alrewady *lousy* with LOCALE issues!
On 2024-03-20 15:41, bent fender wrote:
NB1 the plugins annunciation minds me of earlier discussions about*caps.so* so I wonder where exactly and how does Audacity store the users' decision about accepting or rejecting these plugins?
Tools/Plugin manager I also remember that audacity doesn't update its list of plugins if you remove one of them. Audacity just disables it in the list. The only way is/was to delete the files and have them recreated the next time you start audacity. .config/audacity/pluginsettings.cfg .config/audacity/pluginregistry.cfg -- /bengan
Wed, 20 Mar 2024 19:20:33 +0100 Bengt Gördén <bengan@bag.org> :
On 2024-03-20 15:41, bent fender wrote:
NB1 the plugins annunciation minds me of earlier discussions about*caps.so* so I wonder where exactly and how does Audacity store the users' decision about accepting or rejecting these plugins?
Tools/Plugin manager
I also remember that audacity doesn't update its list of plugins if you remove one of them. Audacity just disables it in the list. The only way is/was to delete the files and have them recreated the next time you start audacity.
.config/audacity/pluginsettings.cfg .config/audacity/pluginregistry.cfg
The only reason I ask is that if "I" had misconfigured anything it would be in the home directory but this new laptop TW *is* now using a copy of the old desktop-TW home directory and Audacity is working just fine. This audacity is Audacity-3.4.2. When I have time I'll do a freshie on the desktop to see what gives.
* bent fender <slowroller@trixtar.org> [03-20-24 17:21]:
Wed, 20 Mar 2024 19:20:33 +0100 Bengt Gördén <bengan@bag.org> :
On 2024-03-20 15:41, bent fender wrote:
NB1 the plugins annunciation minds me of earlier discussions about*caps.so* so I wonder where exactly and how does Audacity store the users' decision about accepting or rejecting these plugins?
Tools/Plugin manager
I also remember that audacity doesn't update its list of plugins if you remove one of them. Audacity just disables it in the list. The only way is/was to delete the files and have them recreated the next time you start audacity.
.config/audacity/pluginsettings.cfg .config/audacity/pluginregistry.cfg
The only reason I ask is that if "I" had misconfigured anything it would be in the home directory but this new laptop TW *is* now using a copy of the old desktop-TW home directory and Audacity is working just fine.
This audacity is Audacity-3.4.2. When I have time I'll do a freshie on the desktop to see what gives.
maybe not mis-config of app but of tw system or sound! -- (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 oftc
Wed, 20 Mar 2024 19:20:33 +0100 Bengt Gördén <bengan@bag.org> :
On 2024-03-20 15:41, bent fender wrote:
NB1 the plugins annunciation minds me of earlier discussions about*caps.so* so I wonder where exactly and how does Audacity store the users' decision about accepting or rejecting these plugins?
Tools/Plugin manager
I also remember that audacity doesn't update its list of plugins if you remove one of them. Audacity just disables it in the list. The only way is/was to delete the files and have them recreated the next time you start audacity.
.config/audacity/pluginsettings.cfg .config/audacity/pluginregistry.cfg
Took me 3 tries to install a fresh TW, build up the package list and tweak everything all the way but without pulseaudio. Audacity worked throughout with the odd fit thrown about plugins. Made several backup images at different stages and saved out the packages XML lists each time. Then I had to try installing pulseaudio because its pavu control panel is too essential. Installing Audacity at this point required removals -wireplumber-audio -pipewire-pulseaudio -pipewire-alsa Even so, as soon as pulseaudio was installed Audacity stopped launching. Rebooted and tried to launch again, this time I got a "libjack.so --- no such file or directory" I don't understand how an uninstalled package can later become a missing dependancy? Anyway, all's well that ends well, with the installation of libjack Audacity is back in business and I'm ready for a LOOOOOOONG overdue guitar session. Thanks for all the pointers, as applicable...
Hello, In the Message; Subject : Re: Solved!, but.... (Was: Re: Audacity VS 'locale'?) Message-ID : <20240320075838.04acbf8a6cc95191be268827@trixtar.org> Date & Time: Wed, 20 Mar 2024 07:58:38 -0400 [BTF] == bent fender <slowroller@trixtar.org> has written: BTF> Wed, 20 Mar 2024 12:33:11 +0900 MN> > Please show the message when you start audacity in the terminal. BTF> There is no mesage and no audacity, sometimes a microsecond BTF> flash of the audacity splash-screen near the very end of the launch BTF> attempt and that is all. Ah, I UNDERSTAND! If you had written about this phenomenon, you could have solved it earlier. Anyway, you've got a plugin issue. That is, Audacity loads plugins at startup, but some of them are faulty and stop launch. The solution is this; $ rm -rf ~/.audacity-data Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
Thu, 21 Mar 2024 07:10:58 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Solved!, but.... (Was: Re: Audacity VS 'locale'?) Message-ID : <20240320075838.04acbf8a6cc95191be268827@trixtar.org> Date & Time: Wed, 20 Mar 2024 07:58:38 -0400
[BTF] == bent fender <slowroller@trixtar.org> has written:
BTF> Wed, 20 Mar 2024 12:33:11 +0900
MN> > Please show the message when you start audacity in the terminal.
BTF> There is no mesage and no audacity, sometimes a microsecond BTF> flash of the audacity splash-screen near the very end of the launch BTF> attempt and that is all.
Ah, I UNDERSTAND!
If you had written about this phenomenon, you could have solved it earlier.
If I had known about it maybe. I remember seeing that Audacity alert sometime in the past 12 months, AND my reaction would have been to 'Continue' and not enable bad plugs. I may be overqualified to be a dev but I ain't stupid :-) As noted earlier I did try to do a fresh TW install on my desktop to see if Audacity would work on it like it did on th elaptop fresh-TW hours earlier. *The entire TW install failed* (a first for me): https://paste.opensuse.org/pastes/fb23086139a5 I could do a fscheck with a fix but don't know if that'd be the best prospect of saving 1-1/2 hour of my time put into the install.
Anyway, you've got a plugin issue. That is, Audacity loads plugins at startup, but some of them are faulty and stop launch.
The solution is this;
$ rm -rf ~/.audacity-data
Someone (maybe you) had suggested that one before and it didn't work then or now. Carlos' "audacity --test" produces a splashflash and no Audacity or anything else. I also renamed these to no effect (just get a splashflash): .config/audacity/pluginsettings.cfg .config/audacity/pluginregistry.cfg
Hello, In the Message; Subject : Re: Solved!, but.... (Was: Re: Audacity VS 'locale'?) Message-ID : <20240320225907.9d63b370b9bddf051c7b6156@trixtar.org> Date & Time: Wed, 20 Mar 2024 22:59:07 -0400 [BTF] == bent fender <slowroller@trixtar.org> has written: BTF> Thu, 21 Mar 2024 07:10:58 +0900 BTF> Masaru Nomiya <nomiya@lake.dti.ne.jp> : [..] MN> > The solution is this; MN> > $ rm -rf ~/.audacity-data BTF> Someone (maybe you) had suggested that one before and it didn't BTF> work then or now. If you remove .audacity-data and it still freezes on splash, that means it freezes on the audio device scan. Sorry, I have no idea..... Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
participants (10)
-
Andrei Borzenkov -
Ben T. Fender -
Bengt Gördén -
bent fender
-
Carlos E. R. -
Dave Howorth -
jdd＠dodin.org -
Lew Wolfgang -
Masaru Nomiya -
Patrick Shanahan