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

List:       kde-core-devel
Subject:    Re: KRootProp
From:       Simon Hausmann <shaus () uermel ! Med ! Uni-Magdeburg ! DE>
Date:       1999-10-01 17:51:05
[Download RAW message or body]

On Fri, 1 Oct 1999, Rik Hemsley wrote:

> #if Simon Hausmann
> > Hmmm, what happends if you
> > 
> > 1) kill any possibly running kded
> > 2) remove the property manually (xprop -root -remove KDED_RESOURCES)
> > 3) start kded standalone
> > 4) launch your favourite app using kded
> 
> Seg fault :(
> 
> > BTW, do applications like kpanel, konqueror or kdesktop run for you?
> > ('cause they all *use* kded)
> 
> konqy is working for me now. I'm starting to mistrust my code. I've
> tried various ways of doing things, copying code from the apps
> that use kded, but no luck.
> 
> I'll persevere, as it is likely to be me doing something wrong, though
> the code that causes the crash is quite simple:
> 
> int main( int argc, char *argv[] )
> {
>   CORBA::ORB_var orb = CORBA::ORB_init(argc, argv, "mico-local-orb");
>   assert (!CORBA::is_nil(orb));
> 
>   KdedInstance kded(argc, argv, orb);
>    ... -> crash in KRootProp::setProp()
> 
> Am I doing something wrong there ? I started with the example code
> in the kded docs.

You should probably define a K/QApplication object *before* defining the
KdedInstance, as setProp() accesses qt_xdisplay() and qt_xrootwin() which
are AFAIK only setup after application setup.

Ciao,
 Simon

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