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

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

    is not a solution to use kdesudo from konsole. I use sude over 3 years and i have no problem. What happen and have change with the sudo command?
    We have to report it as a bug?

    Comment


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

      Same problem here. I reported this as a bug. If this affects you please subscribe to the bug report:

      https://bugs.launchpad.net/ubuntu/+s...ce/+bug/378394

      Comment


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

        Originally posted by vista killer

        I use sude over 3 years and i have no problem. What happen and have change with the sudo command?
        We have to report it as a bug?
        No. "sudo" has never been correct syntax to run a KDE package, only "kdesu" or "kdesudo".

        http://kubuntuforums.net/forums/inde...opic=3089088.0

        Comment


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

          i think you have wrong. I use kubuntu for three years and i have always use sudo when i want to edit a file with kate.

          Comment


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

            kdesudo is the correct way to launch GUI applications in KDE. sudo will 'work', but there are risks associated with it, like damaging permissions on files in your home directory. You should always launch a GUI app with kdesudo.

            mm0
            Dell Inspiron 1720 Laptop<br />Intel T9300 Core2Duo Processor @ 2.5Ghz<br />4 GB Ram | 1920 X 1200 Resolution<br />2 X 160 GB SATA HD Internal<br />Nvidia GeForce 8600M Graphics Adapter<br />Using Kubuntu 9.10

            Comment


              #21
              Re: &quot;Could not start ksmserver. Check your installation.&quot; 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?
              I can confirm this works, provided, of course, it's the right instance of it, which is essentially:

              Code:
              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."
              I commented out the entire section. I'm pretty sure it's related, somehow, to the upgrade to KDE 4.2.4, which I did just before I got that error message.

              Comment


                #22
                Re: &quot;Could not start ksmserver. Check your installation.&quot; evil white dialog box

                Originally posted by muzicman0
                kdesudo is the correct way to launch GUI applications in KDE. sudo will 'work', but there are risks associated with it, like damaging permissions on files in your home directory. You should always launch a GUI app with kdesudo.
                even though that is correct, opening some program with sudo only temporary gives you root privilege, while you remain to be the user you are.
                on the other hand kdesudo opens that file as the root user it self.
                try opening dolphin with kdesudo (without any path), and you will see that it will open roots home folder on default instead of your home folder.

                Comment

                Working...
                X