Version: 1.4 (using 4.4.2 (KDE 4.4.2), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS: Linux (i686) release 2.6.34-rc5 If I call dolphin from the command line gievn a zip file as first argument I get : tfoerste@n22 ~/tmp $ dolphin foo.zip Object::connect: No such slot DolphinSearchBox::slotClearButtonClicked() Object::connect: No such signal DolphinController::requestUrlChange(const KUrl&) Object::connect: No such signal DolphinController::requestUrlChange(const KUrl&) KDirWatch: /home/tfoerste/tmp/Report_QA.zip is a file. Use addFile! tfoerste@n22 ~/tmp $ Object::disconnect: Unexpected null parameter If I then close dolphin it quacked furthermore this : tfoerste@n22 ~/tmp $ dolphin(9673)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: dolphin(9673)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: dolphin(9673)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: dolphin(9673)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: Object::disconnect: Unexpected null parameter dolphin(9673)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kDebugStream called after destruction (from void KDirWatchPrivate::removeEntry(KDirWatch*, KDirWatchPrivate::Entry*, KDirWatchPrivate::Entry*) file /var/tmp/portage/kde-base/kdelibs-4.4.2/work/kdelibs-4.4.2/kio/kio/kdirwatch.cpp line 950) Cancelled INotify (fd 10, 1) for "/home/tfoerste/.local/share//user-places.xbel" I'm wondering whether this is harmless or not.
The only difference with starting dolphin without any parameter is the following line: KDirWatch: /home/tfoerste/tmp/Report_QA.zip is a file. Use addFile! @Peter: is this a problem?
@FiNeX: I don't think this is a problem (in any case it is out of scope of Dolphin) As the missing slots above have been fixed, I've set this report to RESOLVED. Thanks Toralf for reporting this warnings.