This is just a data point because these observations are semi-irreproducible results:
sound. Sometimes the sound cuts out and no sound producing applications are able to use sound. I do not see any evidence for what happened in /var/log/messages. If there is something else I should look at, it would be nice to know. Nothing in the alsa stuff jumps out as a way to trace the activity, so I don’t know how to provide any diagnostic info. After several reboots, it eventually restores itself and works correctly.
video. Sometimes when I boot up, the secondary monitor has residual trash on the boot up/login screen. Other times, it is switched off entirely and I only get one monitor functioning when the desk top is finally up. Rebooting a few times clears this up, too.
The clear-up reboot requires a full shut down, not just a KDE restart. That is always ineffective when these problems present themselves, so these are likely driver level issues.
I do not know where developers get their suggestions, but here’s one: for each subsystem, have some well-named “I need diagnostics for this” thing available under the yast administrator stuff. That would turn on diagnostics for the subsystem. Then, I could turn it on for X and get something a bit better than the .xsession-errors (which showed nothing obvious for this problem) and for sound (aka “alsa” for those in the know). So, for now, if I have anything useful, I do not know what or where. Sorry.
I was about to try your “lsof” (list open file) suggestion, but I’ve got to reboot again. Firing up a console yields a popup:
> KLauncher could not be reached via DCOP
This started today. As far as I know, you gotta recycle KDE.
Of course, the sound is working at the moment…Just not
app. starts in KDE. I will also take your suggestion to where
developers hang out. Thanks!
Note in KDE you can control the order of sound devices under Kmenu (kickoff application launcher) > Configure desktop > multimedia … I always use the xine backend, and I replace the Novell/SuSE-GmbH packaged version of libxine1 with the packman packager packaged version of libxine1 (where one can tell packman packaged versions by the “pm” in the version number).
I needed to run this many times, at different times, with different apps using my audio, before I could figure it out what it means on my PC. If you can run that once on your PC, and have it all figured out, then my hat is OFF to you.
I ran it twice: once when I could run sound apps, once when not and noted the difference. Two opens on controlC1 was obvious. FYI, I’ve been playing with computers since before the beginning of time. (aka Jan 1, 1970)
Anyway, next time it locks up, I’ll try a ``su -c “pkill -TERM pulseaudio”’’, pending confirmation that I should just nuke the whole package.
I confess I tried Gnome out on my sandbox PC for a few months, removing it only a week or so ago. I really liked Gnome’s interface (aside from double click which I hated, and I disliked its YaST implementation, as KDE has IMHO a superior one). I liked Gnome so much I went around changing my KDE desktops to look like Gnome. But in the end I removed Gnome from my sandbox PC and did NOT update any of my other PCs to Gnome despite my liking its appearance. Why? Its sound implementation with pulse audio is simply too quirky and was far too irritating. KDE does NOT have the sound problems that Gnome has.
… anyway, Murphy says you have KDE, even though the characteristics you describe read to me to be like Gnome. Is Murphy correct? (ie you have KDE ? ) … or have you installed both desktops ?
Sometimes, I fail to knock out Gnome when I do an install and I have both. Not this time – plain KDE, plus the non-desktop Gnome stuff that seems to come whether you want it or not. The pieces that Yast finds associated with “gnome” and are installed are: – ahem – below. I started out thinking there would not be that many. I was wrong. I do kind-of wonder how relevant many of these are in a non-Gnome environment…How they all got there would be a question for the openSuSE packaging guys.
By chance do you have pulse selected as your main audio device under Kickoff Application Launcher > Configure Desktop > Multimedia ?
Beats heck out of me. When I fire up the “configure desktop” application, my “sound/multimedia” selection shows that the sound system is enabled, runs with real time priority and should auto-suspend after 5 seconds (“General” tab). The hardware tab shows that it should auto-detect devices. There should be only one device and it is on the motherboard.
Instead I recommend to add the packman repository such that one has 4 and only 4 repositories: OSS, Non-OSS, Update and packman and just those 4. No others. None. Only those 4: OSS, Non-OSS, Update and packman. Adding more than those 4 can cause problems.
Then install via YaST and do NOT use the 1 click install. If one uses the 1 click install and is not careful one can add more repositories and that will cause problems. So don’t use it.
Not “one click install” but “one script validation”.
Also, because I am unfortunate enough to be using the disparaged
“nvidia” video controller chip, I do need some nvidia repo.
I had “debug” and “source” repos also because I figured it would
be useful when things go awry. They always do. So I am down to
those four, plus the DVD “repo”. These are all now ordered and
prioritized per the Please observe carefully the Priority settings! comment.
The problem now, of course, is telling Yast it needs to go out and get the packages from the new sources.
Looking at the YaST2 GUI, there doesn’t seem to be an obvious
trivial way to tell it to do that…