[KIO] cookie service and installing in a parallel prefix (/opt/local)

[René J.V. Bertin]

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 returns ERR_DOES_NOT_EXIST I had a hunch and turned off the web cache. Lo and behold, pages started to load, so the error must be in the caching <whatever>.

I keep getting a crash on exist though:

    frame #3: 0x000000010ca5bde9 libKF5Crash.5.dylib`KCrash::defaultCrashHandler(sig=<unavailable>) + 1049 at kcrash.cpp:527
    frame #4: 0x00007fff8b9645aa libsystem_platform.dylib`_sigtramp + 26
    frame #5: 0x000000010dc6db50 QtCore`QCache<QString, bool>::insert(this=0x00007f85eb6f3090, akey=<unavailable>, aobject=<unavailable>, acost=<unavailable>) + 368 at qcache.h:173
    frame #6: 0x000000010dc6c6d8 QtCore`setNativeLocks(QString const&, int) [inlined] QStringBuilder<QString, QString>::operator QString(fn=0x00007f85eb41a500, a=0x00007f85eb41a3b0, b=0x00007f85eb44e350, rc=<unavailable>) const + 218 at qlockfile_unix.cpp:142
    frame #7: 0x000000010dc6c5fe QtCore`setNativeLocks(fileName=<unavailable>, fd=7) + 126 at qlockfile_unix.cpp:160
    frame #8: 0x000000010dc6be24 QtCore`QLockFilePrivate::tryLock_sys(this=0x00007f85edbd1030) + 612 at qlockfile_unix.cpp:190
    frame #9: 0x000000010dc11870 QtCore`QLockFile::tryLock(this=<unavailable>, timeout=-1) + 112 at qlockfile.cpp:212
    frame #10: 0x000000010c3c0474 libKF5ConfigCore.5.dylib`KConfigIniBackend::lock(this=0x00007f85eb59eb20) + 260 at kconfigini.cpp:635
    frame #11: 0x000000010c3a9a13 libKF5ConfigCore.5.dylib`KConfig::sync() [inlined] KConfigPrivate::lockLocal(this=<unavailable>) + 275 at kconfig.cpp:109
    frame #12: 0x000000010c3a9a01 libKF5ConfigCore.5.dylib`KConfig::sync(this=<unavailable>) + 257 at kconfig.cpp:420
    frame #13: 0x000000010c3a8838 libKF5ConfigCore.5.dylib`KConfig::~KConfig() [inlined] KConfig::~KConfig(this=0x00007f85eb52b310) + 46 at kconfig.cpp:272
    frame #14: 0x000000010c3a880a libKF5ConfigCore.5.dylib`KConfig::~KConfig(this=0x00007f85eb52b310) + 10 at kconfig.cpp:269
    frame #15: 0x000000010bc4aecb libKF5KIOCore.5.dylib`KIO::FavIconsCache::~FavIconsCache() [inlined] KIO::FavIconsCachePrivate::~FavIconsCachePrivate(this=0x00007f85eb52b300) + 118 at faviconscache.cpp:78
    frame #16: 0x000000010bc4ae55 libKF5KIOCore.5.dylib`KIO::FavIconsCache::~FavIconsCache() [inlined] KIO::FavIconsCachePrivate::~FavIconsCachePrivate(this=0x00007f85eb52b300) at faviconscache.cpp:78
    frame #17: 0x000000010bc4ae55 libKF5KIOCore.5.dylib`KIO::FavIconsCache::~FavIconsCache(this=0x000000010bc83920) + 37 at faviconscache.cpp:117
    frame #18: 0x00007fff80fb37b5 libsystem_c.dylib`__cxa_finalize + 177
    frame #19: 0x00007fff80fb3a60 libsystem_c.dylib`exit + 22
    frame #20: 0x00007fff8ad2e604 libdyld.dylib`start + 8

If it were me I'd just disable support for favicons completely but that is apparently not foreseen ...

R.