[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DCOP problem after Etch with Kde upgrade



On Sat, Feb 17, 2007 at 08:50:46 +0000, john gennard wrote:
> Florian Kulzer wrote:

[...]

> >The DCOP server itself is responsible for creating the file that is
> >mentioned in your error message (as far as I know).
> >
> >Something fundamental seems to be wrong with your KDE. With Etch being
> >frozen I would not expect that a dist-upgrade can make a difference, but
> >I would try it nevertheless. You might simply have an inconsistent
> >combination of KDE packages right now, with some old packages still
> >hanging around. (Upgrading at the wrong moment could also cause a
> >situation like this; in such a case another upgrade at a later time
> >might be enough to fix everything.)
> >
> I can't see any old Kde packages hanging around. A dist-upgrade
> has been run (another 30 Mb just covering two days, most accounted 
> for by Kde packages!) - as you expected it has made no significant 
> difference although there is a slight change in the behaviour of the 
> 'frozen' Kde blue screen.
> 
> Also, in the Xorg log file there is an error message:-
> 	"(EE) AIGLX: screen 0 is not DRI capable"
> (I missed this earlier).

I am pretty sure that this does not cause the DCOP problem.
 
> Now, I intend to upgrade another box to see what happens and also
> to ask on the Kde list in case others have seen this difficulty.

I kind of lost track of this thread; did we already talk about the
permissions of the /tmp directory? They should be like this:

$ ls -ld /tmp
drwxrwxrwt 16 root root 8192 2007-02-19 18:49 /tmp

-- 
Regards,
          Florian



Reply to: