Announcement

Collapse
No announcement yet.

"Could not start ksmserver. Check your installation." evil white dialog box

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    "Could not start ksmserver. Check your installation." evil white dialog box

    Help?

    I know what I did. I did:
    dpkg-reconfigure xserver-xorg

    Then I restarted X and didn't like the flickering and the resolution and the dead 2nd monitor, so I did:
    nvidia-xconfig

    Then I restarted X and logged into KDE and wanted to re-add my old twinview setup and game-/emulator-friendly metamodes by hand, so I did:
    Code:
    $sudo kate /etc/X11/xorg.conf
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.    
    Error: "/tmp/ksocket-username" is owned by uid 1000 instead of uid 0.  
    kate(4669) KToolInvocation::klauncher: klauncher not running... launching kdeinit
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.         
    Error: "/tmp/ksocket-username" is owned by uid 1000 instead of uid 0.       
    kdeinit4: Shutting down running client.                     
    kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher          
    Error: "/tmp/ksocket-username" is owned by uid 1000 instead of uid 0.       
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.         
    kdeinit4: preparing to launch /usr/bin/kded4                  
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.     
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.         
    kdeinit4: preparing to launch /usr/bin/kbuildsycoca4              
    kbuildsycoca4 running...                            
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.     
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/local/share/applications/Google-googleearth.desktop" is not compliant with XDG standard (missing trailing semicolon).                         
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/local/share/applications/Google-googleearth.desktop" is not compliant with XDG standard (missing trailing semicolon).                          
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/local/share/applications/renoise.desktop" is not compliant with XDG standard (missing trailing semicolon).                               
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/opera.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/opera.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/lmms.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/lmms.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/mousepad.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/inkscape.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4703) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/kde/krita.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
    kbuildsycoca4 running...
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/local/share/applications/Google-googleearth.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/local/share/applications/Google-googleearth.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/local/share/applications/renoise.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/opera.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/opera.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/lmms.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/lmms.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/mousepad.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/inkscape.desktop" is not compliant with XDG standard (missing trailing semicolon).
    kbuildsycoca4(4707) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/kde/krita.desktop" is not compliant with XDG standard (missing trailing semicolon).
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update
    kdeinit4: preparing to launch
    Startup is noticably delayed by all these messages, but kate (or dolphin or whatever I used) starts.

    A b&w xmessage pops up saying: "Could not start ksmserver. Check your installation." When I click "OK" on it, I'm plonked back into the GDM login.

    When I don't I can continue sort-of-normally, except the keyboard might temporarily die on me (or just KDE keyboard shortcuts).

    I restored the backup of my original xorg.conf, but it makes no difference...

    -----------

    Edit: I manually fixed all the "missing trailing semicolon" errors. Now the output to "sudo kate" (or sudo dolphin, whatever, just has to be a KDE app) is just this:

    Code:
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.
    Error: "/tmp/ksocket-username" is owned by uid 1000 instead of uid 0.
    kate(14120) KToolInvocation::klauncher: klauncher not running... launching kdeinit
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.
    Error: "/tmp/ksocket-username" is owned by uid 1000 instead of uid 0.
    kdeinit4: Shutting down running client.
    kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
    Error: "/tmp/ksocket-username" is owned by uid 1000 instead of uid 0.
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.
    kdeinit4: preparing to launch /usr/bin/kded4
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.
    kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
    kbuildsycoca4 running...
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
    kbuildsycoca4 running...
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update
    kdeinit4: preparing to launch
    But I still get the same xmessage dialog box about ksmserver.

    -----------

    Edit 2: When I leave the xmessage hanging there and run another "sudo kate", all I see is:

    Code:
    Error: "/var/tmp/kdecache-username" is owned by uid 1000 instead of uid 0.
    Error: "/tmp/kde-username" is owned by uid 1000 instead of uid 0.
    Error: "/tmp/ksocket-username" is owned by uid 1000 instead of uid 0.
    (That's normal, although I'm not sure I recall the /tmp/ksocket-username bit)

    -----------

    Edit 3: The message is triggered by /usr/bin/startkde, way down in line 400something:

    Code:
    # finally, give the session control to the session manager
    # see kdebase/ksmserver for the description of the rest of the startup sequence
    # if the KDEWM environment variable has been set, then it will be used as KDE's
    # window manager instead of kwin.
    # if KDEWM is not set, ksmserver will ensure kwin is started.
    # kwrapper4 is used to reduce startup time and memory usage
    # kwrapper4 does not return useful error codes such as the exit code of ksmserver.
    # We only check for 255 which means that the ksmserver process could not be 
    # started, any problems thereafter, e.g. ksmserver failing to initialize, 
    # will remain undetected.
    test -n "$KDEWM" && KDEWM="--windowmanager $KDEWM"
    kwrapper4 ksmserver $KDEWM 
    if test $? -eq 255; then
     # Startup error
     echo 'startkde: Could not start ksmserver. Check your installation.' 1>&2
     test -n "$ksplash_pid" && kill "$ksplash_pid" 2>/dev/null
     xmessage -geometry 500x100 "Could not start ksmserver. Check your installation."
    fi
    However, it does not appear at KDE start. KDE starts fine. It's only when I sudo something that it pops up.

    #2
    Re: "Could not start ksmserver. Check your installation." evil white dialog box

    Oh, right! Another thing I did shortly before this started happening was upgrade to KDE 4.2.3 (via: deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu jaunty main).

    Is there a sane way to downgrade to 4.2.2 again? I've been trying to, starting with kdebase, but Synaptic wouldn't let me.

    Hälp

    Comment


      #3
      Re: "Could not start ksmserver. Check your installation." evil white dialog box

      Have exactly the same problem, getting the xmessage: "Could not start ksmserver. Check your installation." Also get very similar error messages when I do sudo kate, sudo konqueror and sudo dolphin, but I don't get the xmessage if I just do kate, konqueror or dolphin without the sudo. If I click the okay box of the xmessage, kdm restarts.

      To recover I reinstalled my 20 days old partition image - everything OK. Then I updated all the software - 176 files if I remembered correctly - and I am back to the same problem.

      Hjälp!

      Comment


        #4
        Re: "Could not start ksmserver. Check your installation." evil white dialog box

        Hürm... did that updating take you all the way to KDE 4.2.3?

        Comment


          #5
          Re: "Could not start ksmserver. Check your installation." evil white dialog box

          I aslo experience the same error when using sudo kate... and yes it happens after upgrading to KDE 4.2.3 but I used the Kubuntu-eprimental ppa... deb http://ppa.launchpad.net/kubuntu-exp...tal/ppa/ubuntu jaunty main

          Comment


            #6
            Re: "Could not start ksmserver. Check your installation." evil white dialog box

            Yes, I the updating took me to KDE 4.2.3 Decided to retrack and do the upgrade again except for the program I suspected kdm-4.2.3-0ubuntu-jaunty] (my present version is kdm-4.2.2-0ubuntu2). Was very pleased when I did not get the xmessage, even after a reboot. However, this morning the problem is back.

            Comment


              #7
              Re: "Could not start ksmserver. Check your installation." evil white dialog box

              Forgot to mention that I do have http://ppa.launchpad.net/kubuntu-experimental/ubuntu jaunty main
              in my sourse.list

              Comment


                #8
                Re: "Could not start ksmserver. Check your installation." evil white dialog box

                Went back to my old backup image, disabled the launchpad source, and reinstalled now only 52 files. Have rebooted a couple of times, and had no error message. So it seems as though you are right, that KDE 4.2.3 is to blame

                Comment


                  #9
                  Re: "Could not start ksmserver. Check your installation." evil white dialog box

                  1) I should really learn how to do backup images (and split them into DVD-sized chunks)
                  2) kdesudo works, too, of course.

                  Comment


                    #10
                    Re: "Could not start ksmserver. Check your installation." evil white dialog box

                    I use partimage - could not live without it. It splits into 2 GB chunks. Have two disks and each with four primary partitions of which half are different Linux distros. To use partimage you of course have to do that from another partition than the one you are backing up of restoring.

                    Comment


                      #11
                      Re: "Could not start ksmserver. Check your installation." evil white dialog box

                      That would be a problem, then, unless I use it from a live CD (System Rescue CD or some such). Hm, about adding more distros... I'm not sure I can add more partitions to my HDs. sda is tiny (by today's standards) & pretty much full; sdb ended up with four primary partitions.

                      Comment


                        #12
                        Re: "Could not start ksmserver. Check your installation." evil white dialog box

                        Is there a solution for this problem?. I have the same message every time i try to do edit a file with kate

                        Comment


                          #13
                          Re: "Could not start ksmserver. Check your installation." evil white dialog box

                          SOMEBODY has to know what config file we can edit! I wanna kill that evil white dialog box! Isn't there a ksmserverrc or something we can edit to erase that ridiculous xmessage?

                          Otherwise, KDE 4.2.3 is awesome.

                          Comment


                            #14
                            Re: "Could not start ksmserver. Check your installation." evil white dialog box

                            Okay, how about we comment out this line:
                            Code:
                            test -n "$ksplash_pid" && kill "$ksplash_pid" 2>/dev/null
                            in /usr/bin/startkde?

                            Anyone brave enough to try this solution?

                            Comment


                              #15
                              Re: "Could not start ksmserver. Check your installation." evil white dialog box

                              Originally posted by gabe
                              Okay, how about we comment out this line:
                              Code:
                              test -n "$ksplash_pid" && kill "$ksplash_pid" 2>/dev/null
                              in /usr/bin/startkde?

                              Anyone brave enough to try this solution?
                              Oh, why not.
                              [me=abalone]makes sure to type "kdesudo kate" this time[/me]

                              Comment

                              Working...
                              X