Errors in Kubuntu or Kate

[Dazed_75]

On Mon, Nov 28, 2011 at 8:23 AM, Stephen <cryptworks at gmail.com> wrote:

> Ubuntu and its derivatives have specifically limited X so that it
> cannot be run as root, only as a user.
>
> This is why it complains, other distros that allow x to run as root
> are the ones who don't complain because it can spawn root X elements.
>

Except that on ubuntu it works and does not complain.  On Kubuntu, it
complained, but it worked anyway.  Ubuntu does have gksudo intended for
using sudo to run gui stuff and apparently (from another response)
Kubuntu/KDE has kdesudo.   Seems a waste to have two utilities if they both
work.  I wonder what actual difference there is that might add value to the
latter.

>
> this is done as a security choice.
>
> IT wreaks unholy hell with an installer we use at work to install our
> software because it wont work unless it runs as root. so that limits
> what distros we can even hope to install on. but as it does work on
> the one we do support development is happy.
>
> On Sun, Nov 27, 2011 at 5:18 PM, Dazed_75 <lthielster at gmail.com> wrote:
> > ROFL !!!  One of the things I have always disliked about KDE is the
> > insistence that that jave to roll their own packages and name them with
> an
> > initial k or kde.  I am sure there is sometimes a reason to do that but
> with
> > sudo?  I hardly think there could be a real reason.  Of course, I have
> not
> > yet hit my limit of being wrong 100 times yet today.
> >
> > On Sun, Nov 27, 2011 at 5:13 PM, James Mcphee <jmcphe at gmail.com> wrote:
> >>
> >> 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 at 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 at 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 at gmail.com>
> wrote:
> >>>>>
> >>>>> Anyone know why these errors would occur from trying to edit a system
> >>>>> file in Kubuntu 11.10 using Kate?
> >>>>>>
> >>>>>> larry at 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 at 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 at 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 at gmail.com
> >>>>
> >>>> ---------------------------------------------------
> >>>> PLUG-discuss mailing list - PLUG-discuss at 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 at 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 at gmail.com
> >>
> >> ---------------------------------------------------
> >> PLUG-discuss mailing list - PLUG-discuss at 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 at lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail settings:
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
>
>
>
> --
> A mouse trap, placed on top of your alarm clock, will prevent you from
> rolling over and going back to sleep after you hit the snooze button.
>
> Stephen
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.PLUG.phoenix.az.us/pipermail/plug-discuss/attachments/20111128/cce0419e/attachment.html>