Summary: | kdeinit: kio_* problems with 3.1.4 and 3.1.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.keen-web.de/none-of-your-business/tmp/bugreport | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
mail
2004-02-20 03:45:24 UTC
Here's a dumb question: After you emerged KDE, did you run "env-update"? I have KDE installed on over 20 boxes doing nothing more than the typical emerge scenario and have never once had any problem like this. Note that i'm not trying to downplay this problem, just point out that there's got to be something obvious that we're missing here that's causing this problem. Basically, I never ran "env-update", because I thought that portage will do that for me, if really necessary. I have Gentoo for about a year now, reinstalled it about four of five times and I never had the urge to do this...so env-update is something I completely forgot in the past (but never got in trouble because of that). BUT, of course: I env-updated regulary since I noticed and troubleshooted the problem. Just re-emerged qt, kdelibs and kdebase yesterday (once more *sigh*) and after every emerge I did a $ env-update && source /etc/profile Tell me if you need anything more to know - for now, I just have no idea what else could matter :( Tonight, I will try to emerge the complete KDE-3.1.5 Stuff again. What would be the best order to do this? 1. QT 2. kdelibs 3. kdebase 4. <other-kde-packages>? Would this be okay? I will do an env-update and source /etc/profile after each step so I can be sure that the paths and environment variables are allright. PS: I also etc-updated my config files regulary so this shouldn't be a problem neither. PPS: Do you think it's a Gentoo related or pure KDE problem? Could you try to log in from a console and not run kde. Then delete /tmp/ksocket-username, /tmp/kde-username Possibly even delete the X socket and mcop etc stuff. unable to replicate this. It seems like a complete local problem, and I don't know how we can help you fix it or troubleshoot it. Sorry :( |