Agreed. Maybe kdesudo would play happier. But goofy stuff like that is
why I decided to switch away from kde.
On Sun, Nov 27, 2011 at 5:10 PM, Dazed_75 <
lthielster@gmail.com> wrote:
> Of course. And I did ignore it. However, sudo does not give those kinds
> of errors in other distros and derivatives where I have used it. Kind of
> silly to give errors saying we know what you are doing and while it is
> perfectly legitimate and the purpose of using sudo, we just thought we
> would complain and possibly confuse you. :)
>
>
> On Sun, Nov 27, 2011 at 5:05 PM, James Mcphee <jmcphe@gmail.com> wrote:
>
>> You're running a kde app as root, that's what the sudo thing does. It
>> tries to connect to your kde session and notices that it's owned by you and
>> not the UID of the process you're launching, and complains. If it works, I
>> say ignore it.
>>
>> On Sun, Nov 27, 2011 at 4:50 PM, Dazed_75 <lthielster@gmail.com> wrote:
>>
>>> Anyone know why these errors would occur from trying to edit a system
>>> file in Kubuntu 11.10 using Kate?
>>>
>>>> larry@hammerhead:~$ sudo kate /etc/lsb-release
>>>> Error: "/var/tmp/kdecache-larry" is owned by uid 1000 instead of uid 0.
>>>> Error: "/tmp/kde-larry" is owned by uid 1000 instead of uid 0.
>>>> Error: "/tmp/ksocket-larry" 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-larry" is owned by uid 1000 instead of uid 0.
>>>> Error: "/tmp/kde-larry" is owned by uid 1000 instead of uid 0.
>>>> Error: "/var/tmp/kdecache-larry" is owned by uid 1000 instead of uid 0.
>>>> kbuildsycoca4 running...
>>>> Error: "/var/tmp/kdecache-larry" is owned by uid 1000 instead of uid 0.
>>>> Error: "/var/tmp/kdecache-larry" is owned by uid 1000 instead of uid 0.
>>>> Error: "/tmp/kde-larry" is owned by uid 1000 instead of uid
>>>> 0.
>>>>
>>>> larry@hammerhead:~$
>>>>
>>>>
>>>> Kate ran and the edit did work BTW
>>> --
>>> Dazed_75 a.k.a. Larry
>>>
>>> Please protect my address like I protect yours. When sending messages to
>>> multiple recipients, always use the BCC: (Blind carbon copy) and not To: or
>>> CC:. Also remove all of the addresses from the message body before
>>> forwarding the message. These simple measures prevent spy programs from
>>> capturing the addresses shown in the recipient list and the message body.
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>>
>>
>>
>>
>> --
>> James McPhee
>> jmcphe@gmail.com
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>
>
>
>
> --
> Dazed_75 a.k.a. Larry
>
> Please protect my address like I protect yours. When sending messages to
> multiple recipients, always use the BCC: (Blind carbon copy) and not To: or
> CC:. Also remove all of the addresses from the message body before
> forwarding the message. These simple measures prevent spy programs from
> capturing the addresses shown in the recipient list and the message body.
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
--
James McPhee
jmcphe@gmail.com
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)