[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: does kdeinit4 need $DISPLAY ?
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2009-09-20 21:11:40
Message-ID: 200909202311.40475.aacid () kde ! org
[Download RAW message or body]

A Diumenge, 20 de setembre de 2009, Andreas Pakulat va escriure:
> On 20.09.09 21:27:39, Stefan Majewsky wrote:
> > Am Sonntag 20 September 2009 20:53:25 schrieb Thiago Macieira:
> > > Em Domingo 20. Setembro 2009, ās 20.33.21, Martin Koller escreveu:
> > > > Hi,
> > > >
> > > > My backup program (kbackup) can also run as a cron job, so there is
> > > > no KDE session running.
> > > > When it wants to start a KIO Job (I think it comes from
> > > > KIO::listDir()) I get the following error:
> > > > kdeinit4: Aborting. $DISPLAY is not set.
> > > > kdeinit4: Aborting. $DISPLAY is not set.
> > > > kbackup(15825): : couldn't create slave :  "Cannot talk to klauncher:
> > > > Not connected to D-BUS server"
> > > >
> > > > Does that mean KIO needs $DISPLAY ?
> > >
> > > Yes, and D-Bus.
> >
> > D-Bus is something I can understand. (Although this shows a design
> > failure in D-Bus: There should be something like a "user bus" that is
> > activated by the dbus-daemon once a program running with the privileges
> > of this certain user needs it.)
> >
> > But why would KIO need a GUI?
> 
> Because it may need to ask the user for authentication information, show
> errors etc.

In my opinion it would be a nice feature having callbacks/setters/whatever for 
all those kinds of "things KIO uses a gui for" so you can use KIO power in a 
gui-less application.

Before anyone mentions it, no, i'm not voluteering for it.

Albert

> 
> Andreas
> 
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<
> 

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]