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

[Anne Wilson]

On Thursday 13 May 2010 10:04:27 Ingo Klöcker wrote:
> On Thursday 13 May 2010, Anne Wilson wrote:
> > > 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.
> 
Interesting.  That opened Kontact in Akregator - possibly that was the module 
open when I closed kontact.  However, the busy icon was non-stop even though 
the progress bar says 100%, and I can't either change module or see anything 
in the main window.

> > 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.
> 
OK

> Maybe starting Kontact with strace or ltrace, i.e.
>   strace kontact --nofork

I tried to capture the output of that, but without success.  When it gets to 
the stage where it falters I see messages containing

= -1 EAGAIN (Resource temporarily unavailable)

several times.  I'll try to leave it until it completes or shuts down, then 
try the ltrace command.  After an hour or so I killed it.

> or
>   ltrace kontact --nofork
> will show something useful.
> 
Again, I couldn't capture the output, but it ended with

_ZN12KApplication6notifyEP7QObjectP6QEvent(0xbf9f0224, 0x92db768, 0xbf9ee48c, 
0, 0x92db768 <unfinished ...>
_ZN7QObject10childEventEP11QChildEvent(0x92db768, 0xbf9ee48c, 0x592ff4, 
0x6c2bdb8, 0x5943a0) = 0x6909708
<... _ZN12KApplication6notifyEP7QObjectP6QEvent resumed> ) = 1
<... _ZN12KApplication6notifyEP7QObjectP6QEvent resumed> ) = 1
_ZN12KApplication6notifyEP7QObjectP6QEvent(0xbf9f0224, 0x9d09118, 0xbf9eea80, 
14, 0x9d09118 <unfinished ...>
_ZN7QObject13connectNotifyEPKc(0x9c580d0, 0x5db64b4, 0x946d310, 4, 0) = 
0x5e08aa8
_ZN12KApplication6notifyEP7QObjectP6QEvent(0xbf9f0224, 0x9d78aa0, 0xbf9ee2a4, 
11, 0x9d78aa0) = 1
_ZN12KApplication6notifyEP7QObjectP6QEvent(0xbf9f0224, 0x9d055c4, 0xbf9eea80, 
13, 0x9d055c4) = 1
_ZN12KApplication6notifyEP7QObjectP6QEvent(0xbf9f0224, 0x9d70488, 0xbf9eea80, 
12, 0x9d70488 <unfinished ...>
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0x3f92c9c, 0x98b5c58, 16, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0x3f92cf4, 0x98b5c58, 7, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0xa168e08, 0x98b5c58, 17, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0x9de22b8, 0x98b5c58, 8, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0x9de22b8, 0x98b5c58, 18, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0x3f92c9c, 0x98b5c58, 16, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0xa168e48, 0x98b5c58, 7, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0xa168e48, 0x98b5c58, 17, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0x3f92818, 0x98b5c58, 15, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0x9ef9b20, 0x9de22b8, 0x98b5c58, 8, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0x3f927c4, 0x9ef9b20, 14, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0x3f92818, 0x9ef9b20, 15, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0xa169078, 0x9ef9b20, 6, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0x9fad0b8, 0x9ef9b20, 8, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0x9fad0b8, 0x9ef9b20, 7, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0x3f92c9c, 0x98b5c58, 16, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0xa169030, 0x98b5c58, 7, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0x9fad0b8, 0x98b5c58, 17, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0x3f92818, 0x98b5c58, 15, 0) = 
0x3fc8c08
_ZN7QObject13connectNotifyEPKc(0xa1656f8, 0x9de22b8, 0x98b5c58, 8, 0) = 
0x3fc8c08
+++ killed by SIGTRAP +++

Anne
-- 
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
-------------- 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/cc071e24/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/