rpm -qa | grep -e kate -e kwrite
doktor5000 wrote:Can you please open a terminal and show the output of
- Code: Select all
rpm -qa | grep -e kate -e kwrite
~>rpm -qa|grep -e kate -e kwrite
kate-4.10.5-1.1.mga3
kwrite-4.10.5-1.1.mga3
kwrite-handbook-4.10.2-3.mga3
lib64kateinterfaces4-4.10.5-1.1.mga3
lib64katepartinterfaces4-4.10.2-3.mga3
kate-handbook-4.10.5-1.1.mga3
katepart-4.10.5-1.1.mga3
kate-plugin-pate-4.10.5-1.1.mga3
~>
rpm -qa | grep texteditor
ps -ef | grep dbus
dbus-launch kwrite
~>rpm -qa | grep texteditor
ktexteditor-4.10.5-1.1.mga3
lib64ktexteditor4-4.10.2-3.mga3
~>ps -ef | grep dbus
499 880 1 0 08:23 ? 00:00:01 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
rakitsa 1125 1 0 08:24 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session --sh-syntax
rakitsa 1132 1 0 08:24 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
rakitsa 3950 3935 0 08:33 pts/1 00:00:00 grep dbus
~>dbus-launch kwrite
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
kdeinit4: Shutting down running client.
klauncher: Exiting on signal 15
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
kbuildsycoca4 running...
QDBusObjectPath: invalid path ""
QObject::connect: Cannot connect (null)::deviceFound(Device*) to BlueDevilDaemon::deviceFound(Device*)
QObject::connect: Cannot connect QTimer::timeout() to (null)::stopDiscovery()
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
kded(4113): KDE Power Management system not initialized, another power manager has been detected
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.6'
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
urpmq --list-media active
~>urpmq --list-media active
Core Release
Core Release (distrib1)
Core Updates (distrib3)
Nonfree Release (distrib11)
Tainted Release (distrib21)
Core 32bit Release (distrib31)
Core 32bit Updates (distrib32)
Nonfree 32bit Release (distrib36)
Tainted 32bit Release (distrib41)
~>
strace kate
rakitsa wrote:
- Code: Select all
~>urpmq --list-media active
Core Release
Core Release (distrib1)
Core Updates (distrib3)
Nonfree Release (distrib11)
Tainted Release (distrib21)
Core 32bit Release (distrib31)
Core 32bit Updates (distrib32)
Nonfree 32bit Release (distrib36)
Tainted 32bit Release (distrib41)
~>
gives extremely long and incomprehensible output. If I were able to understand such things, I would not seek help here
davidwhodgins wrote:rakitsa wrote:
- Code: Select all
~>urpmq --list-media active
Core Release
Core Release (distrib1)
Core Updates (distrib3)
Nonfree Release (distrib11)
Tainted Release (distrib21)
Core 32bit Release (distrib31)
Core 32bit Updates (distrib32)
Nonfree 32bit Release (distrib36)
Tainted 32bit Release (distrib41)
~>
The first Core Release would be from the installation cd/dvd,
so It should likely be unselected, so the cd/dvd doesn't have
to be inserted, each time updates are being installed.
Every one of the remaining Release repositories, should have
a corresponding Updates repository enabled, so Nonfree Updates, Tainted Updates, Nonfree 32bit Updates,
and Tainted 32bit Updates, should all be enabled.
To enable them, either run drakrpm-edit-media, from the
command line (as root), or use mcc, Configure media sources.
Once they've been enabled, run (as root), urpmi --auto-update.
~>kate
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/65-google-droid-sans.conf", line 61: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-google-droid-sans.conf", line 96: Having multiple values in <test> isn't supported and may not work as expected
~>
Thanks for marking this as solved but please add [SOLVED] to the subject of your first post so that people don't have to read the whole thread only to find in the last post that it was solved.davidwhodgins wrote:Adding solved to the subject. Thanks for the feedback.
davidwhodgins wrote:Or does rakitsa have to do it?
Latte wrote:davidwhodgins wrote:Or does rakitsa have to do it?
But David is correct: only the thread opener can change the subject of the first posting.
Users browsing this forum: No registered users and 1 guest