|fungos||when kde4 debuts?|
|bsdfox||fungos: sometime in october I think|
|ori||is there a way to disable kde's "an application has crashed" notification?|
typically i'm pretty aware of application crashes, so it's just adding insult to injury, as if you tripped and broke your leg and someone said: "look, you broke your leg!"
|hydrogen||don't install drkonqi? :)|
|ori||oh, is that the culprit?|
|hydrogen||thats the app that does it|
|blackdog||isn't ironic that the KDE channel has relatively very few people with names that start with K compared to most other letters?|
i thought i'd start with a joke to break the ice
wow tough crowd
|qupada||blackdog: mine starts with q|
|blackdog||my point exactly|
|smileaf||<-- Super? =)|
|blackdog||im afraid i dont understand|
|action||smileaf hands blackdog a puppy.|
|smileaf||hands blackdog a puppy.|
|lhunath||I keep getting these really annoying delays followed by the error message:|
Session management error: Could not open network socket
what's going on?
when I strace it; the thing seems to be trying to connect to /tmp/.ICE-unix/3726 which does not exist.
mine's called 15237, not 3726
ksmserver is loaded ..
doesn't happen with xmessage, though, so not all x client suffer this delay
and so does vim because it tries to connect to the clipboard .. -_-
|nocti||i get this on starting k3b, konqueror: "kdeinit: DCOPServer could not be started, aborting."|
|jabhatti91||maybe your dcop server died...|
|bsdfox_||nocti: I had that happen one time, I ended up reinstalling KDE :\|
|Renze||bsdfox_: talk about overkill|
|bsdfox_||Renze: probably :)|
I tried to fix it for a couple days but then I gave up.. it was on a media box that I didn't need to use anyways
|nocti||bsdfox_: i'll try to install kdcop. :)|
|wolsni||nocti: kdcop is not a dcop server|
wolsni: what could be pulling it? i'm using gentoo
|wolsni||i'm with whoever suggested your dcop server might have crashed|
nocti: if you run 'ps aux | grep dcop' is a dcopserver listed?