Bug 469606
Summary: | galeon says "myportal is not a registered protocol" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
Component: | galeon | Assignee: | Denis Leroy <denis> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 10 | CC: | denis, gecko-bugs-nobody, tpeplt |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.0.7-15.fc11 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-23 07:40:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2008-11-03 05:15:56 UTC
In 'configure' script for galeon there is the following: Note that Galeon has a runtime dependency on the 'cookie' and 'permission' mozilla extensions. These are not built as part of the default xulrunner build, and must be added explicitly at xulrunner configure-time. This is printed on a screen when configuring galeon to build with xulrunner or libxul-embedding or libxul-embedding-unstable. OTOH about:buildconfig in galeon appears to show a build configuration for an underlying xulrunner (galeon-2.0.7-2.fc10 and xulrunner-1.9.0.2-5.fc10). The only extensions mentioned there are default and python/xpcom. Maybe that is it what is causing the problem? In any case it looks like that a used xulrunner configuration is not good enough for galeon needs. The quoted text says "must". It has also some followup text which warns agains using 'typeaheadfind' and 'wallet' extensions but those are indeed absent - at least for the moment. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fixed in next release. galeon-2.0.7-15.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/galeon-2.0.7-15.fc11 galeon-2.0.7-15.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. $ rpm -q galeon galeon-2.0.7-15.fc11.x86_64 $ rpm -V galeon && echo $? 0 $ cat /etc/fedora-release Fedora release 11 (Leonidas) The following steps still lead to the error message "myportal is not a registered protocol" being displayed: 1. Click on 'Go' in galeon's main menu. 2. Click on 'My Portal' in the Go sub-menu. An error message window with a lightbulb icon and the text "myportal is not a registered protocol" is displayed. Should this be reported as a separate error in galeon in the Fedora 11? A patch would be preferred... we just need to remove it from the menu... (In reply to comment #7) > A patch would be preferred... we just need to remove it from the menu... Is 'myportal' no longer a feature of galeon? Here is some of the documentation describing it in the galeon User's Guide. At present, these features do work as described in the manual. "'My Portal' creates a portal style view of your bookmarks in a web page. It makes a good choice for your homepage, since it provides a rapid way of jumping to a large number of bookmarks. You can visit 'My Portal' at any time by opening the URL about:myportal, or you can set it as your homepage, as described in Section 3.1 ― General." and Home Page "When Galeon first starts up, it will automatically load the page specified here. Type an address into the entry bar or, if you are currently viewing a page you would like to set as your permanent home page, click the Set to Current button. If you want the 'My Portal' page your home page by (sic), type in myportal:." |