Bug 320858 - Search bar not cleared when starting a Konqueror preloaded instance
Summary: Search bar not cleared when starting a Konqueror preloaded instance
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: searchbarplugin (show other bugs)
Version: 4.10.4
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: Arend van Beelen jr.
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-07 11:40 UTC by Víctor Fernández
Modified: 2023-02-12 03:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Víctor Fernández 2013-06-07 11:40:02 UTC
I can type some text in the search bar to search for something. After that, I close the Konqueror window and later open a new window of Konqueror by starting it from the K menu. The text I typed before is still visible in the search bar. It is not cleared.

My Konqueror is configured to keep 1 instance loaded. If I send SIGTERM to the konqueror process, or if I start a new instance, the search bar is empty.

This behaviour is inconherent. The search bar should always be cleared.

Reproducible: Always

Steps to Reproduce:
1. Configure Konqueror to keep one running instance in memory.
2. Type some text in the search bar. You don't even need to make the actual search; it is enough to type something.
3. Close Konqueror and start it again.
Actual Results:  
Text is present in search bar.

Expected Results:  
Search bar should be empty.
Comment 1 Andrew Crouthamel 2018-11-10 03:22:36 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:46:07 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-13 01:36:41 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-28 05:08:27 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-02-12 03:50:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!