On Friday 22 April 2016 23:51:51 René J.V. Bertin wrote:
> On Friday April 22 2016 23:33:27 René J.V. Bertin wrote:
>
> > Looks like I'm going to have to add output to kio_http and see if the error
> > message doesn't come from an error==ENOENT returned from a failed function
> > call. Seems
On Friday April 22 2016 23:33:27 René J.V. Bertin wrote:
> Looks like I'm going to have to add output to kio_http and see if the error
> message doesn't come from an error==ENOENT returned from a failed function
> call. Seems like something that's going to be fun ...
Looking at when http.cpp
On Friday April 22 2016 21:28:56 David Faure wrote:
> Yep. A qt5/kf5 based konqueror isn't released yet, so who would need this
> yet...
There's a frameworks branch in kde-baseapps that provides "konqueror5", which
isn't missing too much from what I can see ...
> (dunno about rekonq).
I only
On Friday 22 April 2016 20:57:55 René J.V. Bertin wrote:
> On Friday April 22 2016 20:38:09 David Faure wrote:
>
> >> but the cookies KCM considers that the service isn't running? I'd expect
> >> something OS X-specific in the KCM if this didn't happen on Linux too.
> >
> >Ah, that was a bug.
>
On Friday April 22 2016 20:38:09 David Faure wrote:
>> but the cookies KCM considers that the service isn't running? I'd expect
>> something OS X-specific in the KCM if this didn't happen on Linux too.
>
>Ah, that was a bug.
>Fixed --
On Friday 22 April 2016 18:42:34 René J.V. Bertin wrote:
> but the cookies KCM considers that the service isn't running? I'd expect
> something OS X-specific in the KCM if this didn't happen on Linux too.
Ah, that was a bug.
Fixed --
On Friday April 22 2016 15:28:35 David Faure wrote:
> It is, but with a different name. In KDE4 it's
> $ qdbus org.kde.kded /modules/kcookiejar
>
> I moved it to the name "org.kde.kcookiejar5" so that later it can be hosted
> by kiod rather than kded5, transparently.
Right.
So, any ideas
On Friday 22 April 2016 15:17:43 René J.V. Bertin wrote:
> On Friday April 22 2016 10:19:35 David Faure wrote:
>
> > kcookiejar5 is just a client-side tool (*).
>
> And not the tool that applications use to manage cookies?
Right. Apps use library code, rather than command-line tools.
> > The
On Friday April 22 2016 10:19:35 David Faure wrote:
> kcookiejar5 is just a client-side tool (*).
And not the tool that applications use to manage cookies?
> The actual service is provided by a kded module. You can see if it works by
> doing
> $ qdbus org.kde.kcookiejar5 /modules/kcookiejar
On Friday 22 April 2016 09:51:03 René J.V. Bertin wrote:
> Hi,
>
> I'm installing K*5 in a parallel prefix (/opt/local) that also includes Qt,
> on OS X and Linux. On OS X the DBus lives in there while on Linux (KUbuntu
> 14.04) I use the system's DBus which is configured to be aware of
>
10 matches
Mail list logo
