http://bugs.winehq.org/show_bug.cgi?id=11960
Summary: Legacy 5 - created web pages cannot be viewed in browser from within Legacy. Product: Wine Version: 0.9.57. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: aganderson@ukonline.co.uk
While checking out functionality of Legacy 5, I created a set of web pages successfully, except that the dialog option to view the pages in a browser did not work, either with Konqueror or Firefox.
I had created the pages to a folder in my home folder [drive y:], and I think the browsers were objecting to this address. Drive d: caused same trouble, etc.
The window for selecting the location for the creation of the web pages cannot give access to conventional linux drive addresses, instead it offers only windows drives.
The pages are accessible directly via browser, just not via Legacy.
http://bugs.winehq.org/show_bug.cgi?id=11960
--- Comment #1 from Lei Zhang thestig@google.com 2008-03-09 19:55:25 --- so you're saying legacy 5 is trying to launch konqueror / firefox with a file:///y:/... url?
http://bugs.winehq.org/show_bug.cgi?id=11960
allan aganderson@ukonline.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aganderson@ukonline.co.uk
--- Comment #2 from allan aganderson@ukonline.co.uk 2008-03-10 06:07:25 --- (In reply to comment #0)
While checking out functionality of Legacy 5, I created a set of web pages successfully, except that the dialog option to view the pages in a browser did not work, either with Konqueror or Firefox.
I had created the pages to a folder in my home folder [drive y:], and I think the browsers were objecting to this address. Drive d: caused same trouble, etc.
The window for selecting the location for the creation of the web pages cannot give access to conventional linux drive addresses, instead it offers only windows drives.
The pages are accessible directly via browser, just not via Legacy.
(In reply to comment #1)
so you're saying legacy 5 is trying to launch konqueror / firefox with a file:///y:/... url?
Not exactly.
When Legacy launches Konqueror, Konqueror throws up "Protocol not supported y" error. If I try to access the pages via Wine's drive d:, then "protocol d is not supported".
If I set it to launch Firefox, Firefox says it doesn't know how to access this address because no application is associated with the protocol (y).
Allan
http://bugs.winehq.org/show_bug.cgi?id=11960
--- Comment #3 from Lei Zhang thestig@google.com 2008-03-10 08:06:45 --- can you run:
WINEDEBUG=+exec,+winebrowser wine legacy_app_name.exe > legacy_log.txt 2>&1
and attach legacy_log.txt to this bug report?
http://bugs.winehq.org/show_bug.cgi?id=11960
--- Comment #4 from allan aganderson@ukonline.co.uk 2008-03-10 12:43:59 --- (In reply to comment #3)
can you run:
WINEDEBUG=+exec,+winebrowser wine legacy_app_name.exe > legacy_log.txt 2>&1
and attach legacy_log.txt to this bug report?
I entered WINEDEBUG=+exec,+winebrowser wine "c:\Legacy\legacy.exe" > legacy_log.txt 2>&1 which I presume is what you wanted. Legacy launched, I produced the web pages and confirmed I wished to view them in my browser, and a log was produced, but did not seem to have anything significant - just a bunch of 'fixme's, so I engaged brain.
Now, I have been using my **linux** browsers (inc. Konqueror as I indicated) and I realised this might be a problem, even though Legacy could launch them and access the Legacy site.
So I installed IE in wine and am now able to browse the web pages OK.
However, it still is not possible to check for updates from Legacy - it just times out. I've just checked on XP and it responds immediately. I did mention this as a possible problem in my initial bug. On the same dialog box used to check for updates, there is a link to 'See what's new' and that works as expected. Should I raise it as a separate bug, please?
Allan
http://bugs.winehq.org/show_bug.cgi?id=11960
--- Comment #5 from Lei Zhang thestig@google.com 2008-03-10 15:03:17 --- (In reply to comment #4)
(In reply to comment #3)
can you run:
WINEDEBUG=+exec,+winebrowser wine legacy_app_name.exe > legacy_log.txt 2>&1
and attach legacy_log.txt to this bug report?
I entered WINEDEBUG=+exec,+winebrowser wine "c:\Legacy\legacy.exe" > legacy_log.txt 2>&1 which I presume is what you wanted. Legacy launched, I produced the web pages and confirmed I wished to view them in my browser, and a log was produced, but did not seem to have anything significant - just a bunch of 'fixme's, so I engaged brain.
From what I remember, the way Wine launches an external web browser is through
shellexec and winebrowser. Maybe legacy is doing it differently, which would explain why those logs came up empty.
Now, I have been using my **linux** browsers (inc. Konqueror as I indicated) and I realised this might be a problem, even though Legacy could launch them and access the Legacy site.
So I installed IE in wine and am now able to browse the web pages OK.
Did you install ies4linux? We can't support that BTW.
However, it still is not possible to check for updates from Legacy - it just times out. I've just checked on XP and it responds immediately. I did mention this as a possible problem in my initial bug. On the same dialog box used to check for updates, there is a link to 'See what's new' and that works as expected. Should I raise it as a separate bug, please?
Allan
Yes, please file a separate bug. There's been some wininet issues lately.
BTW, is this the website for the program? http://www.legacyfamilytree.com/
http://bugs.winehq.org/show_bug.cgi?id=11960
allan aganderson@ukonline.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #6 from allan aganderson@ukonline.co.uk 2008-03-10 18:05:36 --- (In reply to comment #5)
(In reply to comment #4)
(In reply to comment #3)
can you run:
WINEDEBUG=+exec,+winebrowser wine legacy_app_name.exe > legacy_log.txt 2>&1
and attach legacy_log.txt to this bug report?
I entered WINEDEBUG=+exec,+winebrowser wine "c:\Legacy\legacy.exe" > legacy_log.txt 2>&1 which I presume is what you wanted. Legacy launched, I produced the web pages and confirmed I wished to view them in my browser, and a log was produced, but did not seem to have anything significant - just a bunch of 'fixme's, so I engaged brain.
From what I remember, the way Wine launches an external web browser is through shellexec and winebrowser. Maybe legacy is doing it differently, which would explain why those logs came up empty.
Now, I have been using my **linux** browsers (inc. Konqueror as I indicated) and I realised this might be a problem, even though Legacy could launch them and access the Legacy site.
So I installed IE in wine and am now able to browse the web pages OK.
Did you install ies4linux? We can't support that BTW.
I used wine-doors.
However, it still is not possible to check for updates from Legacy - it just times out. I've just checked on XP and it responds immediately. I did mention this as a possible problem in my initial bug. On the same dialog box used to check for updates, there is a link to 'See what's new' and that works as expected. Should I raise it as a separate bug, please?
Allan
Yes, please file a separate bug. There's been some wininet issues lately.
BTW, is this the website for the program? http://www.legacyfamilytree.com/
Yes, that's the one.
http://bugs.winehq.org/show_bug.cgi?id=11960
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |WORKSFORME
--- Comment #7 from Lei Zhang thestig@google.com 2008-03-10 18:44:19 --- Hmm, I downloaded Legacy 5 here: http://www.legacyfamilytree.com/Download/Legacy5/sng1/Legacy5Setup.exe
- Started with a fresh .wine directory - Installed Legacy 5 - Started the app, opened the sample family database - Created a webpage - It asked me if I wanted to view the webpage, I clicked yet
result - Firefox opened file:///home/thestig/.wine/drive_c/Legacy/web/sample/index.htm successfully. No need to install wine-doors or do anything special.
http://bugs.winehq.org/show_bug.cgi?id=11960
--- Comment #8 from allan aganderson@ukonline.co.uk 2008-03-10 20:46:58 --- (In reply to comment #7)
Hmm, I downloaded Legacy 5 here: http://www.legacyfamilytree.com/Download/Legacy5/sng1/Legacy5Setup.exe
- Started with a fresh .wine directory
- Installed Legacy 5
- Started the app, opened the sample family database
- Created a webpage
- It asked me if I wanted to view the webpage, I clicked yet
result - Firefox opened file:///home/thestig/.wine/drive_c/Legacy/web/sample/index.htm successfully. No need to install wine-doors or do anything special.
That's good!! No oleauto32 or vbasic?
I've noticed that my Legacy version is not the latest and have downloaded the newer one, which presumably will be the one you used. I'll install that and de-install iexplore from wine-doors and see if that makes a difference.
Nope. Done that. I've assumed you didn't specify a particular browser, so I reset to default. On view web page, Wine Internet Explorer opens a blank window, and that's it. Same if I set to Wine's IE.
Allan
http://bugs.winehq.org/show_bug.cgi?id=11960
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|WORKSFORME |
--- Comment #9 from Lei Zhang thestig@google.com 2008-03-10 21:26:50 --- Let's reopen this for now until we get it ironed out.
(In reply to comment #8)
That's good!! No oleauto32 or vbasic?
Nope, I started with a fresh ~/.wine from scratch. Removed the old one and ran wineprefixcreate.
I've noticed that my Legacy version is not the latest and have downloaded the newer one, which presumably will be the one you used. I'll install that and de-install iexplore from wine-doors and see if that makes a difference.
If you read comment 7, I'm using Legacy 5 (final version), not Legacy 6.
Nope. Done that. I've assumed you didn't specify a particular browser, so I reset to default. On view web page, Wine Internet Explorer opens a blank window, and that's it. Same if I set to Wine's IE.
So before it was trying to open in Konqueror, and now it's opening in Wine's IE?
http://bugs.winehq.org/show_bug.cgi?id=11960
allan aganderson@ukonline.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #10 from allan aganderson@ukonline.co.uk 2008-03-11 19:09:41 --- (In reply to comment #9)
Let's reopen this for now until we get it ironed out.
(In reply to comment #8)
That's good!! No oleauto32 or vbasic?
Nope, I started with a fresh ~/.wine from scratch. Removed the old one and ran wineprefixcreate.
Hi Right, now I've done that (I won't bore you with what then happened as that is the subject of an earlier bug, revisited.) So, sticking to the point. Legacy can now launch a browser (it's own) to view the web pages. So, many thanks for that. Further coments below. continue...
I've noticed that my Legacy version is not the latest and have downloaded the newer one, which presumably will be the one you used. I'll install that and de-install iexplore from wine-doors and see if that makes a difference.
If you read comment 7, I'm using Legacy 5 (final version), not Legacy 6.
Yes, me too. That is, I'm now on the final version, not the earlier one I was on. (It made no difference.)
Nope. Done that. I've assumed you didn't specify a particular browser, so I reset to default. On view web page, Wine Internet Explorer opens a blank window, and that's it. Same if I set to Wine's IE.
So before it was trying to open in Konqueror, and now it's opening in Wine's IE?
It would launch whichever browser I set in Options/launch, either Firefox or Konqueror in Linux, Internet Explorer from wine-doors, or wine's own, but none showed any content. After removing .wine etc., I didn't specify any browser and it launches wine's with proper content.
Fixed, I'd say and thanks again.
Allan ,
http://bugs.winehq.org/show_bug.cgi?id=11960
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID
--- Comment #11 from James Hawkins truiken@gmail.com 2008-03-11 19:21:30 --- Nope, it's invalid.
http://bugs.winehq.org/show_bug.cgi?id=11960
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from James Hawkins truiken@gmail.com 2008-03-11 19:21:39 --- Closing.