Its either a flaw in the way permissions are set up or in KDE itself. I have similar problems. For instance, now I can't setup the colors of KDE. I only get the default gray with blue/gray header. This always happens after I upgrade stuff like KDE (but I'm not convinced that it isn't just certain upgrades in general). I often wonder if it's not how SuSEconfig works either. I wish they'd address this issue. But given the move, christmas, and the fact that they're most likely understaffed (which would also explain why I haven't heard back from my support submission in over a week - so much for 90 days install support - I know, I know - it's only for installation to get a default sys working). Don't get me wrong, I am very fond of SuSE, I just wish the DB was a little more complete. I can't believe that were the only two that have had this problem. Gets frustrating! Cheers, Curtis On Sunday 23 December 2001 22:02, Hydra wrote:
I now have 7.3 installed and updated completely - 2.4.16, 2.2.2.
But my user account wasn't saving my settings (window size, location) at all. (same problem in 2.2.1 and 2.1) So I set aside /home/hydra/.kde and symlinked it to .kde2 and then it remembered sizes/locations.
But now it saves the sessions cumulatively. In other words when I log off with one konsole & konqueror and save settings, when I log in I get 6 konquerors and 5 konsoles, different sizes from old sessions.
AND MY SUSE MENU *POP* MAGICALLY TURNED TO A FOLDER ICON, WITH NOTHING IN IT! WTF?!?! HAAAALLLP! My *whole*Suse*menu* is gone, as well as Work and Admin menus! How does this system work?
Also I would like my user account and my root account K settings to be the same. (color, theme, etc) In Suse7.2 I tried symlinking most root .kde2 files and dirs to my user files (not tmp or socket), but THEY STILL REMAINED DIFFERENT SETTINGS. How can this be? Spirits and ghosts?
I tried moving config files from root to /opt/kde/share, but KDE ERASED THEM THERE for me.
While we're talking, I wonder why my parallel port's not being recognised. IBM Stinkpad a22p. It was set to ECP in BIOS and the ECP module was loading, but I changed BIOS to EPP, and the log is silent of hardware or driver notice.
Is a change needed in modules.conf? With Suse's different structure, I'm a bit afraid of mucking. No apparent way to config parallel port. Why make an intermediate meta-layer (char-major)?
My scanner's not being recognized, after I went through the Suse Config Guide, but that's another story.
Getting concerned as I need to be working rather than configuring.