[Kde-pim] Kontact Summary Page Hanging - more info

[Ingo Klöcker]

On Thursday 13 May 2010, Anne Wilson wrote:
> On Wednesday 12 May 2010 22:17:31 Ingo Klöcker wrote:
> > On Tuesday 11 May 2010, Anne Wilson wrote:
> > > On Tuesday 11 May 2010 19:12:18 Ingo Klöcker wrote:
> > > > On Tuesday 11 May 2010, Anne Wilson wrote:
> > > > > On Monday 10 May 2010 22:43:17 Lindsay Mathieson wrote:
> > > > > > On Tue, 11 May 2010 06:37:08 am Ingo Klöcker wrote:
> > > > > > > This problem has been discussed recently on the
> > > > > > > kdepim-users mailing lists. The reporter has identified
> > > > > > > the plugin that is responsible for the problem: the
> > > > > > > Special Dates plugin.
> > > > > > 
> > > > > > Nope, I tried disabling that on Anne Wilson's advice, it
> > > > > > made no difference. She said it didn't work for her
> > > > > > either.
> > > > > 
> > > > > I'm not sure that my problem is directly related to kdepim. 
> > > > > In my case kontact will not launch.  All the apps launch as
> > > > > stand-alone, so I tried disabling that special dates plugin
> > > > > in case it was Summary that was causing my problem - I
> > > > > always configure kontact to start in Summary.
> > > > 
> > > > Hmm. In this case I'd look for the culprit by disabling all
> > > > summary plugins and then enabling them one by one.
> > > 
> > > OK - I tried that.  I renamed my kontact_summaryrc~ to save it,
> > > then cleaned out the whole content of kontact_summaryrc. 
> > > Kontact still doesn't display.
> > > 
> > > Last week I was given a command that should have caused the
> > > display if the processes are running, but I get a failure with
> > > it.  Perhaps you can see what's wrong with the command, so that
> > > I can test it again.
> > > 
> > > qdbus org.kde.kontact
> > > /kontact/MainWindow_1.com.trolltech.Qt.QWidget.show
> > > 
> > > gives
> > > 
> > > Path '/kontact/MainWindow_1.com.trolltech.Qt.QWidget.show' is not
> > > a valid path name.
> > 
> > Try
> > 
> >   qdbus org.kde.kontact
> >   /kontact/MainWindow_1/com.trolltech.Qt.QWidget
> > 
> > show
> 
> "Path '/kontact/MainWindow_1/com.trolltech.Qt.QWidget' is not a valid
> path name."
> 
> > Alternatively, you can always use qdbusviewer.
> 
> Never used that before, and not sure what I'm looking for, but
> filtering on kontact gives me
> 
> org.kde.kontact

You can simply navigate to 
/kontact/MainWindow_1/com.trolltech.Qt.QWidget and then click on 
"Method: show" to call this method.


> Connected to D-Bus.
> 
> Just one thing that I have noticed, and I don't know whether it's
> significant or not.  When I've tried to launch Kontact I have to
> kill it - and I use System Activity Monitor for that.  Killing
> Kontact leaves many kio-files behind.  Killing one (sometimes two)
> takes most of the others with it, but there is always one left
> behind.  It appears to be related to the launcher. If more
> information can be gathered from that, please tell me what to check
> for, since the monitor does show quite a bit of information about
> the processes.

KIO slaves quit automatically after a certain timeout. There's no point 
in killing them manually.

Maybe starting Kontact with strace or ltrace, i.e.
  strace kontact --nofork
or
  ltrace kontact --nofork
will show something useful.


Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20100513/61c5538c/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/