After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 623605 - [Win32] Web links in help menu don't work
[Win32] Web links in help menu don't work
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
1.10.x
Other Windows
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2010-07-05 14:02 UTC by Pedro Lino
Modified: 2010-07-09 01:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pedro Lino 2010-07-05 14:02:11 UTC
The "Visit the Gnumeric website" link in the About box doesn't work. It returns "Could not show link. HEAD request failed: WinHttp error: CANNOT_CONNECT"

The Help menu options "Gnumeric on the Web" and "Report a Problem" return the same error (these two used to work in version 1.9.x)

The Help menu option "Live Assistance" returns "Error stating file 'C:\Program Files\Gnumeric\1.10.7\bin\irc:\irc.gnome.org\gnumeric': No such file or directory"
The link should be irc://irc.gnome.org:6666/gnumeric with slashes instead of backslashes and with the port number
Comment 1 Andreas J. Guelzow 2010-07-05 16:43:20 UTC
In gnumeric we have:
show_url (wbcg, "irc://irc.gnome.org/gnumeric");
which effectively is:
go_gtk_url_show (url, screen); with url being "irc://irc.gnome.org/gnumeric"

What go_gtk_url_show does depends on HAVE_GTK_SHOW_URI. Assuming a recent version of GTK that is simply 
gtk_show_uri (screen, url, GDK_CURRENT_TIME, &error);
which makes this a gtk bug.
Comment 2 Pedro Lino 2010-07-05 17:26:34 UTC
Ok. What about the Http errors? These used to work in version 1.9.x (except for the link in the About box that never worked)
Comment 3 Andreas J. Guelzow 2010-07-05 18:37:34 UTC
The http requests go through the same go_gtk_url_show...gtk_show_uri... chain. So I wouldn't be surprised if that is the same error. This "HEAD request" is strange though.

I don't have MSWindows and it works fine under Linux so I can't debug this.
Comment 4 Pedro Lino 2010-07-05 21:16:25 UTC
As I have said several times, if you post a debug build I can send you the log file. I do this for a project where I am the main beta tester...
Comment 5 Andreas J. Guelzow 2010-07-05 22:21:26 UTC
Yes you have said that often, but I have no idea how to build a debug build for MSWindows.
Comment 6 Pedro Lino 2010-07-06 00:10:36 UTC
Some of Jody's Windows binaries were named debug (although I never found any log files). Maybe he can help you?
Comment 7 Morten Welinder 2010-07-06 19:35:37 UTC
The "debug" in Jody's build related to debug information for a debugger.
I could create such a beast, but without a skilled gdb operator, I don't
see what good it would do.
Comment 8 Morten Welinder 2010-07-06 19:38:18 UTC
Bug 622125 is possibly relevant.
Comment 9 Andreas J. Guelzow 2010-07-06 20:33:46 UTC
@Morten: Assuming this is your windows build, are you including gvfs? (THat's teh issue in bug # 622125.)

re the debug build, I think Pedro envisions a build that has bee speckled with commands to write info to a log file. The only thing here which would be interesting to know is what the arguments are that go_gtk_url_show and gtk_show_uri are called with and what there return values really are.
Comment 10 Morten Welinder 2010-07-06 20:59:23 UTC
I'll throw a debugger and/or a bunch of print statements at the problem later.
Comment 11 Morten Welinder 2010-07-07 13:20:23 UTC
The relevant glib/gio apis just aren't implemented for win32.

http://git.gnome.org/browse/glib/tree/gio/gwin32appinfo.c#n618

It isn't my job to debug glib/gio so I'll just hack around it.
Comment 12 Morten Welinder 2010-07-09 01:24:45 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.