Bug 24986 - konqueror won't launch
konqueror won't launch
Product: Red Hat Linux
Classification: Retired
Component: kdebase (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Aaron Brown
Florence RC-1
: 26298 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2001-01-25 18:32 EST by Tim Waugh
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-06 19:56:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
.xsession-errors (9.11 KB, text/plain)
2001-01-25 18:36 EST, Tim Waugh
no flags Details

  None (edit)
Description Tim Waugh 2001-01-25 18:32:46 EST
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.
Comment 1 Tim Waugh 2001-01-25 18:36:33 EST
Created attachment 8290 [details]
Comment 2 Tim Waugh 2001-01-26 05:20:09 EST
This still happens for me with the qa0126.0 tree.
Comment 3 Tim Waugh 2001-01-26 05:28:48 EST
I should mention that this problem also happens when I click on the
'www.redhat.com' icon, and the other URL icons.
Comment 4 Bernhard Rosenkraenzer 2001-01-26 05:52:31 EST
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*?

Comment 5 Tim Waugh 2001-01-26 06:44:45 EST
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.
Comment 6 Tim Waugh 2001-01-26 07:40:30 EST
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.
Comment 7 Tim Waugh 2001-01-26 08:03:10 EST
(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
Comment 8 Tim Waugh 2001-01-26 08:10:59 EST
Without logging off, I ran the 'rm' command you suggested, and now it works.
Comment 9 Tim Waugh 2001-01-28 08:29:28 EST
This also happens on upgrade from Red Hat Linux 7, or at least it did on the 
machine I'm using now.
Comment 10 Tim Waugh 2001-01-29 13:52:39 EST
Bero, can you reproduce this yet?
Comment 11 Glen Foster 2001-01-29 19:01:37 EST
This defect is considered MUST-FIX for Florence Release-Candidate #1
Comment 12 Bernhard Rosenkraenzer 2001-01-29 19:23:54 EST
Can't reproduce this... Does it happen with glibc-2.2.1-2? With a broken
dlopen(), anything can happen in KDE...
Comment 13 Tim Waugh 2001-01-30 06:04:55 EST
It still happens with 2.2-9 (i386), which is what I had handy.
Comment 14 Tim Waugh 2001-02-02 17:36:08 EST
This also happens on upgrade from Guinness.

Removing just .DCOP* works around the problem.
Comment 15 Bernhard Rosenkraenzer 2001-02-06 12:03:56 EST
*** Bug 26298 has been marked as a duplicate of this bug. ***
Comment 16 Tim Waugh 2001-02-06 19:56:52 EST
I'll try this again on a qa0206.0 install tomorrow morning.
Comment 17 Tim Waugh 2001-02-07 06:51:15 EST
Okay, I can't get this to happen now.  I'm using the 20010205 packages from
qa0206.0.  I think it must be fixed.

Note You need to log in before you can comment on or make changes to this bug.