Saída de erro de terminal RE: editando o arquivo .conf no Xbuntu

Saída de erro de terminal RE: editando o arquivo .conf no Xbuntu

Estava curioso para saber a saída de erro do terminal ao executar o arquivo sudo Kate. Eu li em um fórum que me orientou a abrir meu bloco de notas usando o gksudo. Percebendo que isso não havia sido instalado, simplesmente fui em frente e tentei abrir meu editor de bloco de notas sudoe editar o .confarquivo (o que funcionou, quero dizer que salvou o novo .confarquivo sem erro de acesso root, mas me deixou com"linhas de erros desconhecidos"). Não tenho problemas sudoem executar meu Raspberry PI para abrir e editar arquivos de texto usando nano.

O que causou as linhas de erro e como corrigi-las se forem facilmente respondidas?

skratch@Slick:~$ sudo kate
[sudo] password for skratch: 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Error: "/var/tmp/kdecache-skratch" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-skratch" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-skratch" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-skratch" is owned by uid 1000 instead of uid 0.
kdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Error: "/tmp/ksocket-skratch" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-skratch" is owned by uid 1000 instead of uid 0.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Error: "/var/tmp/kdecache-skratch" is owned by uid 1000 instead of uid 0.
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-skratch" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-skratch" is owned by uid 1000 instead of uid 0.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Error: "/var/tmp/kdecache-skratch" is owned by uid 1000 instead of uid 0.
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Error: "/var/tmp/kdecache-skratch" is owned by uid 1000 instead of uid 0.
QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.8'
Error: "/tmp/kde-skratch" is owned by uid 1000 instead of uid 0.

Responder1

Uid 1000 é você. Uid 0 é raiz. Ganhe um saque na saída de ls -l /var/tmp. Existem algumas pastas das quais você é proprietário e outras de propriedade do root. Se você não é proprietário de um arquivo e as permissões são drwx------, você não pode abri-lo, simples assim. Quando você chamou o kate com privilégios de root, o kate precisou acessar pastas que são de sua propriedade, mas o programa foi executado da perspectiva do root. Daí os erros

informação relacionada