Bug 218162 - No graceful handling when there is no default search engine defined
Summary: No graceful handling when there is no default search engine defined
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.3.4
Platform: Compiled Sources Unspecified
: NOR minor
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-10 20:37 UTC by Richard Hartmann
Modified: 2022-11-12 05:15 UTC (History)
0 users

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 Richard Hartmann 2009-12-10 20:37:44 UTC
Version:            (using KDE 4.3.3)
Installed from:    Compiled From Sources

Problem:

Enter 'foo' in the address bar & press enter. You get an error stating that the 'protocol [is] not supported'.

Reproduce:

* Start Konqui
* Settings
* Configure Konqueror
* Web Shortcuts
* Select "None" as default search engine
* Save & exit
* Enter "foo" in address bar, get error

This is somewhat confusing. It would be better to tell the user that there is no default search engine defined or something.
Comment 1 Dawit Alemayehu 2011-12-20 06:39:20 UTC
You no longer get 'protocol is not supported' error message. You now get imporoperly formatted URL error message, which is more accurate description of the problem.

Konqueror does not know there is not search engine configured because the URI filtering mechanism is globally definited and not specific to konqueror's code. Moreover, even if it did there could be a number of reasons why foo did not qualify for being handled by konqueror.

Regardless, this is not a bug. Arguably a minor issue that can be perhaps improved, perhaps... Marking it as minor.
Comment 2 Justin Zobel 2022-10-13 04:47:34 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported and confirmed, 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 "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-10-28 05:02:13 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 4 Bug Janitor Service 2022-11-12 05:15:00 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!