E. Liddell composed on 2014-12-14 07:29 (UTC-0500): > On Sun, 14 Dec 2014 01:26:25 -0500 Felix Miata wrote: >> Mike Bird composed on 2014-12-13 21:26 (UTC-0800): >> > Does "apt-get --reinstall install kdelibs4c2a-trinity" help at all? >> Helped a lot! KControl works. :-D http://tinyurl.com/nz37aer :-D How did you >> figure out that's what needed doing? $SUBJECT produced 0 hits from Google. :-p > The error suggested it was having difficulty finding the symbol definitions for a > common TDE graphical component. The logical place for such a component to > be defined is the libs package, and the easiest way to deal with a broken package > is usually to reinstall it and hope the package mangler gets it right this time. ;) Mike Bird composed on 2014-12-14 07:39 (UTC-0800): > kdelibs4c2a-trinity was by far the most likely candidate. Downloaded > the source for that package and checked that KListView::selectAll is > defined there. I get that *some* lib was a likely candidate, and that reinstalling the right package should be the solution. What I don't see is the connection between the error message and the package name string "kdelibs4c2a" that Mike correctly identified. > I suggest you might want determine how the problem arose - whether by > user error or disk error or malicious attack or otherwise. Likely a combination of user error and package mangler error. I had tried to update to v14, but after an hour of seeing upgrade candidate messages scroll up the screen without noticing evidence of actual progress, I Ctrl-C'd out, restored the old sources.list, and from there dont' remember what I did and didn't do. I've since done an update that included somewhere between 250 & 300 packages, and all seems good now with that installation. As it's a multiboot machine, with old HD and new Asus A88X-Pro motherboard/RAM/CPU/video, I have to get all working acceptably, and I've hit another big snag Google isn't helping with. The owner's vision is somewhere in the bottom 2%, very poor. One of his workarounds is using a 42" TV screen. Another was apparently installing/configuring some accessibility package that made his mouse pointer easier to find in KDE3 in openSUSE 11.3. Using his 11.3 user data for a fresh 13.1 installation, his mouse pointer totally disappears as soon as login painting completes, and it stays gone. With a virgin user the pointer works normally. I've tried going through .kde/share/config/ looking for mouse configs to zero out, but that hasn't worked, and neither has looking for suspect package names among a complete package list. I found he had downloaded 140787-LargeCursors.tar.bz2 and installed that, but no help from it either. Also, many sound devices are showing up in lsmod, apparently confusing both automatic and manual configuration attempts. Alsactl init in Squeeze returns instantly, writing nothing anywhere I can find. According to YaST2 on openSUSE 13.2, there are 2 "cards", ATI as card0 using snd-hda-intel, and FCH Azalia as card1, also using snd-hda-intel. :~( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
snd 87947 12 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel snd_hda_codec 151970 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller snd_hda_codec_generic 77129 1 snd_hda_codec_realtek snd_hda_codec_hdmi 55740 1 snd_hda_codec_realtek 80983 1 snd_hda_controller 35103 1 snd_hda_intel snd_hda_intel 34475 2 snd_hwdep 13602 1 snd_hda_codec snd_pcm 116857 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller snd_timer 33609 1 snd_pcm soundcore 15047 2 snd,snd_hda_codec