[SOLVED] Missing text editor

[Ditzian]

I am using PCLinuxOS 2010 and I find that there is no text editor.  The default in the desktop configurator is Kwrite, but there is no Kwrite, nor is there a Kate.  A search of Synaptic does not reveal of these, nor is there a KDesk4.  I am using the spout.ussg.Indiana repo, which is what was selected when I downloaded PCLinuxOS 2010.  

What is the text editor in KDE4, or is one of the old standards in another repo?

Jan

[Neal ManBear]

When searching for kwrite in Synaptic, switch to the "Provided Packages" search option. This will show you that kwrite is included in kdebase4 and kdebase4-workspace.
Search for kate in the same way.

[travisN000]

Is it safe to assume that you are using the KDE4 desktop environment?  ..I believe it is part of the base kde install, so you should have it.

Perhaps you will find the following thread helpful:

http://www.pclinuxos.com/forum/index.php/topic,71397.0.html
 

[Ditzian]

I switched the search option to "Provided Packages."  It did not turn up either Kate or Kwrite.  However, I turned up KDEbase4 and KDEbase-4workspace as already installed.  I decided to reinstall them, no errors during install, but no improvement.

Here is more information:

• I am using KDE4.
• I am logged on a a regular user, not as a superuser (I hope).
• My list of editors includes Kwrite, but Kwrite does not open; instead,I receive the message "A KDE text-editor component could not be found.  Please check your KDE installation."
• My list of editors does not include Kate.
• Kwrite is included as a program for txt files in "Configure your Desktop."

I seem to have some sort of erroneous installation of something, but that something does not appear to be KDEbase4.  Perhaps it is another package.

Jan

[Neal ManBear]

Open a konsole and type dbus-launch kwrite and then type the <Enter> key.

If any error messages are generated, post them here.

[Ditzian]

Neal,

I opened Konsole and here is the resulting interaction:


[jan@localhost ~]$ dbus-launch kwrite
kdeinit4: Shutting down running client.
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kded(3988): PowerDevil not initialized, another power manager has been detected
QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)
QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)
klauncher: Exiting on signal 15
[jan@localhost ~]$


When the last message appeared, "klauncher......" Kwrite opened.  When I closed Kwrite, the last prompt above appeared.  At this point, with no Kwrite open, I went to PC > Editors > Kwrite, and Kwrite opened properly. 

(1)  I have not rebooted to see if this holds.  Is it necessary to do that? 

(2)  What is dbus-launch and why did it fix this problem? 

(3)  Should I try this approach, dbus-launch [name of program] on anything that causes an error message?

Jan

[Neal ManBear]

LOL So many questions. The command worked. Good. There should be no further problems, but if there are, you know what to do. As to why this happened, I do not know.

[Ditzian]

Well, I answered one of the questions.  The fix is OK after a restart. 

Jan

[Neal ManBear]

Info on the dbus-launch command can be found here.

[travisN000]

General info on dbus is also here:

http://www.freedesktop.org/wiki/Software/dbus

[Ditzian]

Thanks for the references.  I had found that already, but it does not address why dbus--launch fixes anything.  However, it does, so I will simply remember it.

Thanks to all,

Jan

[GOTHBITES]

Hello

just installed and this fixed my problem so than you so very much Neal 

[travisN000]

Thanks for the references.  I had found that already, but it does not address why dbus--launch fixes anything.  However, it does, so I will simply remember it.

Thanks to all,

Jan

How's this:

When you 'su' without '-' the unix environment of the original user is preserved. This includes the variable DBUS-SESSION-BUS-ADDRESS, which is the socket address of the session-local DBUS.

For security, DBUS prohibits other UIDs from accessing a user's session bus. When root's Kate's KApplication instance tries to use DBUS-SESSION-BUS-ADDRESS that still points at your regular user's bus it fails with a fatal error, and an unhelpful error message: "Session bus not found."

If you use 'kdesu' to launch your apps, it clears that environment variable, leaving root's KDE programs free to use the existing session bus for root  applications.  Likewise if you 'su -' - the entire environment is reset.

..with dbus-launch, if it cannot connect to an existing dbus session it starts a new one.