Actually the problem is that that kio_chm is broken. But the worst thing is it breaks kchmviewer users. Please read the first entry in kchmviewer FAQ (http://www.kchmviewer.net/faq.html): =============================================================================== Q: The book shows without any problem using QTextWidget browser, but when I use KHTMLPart browser, I get the following error: An error occurred while loading ms-its:/home/user/Symphony FrameWork.chm::/index.html The file or folder ms-its:/home/user/Symphony FrameWork.chm::/index.html does not exist. A: You have kio_chm installed, and because it installs itself as KIO slave for ms-its, sometime KDE uses it instead of kio_msits. To disable it, find the file chm.protocol in your KDE directory, and remove it. Then run kdeinit to reread the configuration. =============================================================================== I've encountered this issue and found that if I install kio_chm which is part of kdevelop-3.5.4 kchmveiwer does not works exactly like said in FAQ. I've investigated this issue a bit and found that /usr/lib/kde3/kio_chm.so crashes with the following bactrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb6c0f700 (LWP 12159)] 0xb7d57dc6 in KMimeMagic::findBufferType (this=0x8476200, array=@0xbfa773f4) at /usr/include/bits/string3.h:52 52 return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); (gdb) bt #0 0xb7d57dc6 in KMimeMagic::findBufferType (this=0x8476200, array=@0xbfa773f4) at /usr/include/bits/string3.h:52 #1 0xb7d57eca in KMimeMagic::findBufferFileType (this=0x8476200, data=@0xbfa773f4, fn=@0xbfa7753c) at kmimemagic.cpp:2285 #2 0xb731a55d in ChmProtocol::get (this=0xbfa777a8, url=@0xbfa775cc) at chm.cpp:288 #3 0xb7d62f75 in KIO::SlaveBase::dispatch (this=0xbfa777a8, command=67, data=@0xbfa77748) at slavebase.cpp:1046 #4 0xb7d6331b in KIO::SlaveBase::dispatchLoop (this=0xbfa777a8) at slavebase.cpp:301 #5 0xb731b442 in kdemain (argc=4, argv=0x841d790) at chm.cpp:54 #6 0x0804dd5f in launch (argc=4, _name=0x8411f94 "kio_chm", args=<value optimized out>, cwd=0x0, envc=0, envs=0x8412028 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8051e36 "0") at kinit.cpp:673 #7 0x0804ee3d in handle_launcher_request (sock=9) at kinit.cpp:1240 #8 0x0804f576 in handle_requests (waitForPid=0) at kinit.cpp:1443 #9 0x0804fdcb in main (argc=-1079542252, argv=0xbfa77e2c, envp=0x0) at kinit.cpp:1908 I think it's good idea to remove kio_chm protocol handler from kdevelop installation but kde team it's your shot what to do with this kio_chm.
Hi, so far how i understand it, remove the protocol from the kdevelop and add dependency on the kchm or how is that package of yours named so the feature wont me misssing. But it is DIY cause i dunno who is using kdevelop for kde3 among us :(
Well I'm not sure what to do here. Ubuntu has similar bug undecided: https://bugs.launchpad.net/ubuntu/+source/kchmviewer/+bug/252159 At the same time I found some reports that it's possible to use konqueror to read chm files, and although not without problems I've managed to read them too. Currently I've added notice to kchmviewer and I can't think of better solutions at the moment. I hope that kde/kchmviewer upstreams resolve this issue somehow in kde4. ewarn "kchmviewer and kdevelop's kio_chm don't work together, bug #260134." ewarn "Until we find better solution, if you want to read chm files with ${PN}" ewarn "you need to remove ${ROOT}usr/share/services/chm.protocol file manually."
Sorry but WONTFIX, pva's ewarn is enough and i don't want kdevelop to depend on kchmviewer
