Announcement

Collapse
No announcement yet.

DCOP server doesn't terminate, causing shutdown block

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

    DCOP server doesn't terminate, causing shutdown block

    Everyone knows about that problem where you try to shut down, but you get stuck at a black screen with the cursor, right?

    Well, I've tracked it down to a process that, when terminated, allows the shutdown to happen. The process is "dcopserver_shut" (or similar).

    Anyone know if this is caused by the DCOP server itself, as I think it is? How about a solution? Should I just report it to someone involved with DCOP, file a bug report, or what?
    For external use only.

    #2
    Re: DCOP server doesn't terminate, causing shutdown block

    Just an idea for a little hack, er, work around ...:

    Code:
    USER # mkdir ~/.kde/shutdown
    USER # touch ~/.kde/shutdown/terminator
    USER # chmod +x ~/.kde/shutdown/terminator
    USER # echo '#!/bin/bash' >> ~/.kde/shutdown/terminator
    USER # echo 'killall dcopserver' >> ~/.kde/shutdown/terminator
    (As, from my experience, bugs are long-living :P)

    Comment


      #3
      Re: DCOP server doesn't terminate, causing shutdown block

      So putting a script in ~/.kde/shutdown will cause that script to be executed on shutdown? Interesting... i wonder what else I could do with it.
      For external use only.

      Comment


        #4
        Re: DCOP server doesn't terminate, causing shutdown block

        Originally posted by SheeEttin
        So putting a script in ~/.kde/shutdown will cause that script to be executed on shutdown?
        Worth a try, at least (- further reading).

        Originally posted by SheeEttin
        Interesting... i wonder what else I could do with it.
        Believe me: you don't want to know

        Comment


          #5
          Re: DCOP server doesn't terminate, causing shutdown block

          Hmm... doesn't work.
          Apparently, it doesn't get executed at the right time. There's no dcopserver_shut process at the time of execution for it to kill. Could I make it wait a few seconds before attempting the kill? (Also, exactly when does the script get executed?)

          By the way, the process seems to be a little tricky to kill (by usual standards, anyway). It isn't killed by killall, nor can you get its PID through pidof for kill. I eventually had to resort to "kill `ps -e | grep dcopserver_shut | cut -c 1-5`", rather complicated for killing one process.
          For external use only.

          Comment


            #6
            Re: DCOP server doesn't terminate, causing shutdown block

            Originally posted by SheeEttin
            Hmm... doesn't work.
            Maybe because you're not trying what I've asked you for (?).

            While I've suggested to kill the dcop server as a whole, you are trying to kill it's shutdown process ...

            Comment


              #7
              Re: DCOP server doesn't terminate, causing shutdown block

              Well, that process, when killed, will allow the shutdown to continue.
              But if you think that killing the DCOP server outright isn't a bad idea, I'll try that.
              For external use only.

              Comment


                #8
                Re: DCOP server doesn't terminate, causing shutdown block

                Well, that didn't work. Here's what I tried most recently:
                Code:
                #! /bin/sh
                killall dcopserver
                kill 'ps -e | grep dcopserver_shut | cut -c 1-5'
                The dcopserver_shut process apparently doesn't appear until after the script is executed. (Whether it actually appears after the script, or the script merely executes too quickly is something to give thought to.)

                So, is it possible to insert a delay into a script? If not, where could I put a script that would execute after the process appears but before it hangs, waiting for it?
                For external use only.

                Comment

                Working...
                X