[opensuse] Test mic?
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
W dniu 08.05.2020 o 07:08, Doug McGarrett pisze:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug
One of possibilities: pactl load-module module-loopback latency_msec=1000 This makes PulseAudio server to play back your mic on your speakers. The latency argument is optional. To unload: pactl unload-module module-loopback
On 5/8/20 1:21 AM, Adam Mizerski wrote:
W dniu 08.05.2020 o 07:08, Doug McGarrett pisze:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug
One of possibilities: pactl load-module module-loopback latency_msec=1000
This makes PulseAudio server to play back your mic on your speakers. The latency argument is optional.
To unload: pactl unload-module module-loopback
No joy: linux-4qnb:/ # pactl load-module module-loopback latency_msec=1000 Connection failure: Connection refused pa_context_connect() failed: Connection refused linux-4qnb:/ # pactl unload-module module-loopback^C --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
W dniu 09.05.2020 o 06:56, Doug McGarrett pisze:
On 5/8/20 1:21 AM, Adam Mizerski wrote:
W dniu 08.05.2020 o 07:08, Doug McGarrett pisze:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug
One of possibilities: pactl load-module module-loopback latency_msec=1000
This makes PulseAudio server to play back your mic on your speakers. The latency argument is optional.
To unload: pactl unload-module module-loopback
No joy: linux-4qnb:/ # pactl load-module module-loopback latency_msec=1000 Connection failure: Connection refused pa_context_connect() failed: Connection refused linux-4qnb:/ # pactl unload-module module-loopback^C
--doug
Run it as your user, not root.
On 5/9/20 9:12 AM, Adam Mizerski wrote:
W dniu 09.05.2020 o 06:56, Doug McGarrett pisze:
On 5/8/20 1:21 AM, Adam Mizerski wrote:
W dniu 08.05.2020 o 07:08, Doug McGarrett pisze:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug
One of possibilities: pactl load-module module-loopback latency_msec=1000
This makes PulseAudio server to play back your mic on your speakers. The latency argument is optional.
To unload: pactl unload-module module-loopback
No joy: linux-4qnb:/ # pactl load-module module-loopback latency_msec=1000 Connection failure: Connection refused pa_context_connect() failed: Connection refused linux-4qnb:/ # pactl unload-module module-loopback^C
--doug
Run it as your user, not root.
OK, ran it as user. Not happy. (su'd to user doug:) doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000 Connection failure: Connection refused pa_context_connect() failed: Connection refused doug@linux-4qnb:/root> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/05/2020 20.48, Doug McGarrett wrote:
On 5/9/20 9:12 AM, Adam Mizerski wrote:
Run it as your user, not root.
OK, ran it as user. Not happy. (su'd to user doug:) doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Why on earth are you using a desktop as root, so that you have to su to user? If konsole drops you to root by default, do not use konsole. Your system is broken. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 5/24/20 4:42 PM, Carlos E. R. wrote:
On 09/05/2020 20.48, Doug McGarrett wrote:
On 5/9/20 9:12 AM, Adam Mizerski wrote:
Run it as your user, not root.
OK, ran it as user. Not happy. (su'd to user doug:) doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Why on earth are you using a desktop as root, so that you have to su to user?
If konsole drops you to root by default, do not use konsole.
Your system is broken.
Since the sequence with the icons, someone fixed the console problem for me. I don't know who or how, but when I select the console, I get a user login. I can then su to admin if I need to, and exit back to user when done. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/05/2020 01.24, Doug McGarrett wrote:
On 5/24/20 4:42 PM, Carlos E. R. wrote:
On 09/05/2020 20.48, Doug McGarrett wrote:
On 5/9/20 9:12 AM, Adam Mizerski wrote:
Run it as your user, not root.
OK, ran it as user. Not happy. (su'd to user doug:) doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Why on earth are you using a desktop as root, so that you have to su to user?
If konsole drops you to root by default, do not use konsole.
Your system is broken.
Since the sequence with the icons, someone fixed the console problem for me. I don't know who or how, but when I select the console, I get a user login. I can then su to admin if I need to, and exit back to user when done.
But you are not doing that. You said: ]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000 Doing that way, it has to fail. You are not going back to "user", you are su-ing to user. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 5/25/20 5:49 AM, Carlos E. R. wrote:
On 25/05/2020 01.24, Doug McGarrett wrote:
On 5/24/20 4:42 PM, Carlos E. R. wrote:
On 09/05/2020 20.48, Doug McGarrett wrote:
On 5/9/20 9:12 AM, Adam Mizerski wrote:
Run it as your user, not root.
OK, ran it as user. Not happy. (su'd to user doug:) doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Why on earth are you using a desktop as root, so that you have to su to user?
If konsole drops you to root by default, do not use konsole.
Your system is broken.
Since the sequence with the icons, someone fixed the console problem for me. I don't know who or how, but when I select the console, I get a user login. I can then su to admin if I need to, and exit back to user when done.
But you are not doing that. You said:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Doing that way, it has to fail.
You are not going back to "user", you are su-ing to user.
As I have reported in another post, during the icon fiasco someone sent a command that I implemented which turns the console back into a user console unless I su to root. So every command I input now is automatically implemented as user, unless the system says it requires a root environment, which I can obtain in usual Linux/Unix fashion by su. To be clear, when I log in from a "computer off" start, the console comes up in a user config. I don't know why it ever came up differently, but all the "suggestions" to reinstall would probably come up the same way the original did. I installed from a CD downloaded from the net, just like almost everybody else. I picked this system deliberately because it would not (hopefully ever) require a reinstallation, like so many Linux versions do, and I'm not about to change my mind. (It took me about a week to find and get everything I use installed--another reason not to do it again!) RE sound input: Skype doesn't work in Windows on this machine either, so it's not a function of a bad Suse install. This is a new machine, purchased from Micro Center in Westbury NY just a few months ago. It's called PowerSpec and it was not cheap! If anyone wants an lshw or a dmidecode for this system, I will be happy to send it to him/her off list. The complaints about sound software from the system only started since I upgraded the whole system last week with zypper dup, so I suppose there is a bug in the sound software. It didn't complain for the months previous. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/05/2020 19.53, Doug McGarrett wrote:
On 5/25/20 5:49 AM, Carlos E. R. wrote:
On 25/05/2020 01.24, Doug McGarrett wrote:
On 5/24/20 4:42 PM, Carlos E. R. wrote:
On 09/05/2020 20.48, Doug McGarrett wrote:
On 5/9/20 9:12 AM, Adam Mizerski wrote:
Run it as your user, not root.
OK, ran it as user. Not happy. (su'd to user doug:) doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Why on earth are you using a desktop as root, so that you have to su to user?
If konsole drops you to root by default, do not use konsole.
Your system is broken.
Since the sequence with the icons, someone fixed the console problem for me. I don't know who or how, but when I select the console, I get a user login. I can then su to admin if I need to, and exit back to user when done.
But you are not doing that. You said:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Doing that way, it has to fail.
You are not going back to "user", you are su-ing to user.
As I have reported in another post, during the icon fiasco someone sent a command that I implemented which turns the console back into a user console unless I su to root. So every command I input now is automatically implemented as user, unless the system says it requires a root environment, which I can obtain in usual Linux/Unix fashion by su. To be clear, when I log in from a "computer off" start, the console comes up in a user config.
Then explain this: ]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000 ...................^^^^^ (I can explain it. I want you to explain it.)
I don't know why it ever came up differently, but all the "suggestions" to reinstall would probably come up the same way the original did. I installed from a CD downloaded from the net, just like almost everybody else. I picked this system deliberately because it would not (hopefully ever) require a reinstallation, like so many Linux versions do, and I'm not about to change my mind. (It took me about a week to find and get everything I use installed--another reason not to do it again!)
We told you on that thread that you have the wrong repositories. For the record, you don't have to reinstall Leap every time there is a new version. I have *never* reinstalled this system, which goes back to 2009 with 11.0, at least as far as logs go. I think it goes back to 7.3 or perhaps 6.1, doing updates each time. The procedure had complications back them, but it is almost trivial within a major Leap version. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [05-25-20 14:12]:
On 25/05/2020 19.53, Doug McGarrett wrote:
On 5/25/20 5:49 AM, Carlos E. R. wrote:
On 25/05/2020 01.24, Doug McGarrett wrote:
On 5/24/20 4:42 PM, Carlos E. R. wrote:
On 09/05/2020 20.48, Doug McGarrett wrote:
On 5/9/20 9:12 AM, Adam Mizerski wrote:
> Run it as your user, not root. > OK, ran it as user. Not happy. (su'd to user doug:) doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Why on earth are you using a desktop as root, so that you have to su to user?
If konsole drops you to root by default, do not use konsole.
Your system is broken.
Since the sequence with the icons, someone fixed the console problem for me. I don't know who or how, but when I select the console, I get a user login. I can then su to admin if I need to, and exit back to user when done.
But you are not doing that. You said:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Doing that way, it has to fail.
You are not going back to "user", you are su-ing to user.
As I have reported in another post, during the icon fiasco someone sent a command that I implemented which turns the console back into a user console unless I su to root. So every command I input now is automatically implemented as user, unless the system says it requires a root environment, which I can obtain in usual Linux/Unix fashion by su. To be clear, when I log in from a "computer off" start, the console comes up in a user config.
Then explain this:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000 ...................^^^^^
(I can explain it. I want you to explain it.)
I don't know why it ever came up differently, but all the "suggestions" to reinstall would probably come up the same way the original did. I installed from a CD downloaded from the net, just like almost everybody else. I picked this system deliberately because it would not (hopefully ever) require a reinstallation, like so many Linux versions do, and I'm not about to change my mind. (It took me about a week to find and get everything I use installed--another reason not to do it again!)
We told you on that thread that you have the wrong repositories.
For the record, you don't have to reinstall Leap every time there is a new version. I have *never* reinstalled this system, which goes back to 2009 with 11.0, at least as far as logs go. I think it goes back to 7.3 or perhaps 6.1, doing updates each time.
The procedure had complications back them, but it is almost trivial within a major Leap version.
and updating/upgrading Leap systems is different than maintaining a Tumbleweed system, except that some system expertise is necessary and not demonstratively not possessed by the OP. His computer will only work correctly with *any* operating system, if the power cord is not connected to a power source. -- (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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 5/25/20 2:04 PM, Carlos E. R. wrote:
On 25/05/2020 19.53, Doug McGarrett wrote:
On 5/25/20 5:49 AM, Carlos E. R. wrote:
On 25/05/2020 01.24, Doug McGarrett wrote:
On 5/24/20 4:42 PM, Carlos E. R. wrote:
On 09/05/2020 20.48, Doug McGarrett wrote:
On 5/9/20 9:12 AM, Adam Mizerski wrote:
> Run it as your user, not root. > OK, ran it as user. Not happy. (su'd to user doug:) doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Why on earth are you using a desktop as root, so that you have to su to user?
If konsole drops you to root by default, do not use konsole.
Your system is broken.
Since the sequence with the icons, someone fixed the console problem for me. I don't know who or how, but when I select the console, I get a user login. I can then su to admin if I need to, and exit back to user when done.
But you are not doing that. You said:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Doing that way, it has to fail.
You are not going back to "user", you are su-ing to user.
As I have reported in another post, during the icon fiasco someone sent a command that I implemented which turns the console back into a user console unless I su to root. So every command I input now is automatically implemented as user, unless the system says it requires a root environment, which I can obtain in usual Linux/Unix fashion by su. To be clear, when I log in from a "computer off" start, the console comes up in a user config.
Then explain this:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000 ...................^^^^^
(I can explain it. I want you to explain it.)
I can't explain it. This appears to have been something from some days ago, when someone asked me to run the cammand pactl something or other, at a time while I still had the root login on console. I don't know what it was supposed to do, but I'm pretty sure it did not.
I don't know why it ever came up differently, but all the "suggestions" to reinstall would probably come up the same way the original did. I installed from a CD downloaded from the net, just like almost everybody else. I picked this system deliberately because it would not (hopefully ever) require a reinstallation, like so many Linux versions do, and I'm not about to change my mind. (It took me about a week to find and get everything I use installed--another reason not to do it again!)
We told you on that thread that you have the wrong repositories.
I have no idea what repositories I have, nor do I know how to find out-- you think you know more about this system than I do, but you seem to think I have leap installed. I don't. I have tumbleweed installed. I have whatever repositories that tw installed at system installation. --doug>
For the record, you don't have to reinstall Leap every time there is a new version. I have *never* reinstalled this system, which goes back to 2009 with 11.0, at least as far as logs go. I think it goes back to 7.3 or perhaps 6.1, doing updates each time.
The procedure had complications back them, but it is almost trivial within a major Leap version.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/05/2020 20.39, Doug McGarrett wrote:
On 5/25/20 2:04 PM, Carlos E. R. wrote:
On 25/05/2020 19.53, Doug McGarrett wrote:
On 5/25/20 5:49 AM, Carlos E. R. wrote:
On 25/05/2020 01.24, Doug McGarrett wrote:
On 5/24/20 4:42 PM, Carlos E. R. wrote:
On 09/05/2020 20.48, Doug McGarrett wrote: > On 5/9/20 9:12 AM, Adam Mizerski wrote:
>> Run it as your user, not root. >> > OK, ran it as user. Not happy. (su'd to user doug:) > doug@linux-4qnb:/root> pactl load-module module-loopback > latency_msec=1000
Why on earth are you using a desktop as root, so that you have to su to user?
If konsole drops you to root by default, do not use konsole.
Your system is broken.
Since the sequence with the icons, someone fixed the console problem for me. I don't know who or how, but when I select the console, I get a user login. I can then su to admin if I need to, and exit back to user when done.
But you are not doing that. You said:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Doing that way, it has to fail.
You are not going back to "user", you are su-ing to user.
As I have reported in another post, during the icon fiasco someone sent a command that I implemented which turns the console back into a user console unless I su to root. So every command I input now is automatically implemented as user, unless the system says it requires a root environment, which I can obtain in usual Linux/Unix fashion by su. To be clear, when I log in from a "computer off" start, the console comes up in a user config.
Then explain this:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000 ...................^^^^^
(I can explain it. I want you to explain it.)
I can't explain it. This appears to have been something from some days ago, when someone asked me to run the cammand pactl something or other, at a time while I still had the root login on console. I don't know what it was supposed to do, but I'm pretty sure it did not.
a) To go back to "user" on a terminal where you became "root" before, you do not use "su", you type "exit", or control-D. That is going back. If the terminal closes, then you were not "user" initially. b) In the case of using "su", you do not use "su doug". Instead, you have to use "su - doug". That dash is crucial. Without it, you remain at the root home without write access, without the correct environment, and commands fail. The proof of what I say is that tell tale path in your prompt. That is, quite probably, why the command they told you to run failed. This is basic, you should know these things, but not everybody does. Similarly, to become root, you have to use "su -".
I don't know why it ever came up differently, but all the "suggestions" to reinstall would probably come up the same way the original did. I installed from a CD downloaded from the net, just like almost everybody else. I picked this system deliberately because it would not (hopefully ever) require a reinstallation, like so many Linux versions do, and I'm not about to change my mind. (It took me about a week to find and get everything I use installed--another reason not to do it again!)
We told you on that thread that you have the wrong repositories.
I have no idea what repositories I have, nor do I know how to find out-- you think you know more about this system than I do, but you seem to think I have leap installed.
Yes, you do. Knurph told you few days ago to run "zypper lr -d". That's the command to produce the list of repositories. And we told you that you should do certain things, but you did not. Thread "Update Error" And no, I know you don't have Leap installed.
I don't. I have tumbleweed installed. I have whatever repositories that tw installed at system installation.
No, you have way more. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 5/25/20 4:02 PM, Carlos E. R. wrote:
On 25/05/2020 20.39, Doug McGarrett wrote:
On 5/25/20 2:04 PM, Carlos E. R. wrote:
On 25/05/2020 19.53, Doug McGarrett wrote:
On 5/25/20 5:49 AM, Carlos E. R. wrote:
On 25/05/2020 01.24, Doug McGarrett wrote:
On 5/24/20 4:42 PM, Carlos E. R. wrote: > On 09/05/2020 20.48, Doug McGarrett wrote: >> On 5/9/20 9:12 AM, Adam Mizerski wrote: > > >>> Run it as your user, not root. >>> >> OK, ran it as user. Not happy. (su'd to user doug:) >> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000 > > Why on earth are you using a desktop as root, so that you have to su to user? > > If konsole drops you to root by default, do not use konsole. > > Your system is broken. > Since the sequence with the icons, someone fixed the console problem for me. I don't know who or how, but when I select the console, I get a user login. I can then su to admin if I need to, and exit back to user when done.
But you are not doing that. You said:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Doing that way, it has to fail.
You are not going back to "user", you are su-ing to user.
As I have reported in another post, during the icon fiasco someone sent a command that I implemented which turns the console back into a user console unless I su to root. So every command I input now is automatically implemented as user, unless the system says it requires a root environment, which I can obtain in usual Linux/Unix fashion by su. To be clear, when I log in from a "computer off" start, the console comes up in a user config.
Then explain this:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
...................^^^^^
(I can explain it. I want you to explain it.)
I can't explain it. This appears to have been something from some days ago, when someone asked me to run the cammand pactl something or other, at a time while I still had the root login on console. I don't know what it was supposed to do, but I'm pretty sure it did not.
a) To go back to "user" on a terminal where you became "root" before, you do not use "su", you type "exit", or control-D. That is going back. If the terminal closes, then you were not "user" initially.
You have the sequence out of time. to go back to user, you are correct, IF it started as user. Back a week or so ago, it did not start as user. It started as root. In that case, ONLY, it was necessary to us su to go to a user console.
b) In the case of using "su", you do not use "su doug". Instead, you have to use "su - doug". That dash is crucial. Without it, you remain at the root home without write access, without the correct environment, and commands fail. The proof of what I say is that tell tale path in your prompt.
That is correct. However, that situation is in the past and gone.
That is, quite probably, why the command they told you to run failed. This is basic, you should know these things, but not everybody does.
Similarly, to become root, you have to use "su -".
I don't know why it ever came up differently, but all the "suggestions" to reinstall would probably come up the same way the original did. I installed from a CD downloaded from the net, just like almost everybody else. I picked this system deliberately because it would not (hopefully ever) require a reinstallation, like so many Linux versions do, and I'm not about to change my mind. (It took me about a week to find and get everything I use installed--another reason not to do it again!)
We told you on that thread that you have the wrong repositories.
I have no idea what repositories I have, nor do I know how to find out-- you think you know more about this system than I do, but you seem to think I have leap installed.
Yes, you do. Knurph told you few days ago to run "zypper lr -d". That's the command to produce the list of repositories. And we told you that you should do certain things, but you did not. Thread "Update Error"
And no, I know you don't have Leap installed.
I don't. I have tumbleweed installed. I have whatever repositories that tw installed at system installation.
No, you have way more.
Well, that's possible. I have some apps installed that may not appear in the Suse repos. But not "way" more. And no-one has mentioned how one goes about determining what apps are available in official Suse repos. It is possible--no, definite in the case of Master PDF Editor--that I obtained an app from some repo not in the Suse canon because I didn't know it was there--and in that particular case, at least one other correspondent didn't know either. It is almost certainly true of LightScribe. And one or two others. --doug
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Doug McGarrett <dmcgarrett@optonline.net> [05-25-20 16:29]: [...] 39 layers of previous quotes removed
You have the sequence out of time. to go back to user, you are correct, IF it started as user. Back a week or so ago, it did not start as user. It started as root. In that case, ONLY, it was necessary to us su to go to a user console.
and *everything* that you did during that time period had the potential or did contribute to borking your current ?system?.
b) In the case of using "su", you do not use "su doug". Instead, you have to use "su - doug". That dash is crucial. Without it, you remain at the root home without write access, without the correct environment, and commands fail. The proof of what I say is that tell tale path in your prompt.
That is correct. However, that situation is in the past and gone.
*except* what-ever you did during that time period made unknown and unintended changes to to your system which you have failed to recover. your only savior at this time is a reinstall which you unequivocally refuse. and you may as well quite complaining about your system not performing as you wish as you refuse to accept help! -- (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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/05/2020 22.25, Doug McGarrett wrote:
On 5/25/20 4:02 PM, Carlos E. R. wrote:
On 25/05/2020 20.39, Doug McGarrett wrote:
On 5/25/20 2:04 PM, Carlos E. R. wrote:
On 25/05/2020 19.53, Doug McGarrett wrote:
On 5/25/20 5:49 AM, Carlos E. R. wrote:
On 25/05/2020 01.24, Doug McGarrett wrote: > On 5/24/20 4:42 PM, Carlos E. R. wrote: >> On 09/05/2020 20.48, Doug McGarrett wrote: >>> On 5/9/20 9:12 AM, Adam Mizerski wrote: >> >> >>>> Run it as your user, not root. >>>> >>> OK, ran it as user. Not happy. (su'd to user doug:) >>> doug@linux-4qnb:/root> pactl load-module module-loopback >>> latency_msec=1000 >> >> Why on earth are you using a desktop as root, so that you have >> to su to user? >> >> If konsole drops you to root by default, do not use konsole. >> >> Your system is broken. >> > Since the sequence with the icons, someone fixed the > console problem for me. I don't know who or how, but when > I select the console, I get a user login. I can then su > to admin if I need to, and exit back to user when done.
But you are not doing that. You said:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
Doing that way, it has to fail.
You are not going back to "user", you are su-ing to user.
As I have reported in another post, during the icon fiasco someone sent a command that I implemented which turns the console back into a user console unless I su to root. So every command I input now is automatically implemented as user, unless the system says it requires a root environment, which I can obtain in usual Linux/Unix fashion by su. To be clear, when I log in from a "computer off" start, the console comes up in a user config.
Then explain this:
]> OK, ran it as user. Not happy. (su'd to user doug:) ]> doug@linux-4qnb:/root> pactl load-module module-loopback latency_msec=1000
...................^^^^^
(I can explain it. I want you to explain it.)
I can't explain it. This appears to have been something from some days ago, when someone asked me to run the cammand pactl something or other, at a time while I still had the root login on console. I don't know what it was supposed to do, but I'm pretty sure it did not.
a) To go back to "user" on a terminal where you became "root" before, you do not use "su", you type "exit", or control-D. That is going back. If the terminal closes, then you were not "user" initially.
You have the sequence out of time. to go back to user, you are correct, IF it started as user. Back a week or so ago, it did not start as user. It started as root. In that case, ONLY, it was necessary to us su to go to a user console.
No, I'm going only by what you posted in this single thread. In fact, by that single paragraph that I asked you to explain.
b) In the case of using "su", you do not use "su doug". Instead, you have to use "su - doug". That dash is crucial. Without it, you remain at the root home without write access, without the correct environment, and commands fail. The proof of what I say is that tell tale path in your prompt.
That is correct. However, that situation is in the past and gone.
It is not past. It is present. This single thread. I want you to understand that to go back to user you can not use "su doug". You have to go BACK, ie, type 'exit'. ALWAYS. It is a concept that you must record in fire letters on your memory.
That is, quite probably, why the command they told you to run failed. This is basic, you should know these things, but not everybody does.
Similarly, to become root, you have to use "su -".
I don't know why it ever came up differently, but all the "suggestions" to reinstall would probably come up the same way the original did. I installed from a CD downloaded from the net, just like almost everybody else. I picked this system deliberately because it would not (hopefully ever) require a reinstallation, like so many Linux versions do, and I'm not about to change my mind. (It took me about a week to find and get everything I use installed--another reason not to do it again!)
We told you on that thread that you have the wrong repositories.
I have no idea what repositories I have, nor do I know how to find out-- you think you know more about this system than I do, but you seem to think I have leap installed.
Yes, you do. Knurph told you few days ago to run "zypper lr -d". That's the command to produce the list of repositories. And we told you that you should do certain things, but you did not. Thread "Update Error"
And no, I know you don't have Leap installed.
I don't. I have tumbleweed installed. I have whatever repositories that tw installed at system installation.
No, you have way more. Well, that's possible. I have some apps installed that may not appear in the Suse repos. But not "way" more. And no-one has mentioned how one goes about determining what apps are available in official Suse repos. It is possible--no, definite in the case of Master PDF Editor--that I obtained an app from some repo not in the Suse canon because I didn't know it was there--and in that particular case, at least one other correspondent didn't know either. It is almost certainly true of LightScribe. And one or two others.
You have certain repos installed that can explain the many problems you are having. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
* Doug McGarrett <dmcgarrett@optonline.net> [05-25-20 13:56]: [...] much cruft removed
RE sound input: Skype doesn't work in Windows on this machine either, so it's not a function of a bad Suse install. This is a new machine, purchased from Micro Center in Westbury NY just a few months ago. It's called PowerSpec and it was not cheap! If anyone wants an lshw or a dmidecode for this system, I will be happy to send it to him/her off list.
Not working on windowz has absolutely no relationship to not working on your borked linux install!
The complaints about sound software from the system only started since I upgraded the whole system last week with zypper dup, so I suppose there is a bug in the sound software. It didn't complain for the months previous.
There is no way to make any determination as to what causes or caused problems on your system as no one has any idea what constitutes "your system" except that it is borked. -- (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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 5/9/20 12:56 AM, Doug McGarrett wrote:
On 5/8/20 1:21 AM, Adam Mizerski wrote:
W dniu 08.05.2020 o 07:08, Doug McGarrett pisze:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug
One of possibilities: pactl load-module module-loopback latency_msec=1000
This makes PulseAudio server to play back your mic on your speakers. The latency argument is optional.
To unload: pactl unload-module module-loopback
Tried the above from a user console. First try, answer was 28. Repeated line, answer was 29. But no sound came out anywhere. Ran the unload command without answer. Have been getting error notices regarding Skype and its component parts. Ran zypper dup and some of the error notices did not reappear, but at least one other did. (Even tho I did not tell it to, when I installed Skype it seems to want to start at boot-up. Since I cannot seem to get mic to work, I may uninstall Skype and just forget about it. I'll put up with it for a few more days, and then pffft!) --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 5/9/20 12:56 AM, Doug McGarrett wrote:
On 5/8/20 1:21 AM, Adam Mizerski wrote:
W dniu 08.05.2020 o 07:08, Doug McGarrett pisze:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug
One of possibilities: pactl load-module module-loopback latency_msec=1000
This makes PulseAudio server to play back your mic on your speakers. The latency argument is optional.
To unload: pactl unload-module module-loopback
Tried the above from a user console. First try, answer was 28. Repeated line, answer was 29. But no sound came out anywhere. Ran the unload command without answer.
Have been getting error notices regarding Skype and its component parts. Ran zypper dup and some of the error notices did not reappear, but at least one other did. (Even tho I did not tell it to, when I installed Skype it seems to want to start at boot-up. Since I cannot seem to get mic to work, I may uninstall Skype and just forget about it. I'll put up with it for a few more days, and then pffft!) --doug I told you a number of times now, that your system is the problem. Yet you insist to move on and try to solve problems on that borked system. And keep adding packages from home:/ repos. Help can be provided for systems that are systemwise OK. Not for the mess you have and insist to hold. We cannot make
Op zondag 24 mei 2020 21:18:37 CEST schreef Doug McGarrett: things work on that. Reinstall, listen to advice and follow it. The result sofar is a borked system and a borked user homedir. -- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-05-08 07:08, Doug McGarrett wrote:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug
If you just want to test if you can record something, just use arecord. First check which device to use. arecord -l and then record to a file arecord -f [format] -c [channels] -D hw:card,device -d [duration] <file> and play the file aplay <file> Here's is a USB Logitech G35 Headset that one of my kids use: $ arecord -l **** List of CAPTURE Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: CX20753/4 Analog [CX20753/4 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Headset [Logitech G35 Headset], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 record for 5 seconds from card 1 device 0 $ arecord -f S16_LE -c 1 -D hw:1,0 -d 5 soundfile.wav And play it $ aplay soundfile.wav -- /bengan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 5/24/20 4:03 PM, Bengt Gördén wrote:
On 2020-05-08 07:08, Doug McGarrett wrote:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again. There must be some way to plug in a mic and have some indication somewhere that it works. San someone please enlighten me? Thanx! --doug
If you just want to test if you can record something, just use arecord.
First check which device to use.
arecord -l
and then record to a file
arecord -f [format] -c [channels] -D hw:card,device -d [duration] <file>
and play the file
aplay <file>
Here's is a USB Logitech G35 Headset that one of my kids use:
$ arecord -l
**** List of CAPTURE Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: CX20753/4 Analog [CX20753/4 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Headset [Logitech G35 Headset], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
record for 5 seconds from card 1 device 0
$ arecord -f S16_LE -c 1 -D hw:1,0 -d 5 soundfile.wav
And play it
$ aplay soundfile.wav
This is the first answer I got, and it seems to be fairly full, but I have had a series of update errors in the last couple of days, since I did a zypper dup three days ago, all of them referring in one respect or another to skype. The latest one reads as follows: "Software Updates Timeout exceeded when accessing 'https://repo.skype.com.rpm/stable /repodata/repomd.xml'." I don't know if this affects mic testing or not. The example you provided when I ran it shows the webcam. I copied the file you mentioned, and it looked like something was happening, (the webcam lit up) but could not find soundfile.wav. (The first time is obvious--I did not try and record. The second time should have had the file, or what did I miss?) Here's the whole sequence, as copied from the console: doug@linux-4qnb:~> arecord -l **** List of CAPTURE Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 2: ALC887-VD Alt Analog [ALC887-VD Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Webcam [HP USB Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Device [USB Multimedia Audio Device], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 doug@linux-4qnb:~> aplay soundfile.wav (Had no apparent input) soundfile.wav: No such file or directory doug@linux-4qnb:~> arecord -f S16_LE -c 1 -D hw:1,0 -d 5 soundfile.wav ((The webcam lit up when I input this command.) Recording WAVE 'soundfile.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono Warning: rate is not accurate (requested = 8000Hz, got = 16000Hz) please, try the plug plugin <<<What does this mean? doug@linux-4qnb:~> doug@linux-4qnb:~> > aplay soundfile.wav soundfile.wav: command not found (This time there was input--maybe?) In a nutshell: Two problems (at least!) The skype complaints; the absence of soundfile.wav (which may mean that nothing came out of the webcam) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Doug McGarrett <dmcgarrett@optonline.net> [05-24-20 19:24]:
On 5/24/20 4:03 PM, Bengt Gördén wrote:
On 2020-05-08 07:08, Doug McGarrett wrote:
Is there some simple way to test a mic connected to the computer via usb port? When trying to set up skype, there was a test protocol, which I failed--it said the mic was not working. I haven't been able to get back to that particular routine again.
much removed ... [...] you will continue to have *many* problems until you correct your system, that includes logging in and running as <user> rather than root. and helping you solve your problems before then is a lost cause. Strongly suggest reinstall following accepted standards. -- (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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Adam Mizerski -
Bengt Gördén -
Carlos E. R. -
Doug McGarrett -
Knurpht-openSUSE -
Patrick Shanahan