LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   "Could not start kdeinit5. ..." - How do I fix this? (https://www.linuxquestions.org/questions/linux-newbie-8/could-not-start-kdeinit5-how-do-i-fix-this-4175657066/)

Wilfrid 07-08-2019 03:21 PM

"Could not start kdeinit5. ..." - How do I fix this?
 
Hi there,

After a routine update I got the typical message (as I see in the Internet) "Could not start kdeinit5. Check your installation", with an "Okay" button.
I use PCLINUXOS on an Acer Aspire 5733. Technically I am a complete newbie, as good as Linux-illiterate. Therefore I please need exact and detailed guidance through all commands to remedy the problem. I depend on Linux in order to use a customized lexicographic programme.

Would anybody be willing to help, please?

Wilfrid

frankbell 07-08-2019 07:21 PM

I've never encountered this myself, but a web search for "Could not start kdeinit5. Check your installation" will turn up many articles about this issue and offer various ways that others have solved it.

Was there any more to the error message? If so, please post it.

It would be difficult to provide exact and detailed guidance in the absence of more detail about took place. Please take a look at this: https://www.linuxquestions.org/linux...Ask_a_Question

Welcome to LQ.

celchu 07-09-2019 01:31 PM

if i had to guess, on the last update you missed a lot of messages on the extra output box on completion of update
When you get the that screen, do ctrl+alt+f1 to take you back to the terminal log in and do kdeinit5.
This will then tell you what is failing, it happened to me on the last update as it created symlinks to other qt applications that i forgot i put in the path, these were causing the failure, i removed the symlinks and it started up ok.

remove custom path from /etc/ld.so.conf.d/libs.conf
the run ldconfig -v
This should get you back up and running

6th_sense 09-02-2019 02:42 PM

1 Attachment(s)
Hi guys,

Problem
:
========

Been having a similar problem as the OP - Error messages keep popping up one after another in Fedora 28 - KDE desktop... See the attached image.

How to switch to a Terminal - another possibility - for the OP:
========================================

It is possible that X-windows is running on your first terminal (ctrl-alt-f1), so you *may* need to run (ctrl-alt-f2) - to get to a terminal - this is the case with fedora, in any case. Or, alternatively, trying running a the terminal application from within X-windows - you may be able to copy paste commands and the answers you get from there - though I am not sure now, if you have to enable that feature.

Plasma is Running and so is KDEinit5
============================

I've attached an image of the error message that pops up. I am able to however run all my window applications without any issues - and if I run "ps aux|grep kde" I see kdeinit5 running... on the command line - So, I am not sure what is happening.

If anyone can tell me why this happens every 2 to 3 minutes on my laptop - that would be much appreciated.

Fear of Celchu's Suggestion:
====================

I don't believe I can try celchu's suggestions - unless someone can vouch that it won't kill my X-window session - I see kdeinit5 running... showing when I do a ps aux|grep init - so, it would seem I have to kill the process first - hence my fear that I will kill my X-window session - which seems to have no problems apart from an unhappy face showing up in a message box - I haven't been able to capture that in a screenshot.

My hardware is as follows:
====================

Gateway laptop: NV79C51u, 8GB DDR3 Ram (I upgraded it from 4), 1 TB HDD (upgraded), 17.3", Intel HD Graphics, - Running Fedora 28.

rnturn 09-03-2019 08:31 AM

Quote:

Originally Posted by 6th_sense (Post 6032444)
Been having a similar problem as the OP - Error messages keep popping up one after another in Fedora 28 - KDE desktop... See the attached image.

I've seen that error message pop up occasionally on Leap 15.1 so this doesn't seem to be a Fedora-specific problem. Some days it's more frequent than others. That error popped up this morning for the first time in a while. I've never been able to tie it to a specific application -- at least not from anything in /var/log/messages -- so I can't tell if the change in frequency of the messages is tied to a change in my usage or whether it's because of attempts on the part of the KDE developers to squash the bug. It surely would be helpful for the messages to provide a bit more information about what it was trying to do when it failed.


All times are GMT -5. The time now is 12:49 PM.