On Friday 22 January 2016 09:21:12 David Faure wrote:
> On Thursday 21 January 2016 13:54:32 Thiago Macieira wrote:
> > Can I limit the spy hook to method calls? That is, exclude signals.
>
> Yes, for the purpose of kded/kiod that is fine
> A not-loaded-yet-module cannot possibly connect to a dbus
On Thursday 21 January 2016 13:54:32 Thiago Macieira wrote:
> Can I limit the spy hook to method calls? That is, exclude signals.
Yes, for the purpose of kded/kiod that is fine
A not-loaded-yet-module cannot possibly connect to a dbus signal.
> Another attempt, also untested.
It works !
Even th
Am 21.01.2016 um 08:37 schrieb David Faure:
>
> With this patch applied, here's one log for the first call
> (autostart+autoload, doesn't work)
>
> http://www.davidfaure.fr/2016/first_call.txt
>
> and one log for the second call (kded already started, autoload works)
>
> http://www.davidfaure.f
On Thursday 21 January 2016 08:37:38 David Faure wrote:
> On Wednesday 20 January 2016 08:41:31 Thiago Macieira wrote:
> > On Wednesday 20 January 2016 09:08:38 David Faure wrote:
> > > > Can you run with QDBUS_DEBUG=1 and tell me the messages it prints?
> >
> > [cut]
> >
> > I didn't see any "in
On Thursday 21 January 2016 08:37:38 David Faure wrote:
> > I didn't see any "invoking message spies" of the debug I left. Are you
> > sure
> > this had the hook installed?
>
> You mean the messageFilter? That's exactly the issue, that it's not getting
> called. Therefore autoload doesn't happen.
On Wednesday 20 January 2016 08:41:31 Thiago Macieira wrote:
> On Wednesday 20 January 2016 09:08:38 David Faure wrote:
> > > Can you run with QDBUS_DEBUG=1 and tell me the messages it prints?
> >
> [cut]
>
> I didn't see any "invoking message spies" of the debug I left. Are you sure
> this had
On Wednesday 20 January 2016 09:08:38 David Faure wrote:
> > Can you run with QDBUS_DEBUG=1 and tell me the messages it prints?
>
[cut]
I didn't see any "invoking message spies" of the debug I left. Are you sure
this had the hook installed?
For that matter, can you apply the attached patch so w
On Tuesday 19 January 2016 23:59:31 Thiago Macieira wrote:
> On Wednesday 20 January 2016 08:55:17 David Faure wrote:
> > Doesn't seem to support service autostart + module autoload together.
>
> > but if I kill kded5 again and do this right away:
> > $ qdbus org.kde.kcookiejar5 /modules/kcookiej
On Wednesday 20 January 2016 08:55:17 David Faure wrote:
> Doesn't seem to support service autostart + module autoload together.
> but if I kill kded5 again and do this right away:
> $ qdbus org.kde.kcookiejar5 /modules/kcookiejar
> then it doesn't work: kded5 gets started, but the call gets this
On Tuesday 19 January 2016 22:54:35 Thiago Macieira wrote:
> On Monday 18 January 2016 09:23:51 David Faure wrote:
> > Thiago: indeed the BlockingQueuedConnection call from messageFilter to the
> > main thread occasionnally leads to deadlocks, we need your
> > "postpone incoming messages" idea.
>
On Monday 18 January 2016 09:23:51 David Faure wrote:
> Thiago: indeed the BlockingQueuedConnection call from messageFilter to the
> main thread occasionnally leads to deadlocks, we need your
> "postpone incoming messages" idea.
Please try the attached patch, also found at
https://coderevi
On Tuesday 19 January 2016 15:56:47 you wrote:
> I briefly talked about this with David yesterday and looked at the code.
> What happened previously in kded5:
> - it installs a message filter using libdbus API
QtDBus API. In fact, it's QtDBus API that exists and has existed only for kded
(and now
On Dienstag, 19. Januar 2016 10:02:33 CET Aleix Pol wrote:
> On Mon, Jan 18, 2016 at 9:23 AM, David Faure wrote:
> > On Friday 15 January 2016 13:48:14 Aleix Pol wrote:
> >> On Fri, Jan 15, 2016 at 1:02 PM, Aleix Pol
wrote:
> >> > Hi,
> >> > I realized earlier last week that some of my applicati
On Mon, Jan 18, 2016 at 9:23 AM, David Faure wrote:
> On Friday 15 January 2016 13:48:14 Aleix Pol wrote:
>> On Fri, Jan 15, 2016 at 1:02 PM, Aleix Pol wrote:
>> > Hi,
>> > I realized earlier last week that some of my applications were
>> > freezing, it turns out it's because my kded is freezing
On Friday 15 January 2016 13:48:14 Aleix Pol wrote:
> On Fri, Jan 15, 2016 at 1:02 PM, Aleix Pol wrote:
> > Hi,
> > I realized earlier last week that some of my applications were
> > freezing, it turns out it's because my kded is freezing and any dbus
> > calls there need to time out (they take 30
On Fri, Jan 15, 2016 at 1:02 PM, Aleix Pol wrote:
> Hi,
> I realized earlier last week that some of my applications were
> freezing, it turns out it's because my kded is freezing and any dbus
> calls there need to time out (they take 30s to time out btw).
>
> Anyway, here's the backtrace: https://
Hi,
I realized earlier last week that some of my applications were
freezing, it turns out it's because my kded is freezing and any dbus
calls there need to time out (they take 30s to time out btw).
Anyway, here's the backtrace: https://paste.kde.org/pajbfmoh8
I saw David did something in that dir
17 matches
Mail list logo
