|
Bugzilla – Full Text Bug Listing |
| Summary: | invalid URI error when opening help from eog | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Tim Lee <timlee> |
| Component: | GNOME | Assignee: | Hans Petter Jansson <hpj> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | akhil.laddha, coolo, forgotten_taWGjDL4xO, kkaempf, mgoppold |
| Version: | Beta 1 | Flags: | coolo:
SHIP_STOPPER+
|
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Tim Lee
2007-08-09 19:43:13 UTC
*** Bug 299648 has been marked as a duplicate of this bug. *** *** Bug 304137 has been marked as a duplicate of this bug. *** *** Bug 299428 has been marked as a duplicate of this bug. *** Together with all the dupes, this bug essentially says that most GNOME applications have non-working help! (Almost all I tried; some pop up error window [gnome-volume-manager], for some [gnome-power-manager] just nothing happens - I'm not sure if that is the same bug, I'm assuming so.) Still happens in beta3. This is happening because Yelp no longer handles help:// URIs, only file:// and ghelp:// - the relevant code was cut from upstream. I'll see if I can patch libgnome to pass file:// or ghelp:// URIs. Also, EOG's way of specifying its doc path is wrong. It's supposed to be either "file:///usr/share/gnome/help/eog/C/eog.xml" or "ghelp://eog". Most applications randomly combine a scheme and a way of specifying the path. It looks like I can't fix this in libgnome. The failing apps are using gnome_url_show() on non-compliant URIs. So it needs to be fixed in "rarian". *** Bug 308025 has been marked as a duplicate of this bug. *** *** Bug 309045 has been marked as a duplicate of this bug. *** *** Bug 309047 has been marked as a duplicate of this bug. *** Will this be fixed in RC1 after the backrevs? Yes, fixed by backrevs that have now been submitted. |