The program crashes when I try to open CHM file

[Laotse]

Binary package hint: xchm

Hello, when I try to open CHM file which I can open in Windows without problem then XCHM crashes. I can't open this file in XCHM :-S

I hope that this post can help you to fix this problem.

[ville palo (vi64pa)]

Is it possible you to attach that .chm file to this report?

[Laotse (eliseo03)]

I'm sorry but I can't attach it because is "Mosby Medical Dictionary" (the spanish version: Diccionario Médico Mosby) and have copyright. :-(

[ville palo (vi64pa)]

Well, somebody will have a hard time fixing this =)

[Siep Kroonenberg (siepo)]

It also crashes when you simply try to start the program:

 xchm
The program 'xchm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 171 error_code 11 request_code 145 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

so this may be easy to reproduce. As a workaround, I installed kchmviewer-nokde.

[Ralph Janke (txwikinger)]

Thanks for reporting this problem and helping to make Ubuntu better.

I could not reproduce this problem on hardy and KDE. Could you please re-test this on hardy, and also test if on the same workstation/installation this problem only occurs on Gnome, or on both Gnome and KDE.

Thanks.

[Ralph Janke (txwikinger)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!