Red Hat Bugzilla – Bug 24986
konqueror won't launch
Last modified: 2007-04-18 12:30:55 EDT
Fresh install (from oot tree between 7.1-beta3 and qa0125.0)
Typing in a URL (such as https://bugzilla.redhat.com/bugzilla) into the
Alt-F2 dialog causes an 'examining file' dialog to momentarily display,
followed by a 'konqueror' entry in the task bar, but then it disappears
and that's the end of it.
Running konqueror from a konsole works fine. I'll attach my
.xsession-errors, from a session in which I have several attempts to
launch konqueror from Alt-F2, followed by one from a konsole.
I see that there are newer KDE packages; I'll give those a go tomorrow.
Created attachment 8290 [details]
This still happens for me with the qa0126.0 tree.
I should mention that this problem also happens when I click on the
'www.redhat.com' icon, and the other URL icons.
This is odd... I can't reproduce any of this, and there are a number of
"Connection refused" errors in your .xsession errors.
Could this be caused by a firewall blocking the connection? Are you trying to
launch konqueror in a remote session? Are kded and dcopserver running?
Does it still happen if you rm -rf ~/.k* ~/.DCOP* /tmp/mcop*?
IPchains problems was my first thought, and so I made sure that lokkit wrote a
'no firewall' config and did 'service ipchains restart'.
It's running locally, on my machine at home. Unfortunately I'm at work now, but
I'll see if I can get it to work remotely by logging in using kdm. I'll try
removing those files.
Huh. Okay, running Xnest :1 -query localhost -geometry 640x480 while logged in
using ssh with X forwarding, it works fine, without me having done anything
I'll pop back and try it again without changing anything, and again after
removing those files.
(Still at work)
I added a new user with useradd, and logged in as them and clicked on 'Linux
Documents', and this happened again, and I have a 'connect() failed' in the
Without logging off, I ran the 'rm' command you suggested, and now it works.
This also happens on upgrade from Red Hat Linux 7, or at least it did on the
machine I'm using now.
Bero, can you reproduce this yet?
This defect is considered MUST-FIX for Florence Release-Candidate #1
Can't reproduce this... Does it happen with glibc-2.2.1-2? With a broken
dlopen(), anything can happen in KDE...
It still happens with 2.2-9 (i386), which is what I had handy.
This also happens on upgrade from Guinness.
Removing just .DCOP* works around the problem.
*** Bug 26298 has been marked as a duplicate of this bug. ***
I'll try this again on a qa0206.0 install tomorrow morning.
Okay, I can't get this to happen now. I'm using the 20010205 packages from
qa0206.0. I think it must be fixed.