> 293, Kde-config Incorrectly Creates a Profile Folder in the > System root directory > umm no info , could explain more details The bugzilla contains good details. The problem is that when kde-config is used in read mode there should be nothing else happening other than reporting the requested information. kde-config will create a profile directory all the time of one does not exist. When used in a non-interactive shell script, the default location is the system root (not user root) and kde-config will create a profile directory in the system's file system. Repeatable 100%. KDE 3.5.10 and KDE do this too. > 385, Unmounted removable device icons do not appear on the > desktop > this happen from kde original proyect, i > dont nkow but only happen with devices that not listed on > fstab, > I will explain that; since hal&udev handles auto-remove > devices and mount, fstab file not necesari list&handle > all devices rules mount, so then if device not appears in > fstab, desktop icon umount not appear on desktop, only wen > hal mount , device icon appears, so then this ist a problem > of out-date desktop proyect kde, that its not prepared for > new free-desktop & dev-hal up-to-day rules.. Might be HAL related, but as I stated in the bugzilla report, I never have this problem in 3.5.10. We had a conversation in the list about the problem in December and Tim agreed this is a bug: http://trinity-devel.pearsoncomputing.net/?0::830. > 387, Kicker/Panel Clock Font Display Looks Weird > no info from me.. Discussed in the list: http://trinity-devel.pearsoncomputing.net/?0::841. A solution is provided in the bugzilla: to provide a check box to disable/enable transparency. > 388, KDESU Dialog Box Behavior > please provide more details I added a screen grab to the bug report. > 393, Incorrect kdesu Behavior When Opening Kate > err this will happen realy? Yes, that happens, really. :) Read my comment from March 29 in the bugzilla for a possible cause. > 394, Problems with DCOP After Using kdesu > ok this are from kde 3.5 .. some saint > google related topics but nothing that i found yet The problem never occurs in KDE 3.5.10. > 427, NumLock light does not reflect actual state > also from kde 3.5 too, no info, some > saint google related topics but nothing serious.. kde never > take care about that.. Probably so. Num Lock retention never worked in KDE 3.5.10 for me either. My best approach was to always select the Leave Unchange check box. That seems to produce the least problems. The problem is not entirely KDE either. The kernel is set to to toggle Num Lock off. X is set to toggle Num Lock off. Darrell