Bug 856169 - Konqueror gets into an infinite loop when browsing through its menu
Summary: Konqueror gets into an infinite loop when browsing through its menu
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-baseapps
Version: 18
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-09-11 11:16 UTC by Martin Bříza
Modified: 2014-02-05 12:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-02-05 12:09:41 UTC
Type: Bug

Attachments (Terms of Use)
Screenshot of the triggered bug (187.94 KB, image/png)
2012-09-11 11:16 UTC, Martin Bříza
no flags Details

Description Martin Bříza 2012-09-11 11:16:50 UTC
Created attachment 611728 [details]
Screenshot of the triggered bug

Description of problem:
Konqueror gets into an infinite loop when browsing through its menu hogging the UI

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start a clean Konqueror (keeping any previously set configuration will not reveal the bug)
2. Do the usual Alpha test matrix steps (logging into admin.fedoraproject.org, downloading a Linux kernel in a new tab)
3. In the tab with the kernel, quickly browse through the menus, be sure to open Tools -> HTML Settings

Actual results:
The whole system stops responding to anything else than switch to a TTY. Konqueror is then taking about 97% of the CPU according to top.

Expected results:
Opening menu items

Additional info:
I've attached a screenshot with the opened menu and konqueror debug log. The menu opened triggered the bug and left the system in this state.

Comment 1 Jaroslav Reznik 2012-09-11 12:55:04 UTC
I'm unable to reproduce it. Tried for several times...

Comment 2 Lukáš Tinkl 2012-09-14 10:05:35 UTC
Perhaps this depends on the installed konqueror plugins, or even on the rendering engine? (khtml vs. webkit)

Comment 3 Martin Bříza 2012-09-17 09:45:57 UTC
Well, I didn't change anything, it happened in Konqueror as it is in Fedora 18 by default, so no plugins and I suppose KHTML is the default rendering engine.

Comment 4 Martin Bříza 2012-11-22 13:07:18 UTC
Still happens in Fedora 18 Beta RC1.

Comment 5 Fedora End Of Life 2013-12-21 08:51:11 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2014-02-05 12:09:43 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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