Version: 4.00.80 (KDE 4.0.80 >= (KDE 4.1 Beta1) (using 4.00.80 (KDE 4.0.80 >= (KDE 4.1 Beta1), Kubuntu packages) Compiler: gcc OS: Linux (i686) release 2.6.24-19-generic For a totally unknown reason, konqueror displays : The requested operation could not be completed Cannot Initiate the http Protocol Technical Reason: Unable to Launch Process ... Additional Information: Cannot talk to klauncher: Connection is closed ... But Klauncher is running... This happens every day and I haven't found a solution except restarting konqueror. It may occur with any URL... Any other tab in the current konqueror is also screwed up ! dc
At one point, konqueror seem to have lost its connection to klauncher. Then any further operation on the instance will end up with the same message. It just occured while doing : File -> New Tab dc
Does an upgrade fix this?
I also have this problem with 4.0.98 on Debian experimental. In my case, on already existing instances of konqueror there's a moment when opening a new tab, refresh a currently opened tab or any other similar operation doesn't complete with the message: "Can't start hppt process" and "Can't stablish communication with klauncher: Connection is closed" This is what I get in the ~/.xsession-errors: konqueror(22690) KToolInvocation::klauncher: klauncher not running... launching kdeinit kdeinit4: Shutting down running client. klauncher: Exiting on signal 15 kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher kdeinit4: preparing to launch /usr/bin/kded4 KDE Daemon (kded) already running. kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kbuildsycoca4(27527) kdemain: Reusing existing ksycoca QObject: Do not delete object, 'unnamed', during its event handler! konqueror(22690) KToolInvocation::klauncher: klauncher not running... launching kdeinit kdeinit4: Shutting down running client. klauncher: Exiting on signal 15 kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher kdeinit4: preparing to launch /usr/bin/kded4 KDE Daemon (kded) already running. kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kbuildsycoca4(27540) kdemain: Reusing existing ksycoca QObject: Do not delete object, 'unnamed', during its event handler! konqueror(22690): couldn't create slave: "No se puede dialogar con klauncher: Connection is closed" If I want to do anything usable with konqueror I need to start a new instance and it will work. There's also the possibility that eventually this new instance gets into the same trouble. I'm not sure but this may be a duplicate of http://bugs.kde.org/show_bug.cgi?id=157853 Regards,
Also occur on KDE Version 4.1.00 (KDE 4.1.0) (KDE 4.1.00 (KDE 4.1.0), Kubuntu packages) Operating System Linux (i686) release 2.6.24-19-generic This bug is very annoying!
It just happened here too. KDE 4.1.0, debian packages. No idea how. I had a konqueror window open in one desktop, then opened another via krunner in another desktop and visited a few links. After some hour had passed and I had used again the first konqueror window many times, I went back to the second window to visit a link and I got that message. The first window however continued to work fine.
So, I found a standard way to reproduce this. The procedure is the same as in bug 167667, not sure if they are the same bug after all... ;) The procedure is as follows: 1) Configure konqueror to open external links in new tabs. 2) Close all open konqueror windows. 3) Fire up your irc client, join #kde, click the www.kde.org link on the topic. (you can actually do this with any program that opens links externally, but the irc client was easier for me.) Ok, clicking the link will open a konqueror window showing the kde homepage. 4) Move the irc client to another desktop, click to open the link again. It will open it in a new konqueror window and it will ask you to restore the session. If you click to restore, it will restore the session as it currently is on the first desktop. Bug 167667 reproduced ;) 5) Close the konqueror window that just opened. 6) Now move the irc client back to the previous desktop, click to open again that link on the topic. It won't use the existing konqueror window as it should (from the configuration you did on step 1), but it will open a new one and it will prompt again to restore the session. Bug 167667 reproduced for the second time ;) 7) Close the konqueror window that just opened. 8) Go to the first konqueror window that was open from step 3 and try to visit a link. It will complain that it cannot talk to klauncher!
This bug happens all the time for me(kubuntu 8.04 amd64 with kde4.1.0 and all updates). It seems when I leave a konqueror window(configure to open new external etc windows in tabs) open for a while then try use it again a little later it says this error message. Happens everyday many times a day and is terribly annoying.
It seems that it succeeds every time I click on a link in kmail. The new konqueror window asks me if I want to restore the old session. The old konqueror window is not usable anymore. (KDE 4.1.0 - debian packages)
I see this too on fedora9@x86_64 with kdebase-4.1.1-1.fc9.x86_64
(gdb) bt #0 0x0000003f21ada9bf in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:83 #1 0x0000003cabc3aaa8 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2954 #2 0x0000003cabc3adcb in IA__g_main_context_iteration (context=<value optimized out>, may_block=<value optimized out>) at gmain.c:2708 #3 0x0000003cad16b24f in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4 #4 0x0000003cad141662 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4 #5 0x0000003cad1417ed in QEventLoop::exec () from /usr/lib64/libQtCore.so.4 #6 0x0000003cad143cbd in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4 #7 0x0000003cac80d9b8 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdelibs-4.1.1/kinit/klauncher_main.cpp:118 #8 0x0000003f21a1e32a in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=Could not find the frame base for "__libc_start_main". ) at libc-start.c:220 #9 0x00000000004007c9 in _start ()
0x0000003f21ada9bf in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:83 83 return INLINE_SYSCALL (poll, 3, CHECK_N (fds, nfds), nfds, timeout); (gdb) bt #0 0x0000003f21ada9bf in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:83 #1 0x0000003cabc3aaa8 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2954 #2 0x0000003cabc3adcb in IA__g_main_context_iteration (context=<value optimized out>, may_block=<value optimized out>) at gmain.c:2708 #3 0x0000003cad16b24f in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4 #4 0x0000003cad141662 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4 #5 0x0000003cad1417ed in QEventLoop::exec () from /usr/lib64/libQtCore.so.4 #6 0x0000003cad143cbd in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4 #7 0x0000003cac80d9b8 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdelibs-4.1.1/kinit/klauncher_main.cpp:118 #8 0x0000003f21a1e32a in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=Could not find the frame base for "__libc_start_main". ) at libc-start.c:220 #9 0x00000000004007c9 in _start () Current language: auto; currently c (gdb)
@Juha: Why did you paste a backtrace of the event loop twice?
comment #12: > Why did you paste a backtrace of the event loop twice? perhaps this bug is giving me mental problems?
Another data point which may or may not help... this bug triggers for me several times a day, on average. One thing I've noticed is that I seem to get lingering instances of Konqueror running after I close them to restart new instances. strace and lsof on one such process indicates that it's in a poll() loop, waiting for input for from a variety of sources (a pipe, Unix socket, inotify, and a FIFO). However, qdbus doesn't list these konqueror processes.
@Christophe: What you are describing is either bug 167826 or bug 170461 (depending on your kde version) and it's not much related to this bug afaict.
This bug is really annoying, mine konqueror stops working after 5-10 mins and then i need to move all urls into new browser if i want to continue to work like that. I should move to firefox for good.
Just keep *one* konqueror instance running and on *one* desktop only (that's what I do) and you won't even notice that this bug exists :D The disaster only comes when you open external links from other desktops, which you should avoid until the konqueror developers fix this.
Still present in Version 4.1.2 "release 44.1" (openSUSE 11.1beta2)
comment #17 > Just keep *one* konqueror instance running and on *one* desktop > only (that's what I do) and you won't even notice that this bug exists I could also run twm and save some rainforests with that, without noticing the difference. Seriously, we have enough bells and whistles, but this causes lost working hours. Could the fact that I'm using NFS home cause this? Does others have it?
I am not using NFS home
I can confirm this bug with the same symptoms as Vincent (comment #8).
Step 3 can be simplified by simply typing "kfmclient openURL http://www.kde.org" in a terminal. Here konq crashes when doing that (if it's on another desktop); something about wrong QDBusObjectPath usage, investigating.
I just fixed 167667, and I can't reproduce this bug. Can you please re-test with r870787 or later? (either branch or trunk)
MeToo I'm seeing this on Ubuntu, both 8.04 prior to update, and on an update to intrepid. Konqueror Version 4.1.2 (KDE 4.1.2) Package: konqueror State: installed Automatically installed: no Version: 4:4.1.2-0ubuntu4 Priority: optional Section: web Maintainer: Kubuntu Developers <kubuntu-devel@lists.ubuntu.com> Uncompressed Size: 3977k Depends: kdebase-runtime (>= 4:4.1.2), kdelibs5 (>= 4:4.1.2), libc6 (>= 2.4), libkonq5, libqt4-dbus (>= 4.4.3), libqt4-qt3support (>= 4.4.3), libqt4-xml (>= 4.4.3), libqtcore4 (>= 4.4.3), libqtgui4 (>= 4.4.3), libstdc++6 (>= 4.1.1), libx11-6, zlib1g (>= 1:1.1.4), kdebase-data (>= 4:4.1.2-0ubuntu4) Recommends: konqueror-nsplugins (= 4:4.1.2-0ubuntu4) Conflicts: konqueror-kde4 Replaces: konqueror-kde4 Provides: info-browser, man-browser, www-browser Description: KDE 4's advanced file manager, web browser and document viewer Konqueror is the KDE web browser and advanced file manager. Tabs are enabled. I generally have multiple konqueror windows open. On page load or reload I frequently see: The requested operation could not be completed Cannot Initiate the http Protocol Technical Reason: Unable to Launch Process Details of the Request: URL: http://www.sfgate.com/ Protocol: http Date and Time: Tuesday 04 November 2008 09:24 Additional Information: Unable to create io-slave: klauncher said: Unknown protocol ''. (<additional description, possible cause, possible solution omitted) Reloading, sometimes multiple times, eventually clears this.
I just tested this with trunk and it is fixed. Thanks David :)