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)