Specifying file to open on command line, causes this as well as completely blank/default screen instead of the chm: $ chmsee bin/FontValidatorHelp.chm JavaScript strict warning: resource://gre/modules/TelemetryEnvironment.jsm, line 489: ReferenceError: reference to undefined property this._environment._currentEnvironment.addons JavaScript error: chrome://chmsee/content/utils.js, line 119: SyntaxError: missing ; before statement JavaScript error: chrome://global/content/bindings/findbar.xml, line 343: NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getIntPref] JavaScript error: chrome://chmsee/content/main.xul, line 1: TypeError: onWindowLoad is not a function Trying to open chm from chmsee's own file->open menu causes this: JavaScript error: chrome://chmsee/content/main.xul, line 1: TypeError: openFile is not a function xchm can open the chm fine. $ rpm -q xulrunner xulrunner-44.0-1.fc23.x86_64 See discussion below. This is very unfortunate, as mono default to use chmsee as viewer... I'll possibly go and file at ximian's mono bugzilla also, to ask them to change the default. +++ This bug was initially created as a clone of Bug #1238845 +++ Description of problem: chmsee some.chm (process:23006): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Error: Platform version '37.0.2' is not compatible with minVersion >= 22.0 maxVersion <= 33.* Version-Release number of selected component (if applicable): xulrunner-37.0.2-2.fc22.x86_64 chmsee-2.0.2-17.gitd40ff7da.fc22.x86_64 How reproducible: always Steps to Reproduce: 1. just run chmsee on any chm 2. 3. Actual results: Error Expected results: No error, view chm Additional info: Upgrading to chmsee-2.0.2-18.gitd40ff7da.fc22.x86_64 http://koji.fedoraproject.org/koji/buildinfo?buildID=630726 fixes this. It is also apparent in the log: * Fri Apr 24 2015 Yijun Yuan <bbbush.yuan> - 2.0.2-18.gitd40ff7da - rebuild for xulrunner 37 But for some reason this has not been pushed to update yet. --- Additional comment from Hin-Tak Leung on 2015-08-15 19:00:13 EDT --- got broken again! $ rpm -q xulrunner xulrunner-38.0-1.fc22.x86_64 $ chmsee (process:26564): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Error: Platform version '38.0' is not compatible with minVersion >= 22.0 maxVersion <= 37.* $ rpm -q chmsee chmsee-2.0.2-18.gitd40ff7da.fc22.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=1228358#c1 suggests changing /usr/lib/chmsee/application.ini to * from 37.* --- Additional comment from Fedora Update System on 2015-08-16 00:54:54 EDT --- chmsee-2.0.2-21.gitd40ff7da.fc23 has been submitted as an update for Fedora 23. https://admin.fedoraproject.org/updates/chmsee-2.0.2-21.gitd40ff7da.fc23 --- Additional comment from Fedora Update System on 2015-08-16 00:55:01 EDT --- chmsee-2.0.2-19.gitd40ff7da.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/chmsee-2.0.2-19.gitd40ff7da.fc22 --- Additional comment from Fedora Update System on 2015-08-16 00:55:10 EDT --- chmsee-2.0.2-19.gitd40ff7da.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/chmsee-2.0.2-19.gitd40ff7da.fc21 --- Additional comment from Fedora Update System on 2015-08-18 01:13:20 EDT --- Package chmsee-2.0.2-21.gitd40ff7da.fc23: * should fix your issue, * was pushed to the Fedora 23 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing chmsee-2.0.2-21.gitd40ff7da.fc23' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-13536/chmsee-2.0.2-21.gitd40ff7da.fc23 then log in and leave karma (feedback). --- Additional comment from Fedora Update System on 2015-08-19 04:12:12 EDT --- chmsee-2.0.2-19.gitd40ff7da.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. --- Additional comment from Fedora Update System on 2015-08-26 00:33:46 EDT --- chmsee-2.0.2-21.gitd40ff7da.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. --- Additional comment from Fedora Update System on 2015-08-26 12:49:37 EDT --- chmsee-2.0.2-19.gitd40ff7da.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. --- Additional comment from Hin-Tak Leung on 2015-10-26 00:39:30 EDT --- Is broken again!!!! $ rpm -q chmsee chmsee-2.0.2-21.gitd40ff7da.fc23.x86_64 $ rpm -q xulrunner xulrunner-40.0-1.fc23.x86_64 in /usr/lib64/chmsee/application.ini: [Gecko] MinVersion=22.0 MaxVersion=39.* --- Additional comment from Hin-Tak Leung on 2015-10-26 00:41:45 EDT --- Could we change that MaxVersion=x.* to * permanently to stop it breaking again? --- Additional comment from LiZhenbo on 2015-12-02 22:18:00 EST --- (In reply to Hin-Tak Leung from comment #10) > Could we change that MaxVersion=x.* to * permanently to stop it breaking > again? What if the API of Gecko really changed, and caused other bugs? Seems that chmsee needs to be rebuilt very frequently --- Additional comment from Yijun Yuan on 2016-02-13 23:12:38 EST --- Sorry I cannot keep up with this anymore. --- Additional comment from Yijun Yuan on 2016-02-13 23:19:51 EST --- --- Additional comment from Hin-Tak Leung on 2016-04-10 18:30:13 EDT --- Yes, it has completely broken due to API change as of now: $ rpm -q xulrunner xulrunner-44.0-1.fc23.x86_64 The 39->40 was okay, but I have not noticed since 40. Recently found that it is completely broken. Unfortunately mono uses it by default to emulate .net's chm viewing... I'll file a separate bug about it being completely broken.
Forgot to put this down: $ rpm -q chmsee chmsee-2.0.2-21.gitd40ff7da.fc23.x86_64
The hard-coded default to use chmsee is at line 94 of https://github.com/mono/mono/blob/master/mcs/class/System.Windows.Forms/System.Windows.Forms/Help.cs
Argh, sorry... the ximian novell bugzilla integration no longer works. I meant xamarin, and filed: https://bugzilla.xamarin.com/show_bug.cgi?id=40266
Somebody should file a bug for redhat's bugzilla itself for the obsolete ximian novell bugzilla external bug tracker entry...
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.