That’s all good, but often error messages are too general or from a process that is too deep to be understandable by a user. If that doesn’t help, I usually use a few keywords on google search (as few as possible). I often leave out “openSUSE” to cast the net wider, and usually put linux as the first.
I fought Kmail for waaay too long trying to try different configs and bla bla and reading more about what works and none of it works for me.
Yes, to much unrewarded loyalty in this case. I gave up on kmail when the KDE developers followed up a working version with one that was really buggy, although it had spent much time in the “beauty parlour”. That really was style over substance! Then it probably fell foul of the semantic desktop, or akonadi or whatever. I ditched it for Thunderbird which had the added benefit of being cross-platform, and never looked back.
Part is my fault because I get annoyed with the CLI
Why is that your fault(?) It’s mainly productive for those who use it a lot, such as [real-world] system administrators, system engineers. If it was easy, the GUI wouldn’t have evolved as a productivity aid, which empowered the non-technical users in work and at home.
just over the last couple days I’ve been really fighting the sound system and the explanations of the different layers is not well integrated. Not only that, but I feel there are too many layers that just don’t seem to want to get along. I’m trying to do some recording. I also want full ability to adjust all of my output. JACK will do all of that, but all of my Pulseaudio won’t start.
The linux sound documentation is appalling. It’s written by system engineers, who can’t see the forest for the trees. It wasn’t that easy on Windows 95 and it helped if one had some experience as a sound engineer (BTW I don’t). As far as the applications go, Linux has just about caught up with that era. However now there are two sound servers to complicate matters.
JACK for professional level audio (very low latency), and PulseAudio (low enough latency for simple everyday audio), where the two servers do not cohabit well unless they each use a different sound device, i.e. separate sound cards/chips. The simple answer is to have one or the other - not both.
If you must have both, and share the same sound card, you must suspend P/A in order to use JACK, but on 13.1 I found that shutting down JACK doesn’t cleanly activate P/A. Welcome to frustration and the CLI, in order to kill P/A, check its status and restart it.
Are you also trying to use Rosegarden, by any chance?
ALL OF THIS STUFF WORKED IN 12.2 KDE 64 bit!!!
See, no need to SHOUT! I have some sympathy for you since I recently abandoned 12.2 KDE 64bit where it was working just fine - but not at the beginning of 12.2 necessarily. It had to go for security reasons and its partial implementation of systemd which eventually started to exhibit a little instability on my system.
