Bug 88488 - Konqueror repeatedly spawns new windows
Summary: Konqueror repeatedly spawns new windows
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-31 01:56 UTC by Jim Philips
Modified: 2006-08-30 18:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Philips 2004-08-31 01:56:09 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Slackware Packages
Compiler:          gcc 3.3.4 
OS:                Linux

After installation of KDE 3.3, Konqueror worked normally. Then I tried to create a theme in Kthememanager. I saved the theme. First odd thing was that window decorations no longer had buttons. I re-enabled the buttons in Control Center. Then I tried to load a URL in Konqueror. It started spawning a new window every time the page loaded. It will do this when loading any URL at all. The only way to interrupt it is to do a "killall konqueror" or kill the X session with ctl-alt-backspace. The problem is in user configs, since there is no problem when I log in as another user. But I have no idea what I would delete in ..kde to stop this behavior.
Comment 1 Jim Philips 2004-09-02 00:29:23 UTC
On Wednesday 01 September 2004 13:55, Stephan Binner wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> You are a voter for the bug, or are watching someone who is.
>
> http://bugs.kde.org/show_bug.cgi?id=88488
> binner kde org changed:
>
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
>- Severity|crash                       |normal

I don't know your categories as well as I might. But when a problem leaves an 
application totally unusable, would that not have a severity of "crash"? If 
not, why? The only way I can stop this madness once it starts is "killall 
konqueror". Of course, if I didn't do that, it *would* crash because it would 
consume all of my memory and lock up X Windows. I just don't let it do that.
Comment 2 Isaac Olson 2004-09-07 14:19:44 UTC
I get the same problem when clicking on a link to a web page from kmail.
I had set konqueror as the browser to handle these links(from Control Center). Works fine with mozilla, but konqueror keeps infinitely spawning windows of the link that's clicked.

Install is on Gentoo, KDE 3.3.
Comment 3 Ian Powell 2005-01-23 12:40:41 UTC
i've been having problems with konqueror for a couple of releases of KDE on 
SuSE 9.1 and SuSE 9.2.
I first came across this when clicking a URL link in an email in Kmail.  It also happens if i load konqueror, enter a URL and press enter. It will keeps respawning itself without actually getting to the desired page (www.bbc.co.uk was used to test), the only way for me to kill the it is to hold Alt F4 down until it stops. (or killall konqueror in kosole)
It first started happening in SuSE 9.1, i posted it to the kde mailing lists but no-one responded so i thought it must be a problem only on my system. I can't remember which KDE version when it started but i have upgaded to 3.3.2 and it still happens. I also upgraded from SuSE 9.1 to 9.2 when it was released hoping that would cure it by wiping the dsk clean but keeping my home drive so ~/.kde is the same. I've tried removing the files in .kde/share/config and .kde/share/apps/konqueror etc but it still happens. 
Comment 4 Joseph Kerian 2006-08-30 17:03:38 UTC
Hmm... bbc's homepage doesn't cause any problems for me at this point... nor can I reproduce the problem from KMail links. (Dapper Kubuntu, KDE 3.5.2) Can anyone confirm that this is still a problem?

One thing I'd like you to look into:
Check in your control panel (System Settings or "kcontrol")
KDE Components -> Default Applications -> Web Browser
If that is set to "in the following browser", you may want to change that back to "in an application based on the contents of the URL", and see if this problem persists.
Comment 5 Aaron J. Seigo 2006-08-30 18:56:46 UTC
resolved via konq bug day irc session