Comment #3 on issue 29927 by [email protected]: Use .kde4 on KDE 4 systems http://code.google.com/p/chromium/issues/detail?id=29927
[ Clickable version of the patch link above: http://tinyurl.com/yl64g4e ] Ah yes, we probably do need some logic that works something like that. We might not want to just hardcode .kde4 though, as more recent systems are starting to use just plain old "KDE" to refer to KDE 4. I'm not sure whether the .kde4 directory is among the things that are switching back or not. If not, then we could just take the patch as-is. Otherwise, there's an environment variable $KDE_HOME that might contain a value pointing at the right place, and there's also a program that can be run to get it as well (kde4-config --localprefix). Actually, technically, we should always run the program rather than hardcode any value, but of course the program itself has a 4 in it... in KDE 3 it was named kde-config. I'd love to work on this but I'm pretty busy trying to graduate (so I can come work on this stuff full-time). This looks like a job for somebody with a lot of VMs though, to test different versions of KDE. Hopefully this information will help. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
