problems starting KDE - Debian

This is a discussion on problems starting KDE - Debian ; 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 Display Manager window appears (I ...

+ Reply to Thread
Results 1 to 7 of 7

Thread: problems starting KDE

  1. problems starting KDE

    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 Display Manager window appears (I
    tried xdm and kdm)

    3. After I enter my login and password, the splash screen appears.

    4. Splash screen stays at the "Initializing system services" stage for
    about 2 min and then (without passing the rest) I see the background
    with a mouse pointer. That's it.

    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 error handler doing an exit(), pid = 22301, errno = 95
    startkde: Starting up...
    kdeinit: Shutting down running client.
    WARNING: DCOP communication problem!
    QPixmap: Cannot create a QPixmap when no GUI is being used
    QPixmap: Cannot create a QPixmap when no GUI is being used
    Xlib: connection to ":0.0" refused by server

    Xlib: No protocol specified


    QPixmap: Cannot create a QPixmap when no GUI is being used
    QPixmap: Cannot create a QPixmap when no GUI is being used
    kbuildsycoca running...
    kded: Fatal IO error: client killed
    DCOP aborting (delayed) call from 'anonymous-22675' to 'kded'
    kded: ERROR: Communication problem with kded, it probably crashed.
    Xlib: connection to ":0.0" refused by server

    Xlib: No protocol specified


    kdeinit: Can't connect to the X Server.
    kdeinit: Might not terminate at end of session.
    Xlib: connection to ":0.0" refused by server

    Xlib: No protocol specified


    kcminit: cannot connect to X server :0
    Xlib: connection to ":0.0" refused by server

    Xlib: No protocol specified


    knotify: cannot connect to X server :0
    ERROR: KUniqueApplication: Registering failed!
    ERROR: Communication problem with knotify, it probably crashed.
    -----------------------------------------------------------

    Other win-manager (e.g. wmaker and xfce) work without any problem. I
    think, something goes wrong when xlib refuses KDE the connection to
    ":0.0". Why does it do so?
    It does not help if I put "xhost +" in the ".xsession" file BEFORE
    "exec startkde".

    I would appreciate any help.

    Thanks in advance

    Roman

  2. Re: problems starting KDE

    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 error handler doing an exit(), pid = 22301, errno = 95
    > startkde: Starting up...
    > kdeinit: Shutting down running client.
    > WARNING: DCOP communication problem!
    > QPixmap: Cannot create a QPixmap when no GUI is being used
    > QPixmap: Cannot create a QPixmap when no GUI is being used
    > Xlib: connection to ":0.0" refused by server
    >
    > Xlib: No protocol specified
    >


    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, whichever you are using).

    David

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.1 (GNU/Linux)

    iD8DBQBDCtbXOIrGtzS07WgRApAzAKCID23fstGP2D5MLIbyOW ZI2+gpPACgvag2
    8PjOKdmwf6wcZQbnqNCFWV8=
    =LMku
    -----END PGP SIGNATURE-----


  3. Re: problems starting KDE

    > 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, whichever you are using).


    Hi David

    Following your advice, I have checked /etc/hosts -- only one line
    127.0.0.1 localhost
    is there, which is logical: I use hdclient, so all this stuff is
    generated automatically
    after each boot up.

    Also uname -u gives the same as in /etc/hostname
    host resolves the name without any problem (so, DNS works well)

    So, I am quite desperate

    Thanks anyway,

    Roman

  4. Re: problems starting KDE

    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 resolvable by your chosen
    > > domain name resolution system (DNS/files/NIS, whichever you are using).

    >
    > Hi David
    >
    > Following your advice, I have checked /etc/hosts -- only one line
    > 127.0.0.1 localhost
    > is there, which is logical: I use hdclient, so all this stuff is
    > generated automatically
    > after each boot up.
    >
    > Also uname -u gives the same as in /etc/hostname
    > host resolves the name without any problem (so, DNS works well)
    >
    > So, I am quite desperate
    >
    > Thanks anyway,
    >
    > Roman


    Oh, and if you've got any firewall, particularly on the loopback interface,
    drop it.

    Check also that ping 127.0.0.1 replies ok, sometimes people had problems with
    lo coming up.

    David

    --
    -------------------------------
    Your manuscript is both good and original, but
    the part that is good is not original and the part
    that is original is not good. -- Samuel Johnson
    -----BEGIN GEEK CODE BLOCK-----
    Version: 3.12
    GCS d- s-: a-- C++ UL++++ P L+++ E--- W++ N+ o+ K- w---
    O M V- PS+ PE+ Y+ PGP t 5- X+ R- tv+ b+ DI++ D+
    G+ e++ h r% y++ s-: e++
    ------END GEEK CODE BLOCK------

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.1 (GNU/Linux)

    iD8DBQBDC5gVOIrGtzS07WgRAjPAAJ9mM7wa9mdWBL+3Z0IMa4 50oBMUfACg16Pv
    x+zs4j1/xL0O8VZwTaOgsXs=
    =o5Ru
    -----END PGP SIGNATURE-----


  5. Re: problems starting KDE

    On Mon, 22 Aug 2005 18:38:32 +0200
    User Debian 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 Display Manager window appears (I
    > tried xdm and kdm)
    >
    > 3. After I enter my login and password, the splash screen appears.
    >
    > 4. Splash screen stays at the "Initializing system services" stage for
    > about 2 min and then (without passing the rest) I see the background
    > with a mouse pointer. That's it.
    >
    > 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 error handler doing an exit(), pid = 22301, errno = 95
    > startkde: Starting up...
    > kdeinit: Shutting down running client.
    > WARNING: DCOP communication problem!
    > QPixmap: Cannot create a QPixmap when no GUI is being used
    > QPixmap: Cannot create a QPixmap when no GUI is being used
    > Xlib: connection to ":0.0" refused by server
    >
    > Xlib: No protocol specified
    >
    >
    > QPixmap: Cannot create a QPixmap when no GUI is being used
    > QPixmap: Cannot create a QPixmap when no GUI is being used
    > kbuildsycoca running...
    > kded: Fatal IO error: client killed
    > DCOP aborting (delayed) call from 'anonymous-22675' to 'kded'
    > kded: ERROR: Communication problem with kded, it probably crashed.
    > Xlib: connection to ":0.0" refused by server
    >
    > Xlib: No protocol specified
    >
    >
    > kdeinit: Can't connect to the X Server.
    > kdeinit: Might not terminate at end of session.
    > Xlib: connection to ":0.0" refused by server
    >
    > Xlib: No protocol specified
    >
    >
    > kcminit: cannot connect to X server :0
    > Xlib: connection to ":0.0" refused by server
    >
    > Xlib: No protocol specified
    >
    >
    > knotify: cannot connect to X server :0
    > ERROR: KUniqueApplication: Registering failed!
    > ERROR: Communication problem with knotify, it probably crashed.
    > -----------------------------------------------------------
    >
    > Other win-manager (e.g. wmaker and xfce) work without any problem. I
    > think, something goes wrong when xlib refuses KDE the connection to
    > ":0.0". Why does it do so?
    > It does not help if I put "xhost +" in the ".xsession" file BEFORE
    > "exec startkde".
    >
    > I would appreciate any help.
    >
    > Thanks in advance
    >
    > Roman


    I googled DCOP for you and tried the commands on my sarge machine, and it would appear that I don't have DCOP myself.

    I am a new Debian user and this might assist you thanks to several people from the debian-user lists They found what i was missing.

    I have had several problems one being that I couldn't connect to local host and the other being that I couldn't get anything KDE to work when I was connected to the net through

    This may not help you, but it could also be a DNS issue I was run through several procedures but the crux of it was that I had to add to:- /etc/hosts to read like this......... 127.0.0.1 localhost.localdomain localhost

    That /etc/nsswitch.conf has a line like this:

    hosts: files dns



    That /etc/network/interfaces by adding these lines:

    # The loopback network interface
    auto lo
    iface lo inet loopback


    Nothing of mine had anything like this, and maybe that was because DCOP isn't installed or entered or what. But I am working on looking through this.

    So maybe check these things and that might help you as well. But i would also depend on your firewall. I disabled mine to work through this and then reenabled it.

    Charlie.


    +++++++
    Registered Linux User:- 329524
    +++++++++++++++++++++++++++++++++++
    One changes from day to day . . . every few years one becomes a new being. ..............George Sand

    ***********************************************
    Trying Linux Debian Sarge
    _____________________


    --
    To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  6. Re: problems starting KDE

    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

  7. Re: problems starting KDE

    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+x ~/.xsession

    The reasoning for this is so that your ~/.bash_profile is loaded at
    login time. Otherwise it won't be. (If you are using zsh or other
    shell then change the #! line appropriately to match.)

    For full details of the issues see Debian Bug#250765 where a long
    discussion is archived.

    Bob

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.1 (GNU/Linux)

    iD8DBQFDEnzn0pRcO8E2ULYRAhkyAJwPMWZGrQlN6qUQ8Ddevl ZlJQxY5wCfR0Id
    9azN5otezMDEclLlG/5UtDw=
    =vva5
    -----END PGP SIGNATURE-----


+ Reply to Thread