Every time I try to open a chm file with chmsee, I get the following error message: Error: Platform version '11.0' is not compatible with minVersion >= 9.0 maxVersion <= 10.* chmsee was updated to be compatible with latest firefox release: 2012-04-03: Tag v1.99.09 and support xulrunner 11.0. Would it be possible to have a compatible chmsee binary? Many thanks for your help, Pablo
Update to latest snapshot.
chmsee-1.99-0.12.9.git36b4702.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/chmsee-1.99-0.12.9.git36b4702.fc16
chmsee-1.99-0.12.9.git36b4702.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/chmsee-1.99-0.12.9.git36b4702.fc15
chmsee-1.99-0.12.9.git36b4702.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/chmsee-1.99-0.12.9.git36b4702.fc17
chmsee-1.99-0.14.9.git36b4702.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/chmsee-1.99-0.14.9.git36b4702.fc15
chmsee-1.99-0.14.9.git36b4702.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/chmsee-1.99-0.14.9.git36b4702.fc16
chmsee-1.99-0.14.9.git36b4702.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/chmsee-1.99-0.14.9.git36b4702.fc17
I'm afraid that with Firefox-12 the problem arises again (reopening again). Reported upstream and fixed there. So we need a newer update. Many thanks for your help, Pablo
Please test the one above (build for 12)
Works fine now. Many thanks for your help, Pablo
chmsee-1.99-0.14.9.git36b4702.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
chmsee-1.99-0.14.9.git36b4702.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
chmsee-1.99-0.14.9.git36b4702.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.