Results 1 to 5 of 5

Thread: Run Command interface Probs

  1. #1

    Default Run Command interface Probs

    G'day Gentlefolks.
    I've been having this problem ever since my fresh install of opensuse:

    After using the (GUI) Run Prompt to luanch a few programs. It no longer works,and I am subsequently prompted with this message:

    "Error launching /usr/share/applications/kde4/kwrite.desktop. Either KLauncher is not running anymore, or it failed to start the application."

    Soon after, my terminals also begin to tell me:

    "INIT: Id "x" respawning too fast: disabled 5 minutes"

    I'm not certain if the 2 problems are related, but they CERTAINLY correspond, and my system, practically locks me out (because it will happen in EACH terminal, I try to type in)

    Could someone please help?
    http://www.youtube.com/watch?v=dOZUYxwhduE
    The Absence of Evidence is not the Evidence of Absence

  2. #2
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Smile Re: Run Command interface Probs

    G'day Gentlefolks.
    I've been having this problem ever since my fresh install of opensuse:

    After using the (GUI) Run Prompt to luanch a few programs. It no longer works,and I am subsequently prompted with this message:

    "Error launching /usr/share/applications/kde4/kwrite.desktop. Either KLauncher is not running anymore, or it failed to start the application."

    Soon after, my terminals also begin to tell me:

    "INIT: Id "x" respawning too fast: disabled 5 minutes"

    I'm not certain if the 2 problems are related, but they CERTAINLY correspond, and my system, practically locks me out (because it will happen in EACH terminal, I try to type in)

    Could someone please help?
    So I do not know the reason for your reinstall, but based on these errors, your installation did not work. There is corruption of system files, either due to bad installation media or a bad disk partition. In the case of a new install, I would not try to fix it but I suggest you start over and make sure your install media passes muster and your target partition is not bad.

    Thank You,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  3. #3

    Default Re: Run Command interface Probs

    jdmcdaniel3, thank you much for your response. I had felt that bad sectors could be a possibility, but I did a full scan of my HDD with spinrite about.. 3 weeks ago, and all was fine, so I ruled that out - I WILL check my installation media though, thanks for reminding me.

    Yes, it was a fresh install and in less than 48 hours, I have reinstalled 4 times.
    I tried updating during install, NOT updating during install, updating after install, NOT updating after install... its the same thing.

    bah! : ' (.

    I'll tell u how it goes.
    http://www.youtube.com/watch?v=dOZUYxwhduE
    The Absence of Evidence is not the Evidence of Absence

  4. #4
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Smile Re: Run Command interface Probs

    jdmcdaniel3, thank you much for your response. I had felt that bad sectors could be a possibility, but I did a full scan of my HDD with spinrite about.. 3 weeks ago, and all was fine, so I ruled that out - I WILL check my installation media though, thanks for reminding me.

    Yes, it was a fresh install and in less than 48 hours, I have reinstalled 4 times.
    I tried updating during install, NOT updating during install, updating after install, NOT updating after install... its the same thing.

    bah! : ' (.

    I'll tell u how it goes.
    Installation media can be created bad. It might be the downloaded file. It could be the actual media and it could the DVD or CD burner, but it does happen and its hard to know just how the problem will manifest its self in the new OS installation. But, trying to fix it simply will not work in most cases. Good luck and when you re-download it, look at the md5 check-sum. This is useful is determining if the downloaded file is good and then later if the media you made is good, after it is recorded. A problem can occur anywhere in the chain to that final disk install.

    Thank You,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,925
    Blog Entries
    2

    Default Re: Run Command interface Probs

    Although I agree that you should take a look at your install media (both the downloaded file <and> after your burn. Some burner apps like K3b will do that check automatically for you), when/if you wish to troubleshoot your specific launching problem, you can try running the command listed by the displayed error in a terminal, in your case the full kwrite path.

    Not sure about your terminal error, a re-spawning error? If not an installation issue, you might need to recite your last activities before the error, maybe also inspect your "messages" file which logs system events of note.

    HTH,
    Tony

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •