I figured it out. For some reason, following the upgrade, the loopback
interface wasn't binding to 127.0.0.1. So whenever KDE made RPC calls (which
it does frequently for some things, including a lot of font-related things),
it hung, waiting to timeout.
Sorry to bother...
Dan Keshet
On Sund
[replying to all as op said he wasn't subscribed]
Dan Keshet wrote, On 2006-11-12 16:35:
I did an apt-get upgrade, upgrading both xserver-xorg (7.0-7.1) and kde
(3.5.4 to 3.5.5). Following this, I had trouble starting the xserver,
which was fixed by updating my xorg.conf to use the new
/usr/sha
I assume you're using unstable...
George Adamides:
> Hello
> I am following the instructions from a paper to install and start KDE. I
> managed to install it and now I am trying to make it work...When I type
> startkde I get the following message
>
> :~# startkde
>
> xsetroot: unable to open disp
User Debian wrote:
> 1. In ~/.xsession I have only one line "exec startkde"
I know you already solved your problem but I wanted to comment upon
this. You really probably want another line above it.
#!/bin/bash --login
exec startkde
Then make sure it is executable to have effect.
chmod a
Hallo everybody.
First of all -- thanks really A LOT to David! It finally works.
Stupid me -- one typo in /etc/network/interfaces and "lo" was not started.
Once again - thank you all for your replies,
Roman
Hi,
I remember having a similar problem some time ago: On start, KDE would freeze
in the initializing screen. I am not shure about the background with mouse
pointer and the .xsession-errors file, though.
However, I solved this problem by removing some leftover KDE session file. I
am not sure w
On Mon, 22 Aug 2005 18:38:32 +0200
User Debian <[EMAIL PROTECTED]> wrote:
> Dear All,
>
> My question concerns starting KDE 3.3 on my fresh Etch installation
> (i386 on AMD Athlon machine).
>
> 1. In ~/.xsession I have only one line "exec startkde"
>
> 2. X starts without any problems and Disp
On Tuesday 23 August 2005 13:10, User Debian wrote:
> > The problem, as far as I can see is the DCOP communication problem.
> >
> > Check /etc/hosts, specifically, and ensure you have not messed with the
> > line
> >
> > 127.0.0.1 localhost
> >
> > and that your system hostname (uname -n) is resol
> The problem, as far as I can see is the DCOP communication problem.
>
> Check /etc/hosts, specifically, and ensure you have not messed with the line
>
> 127.0.0.1 localhost
>
> and that your system hostname (uname -n) is resolvable by your chosen domain
> name resolution system (DNS/files/NIS
On Monday 22 August 2005 17:38, User Debian wrote:
> Dear All,
>
> 5. After killing the X with Ctrl+Alt+Bsp the .xsession-errors file reads:
> --
> Xsession: X session started for at Mon Aug 22 18:28:16 CEST 2005
> ICE default IO
10 matches
Mail list logo
