Version: v1.0 (using 4.0.3 (KDE 4.0.3), Kubuntu packages) Compiler: gcc OS: Linux (i686) release 2.6.22-14-generic Using kig 1.0 on KDE 4.0.3 I am unable to either load or to save files. When I try to open a file, I get a "Format Not Supported" error: """ You tried to open a document of type "text/plain"; unfortunately, Kig does not support this format. If you think the format in question would be worth implementing support for, you can always ask us nicely on mailto:pino@kde.org or do the work yourself and send me a patch. """ The files can all be opened with Kig 0.10.7. When I try to save a file, I also get a "Format Not Supported" error: """ Kig does not support saving to any other file format than its own. Save to Kig's format instead? """ If I press "Save Kig Format" I get the file dialog back again, but the file is not saved. If I then click "Cancel" on that file dialog, the file is saved with the name I gave previously. I cannot open the file that is created in Kig 1.0, but if I go back to Kig 0.10.7 I am able to open the file.
I confirm this bug on for weeks with Hardy Heron on 64 bit machines ; difficult reallt to pursue testing in these conditions. No really linked to kig I confirme the following bug : when clicking on bug report of appropriate Kig menu Konqueror does not open ; but this is the case for all KDE 4.0.3 apps.
I cannot reproduce the problem, I can open files correctly here. From what I read, the issue might be related to the fact that the KDE4-specific mimetypes (including kig's one) do not seem to be used. Can you please paste the result of the follwing command: $ kde4-config --path xdgdata-mime
$ kde4-config --path xdgdata-mime /home/lee/.local/share/mime/:/usr/local/share/mime/:/usr/share/mime/ I don't see anything about kig in any of those locations. I also have a .kde4/share/mimelnk/ directory, but no mention of kig types in there either.
Just like I don't see anything kde4-specific there. It should have something like: $prefix/share/mime, where $prefix is the result of `kde4-config --prefix`. As additional check, could you please paste the output of `env | grep XDG`?
$ kde4-config --prefix /usr/lib/kde4 I have a file /usr/lib/kde4/share/mime/packages/kde.xml which does have kig related entries. $ env | grep XDG XDG_SESSION_COOKIE=[...] XDG_DATA_DIRS=/usr/local/share/:/usr/share/:/usr/share/gdm/ Am I supposed to set the xdgdata-mime or XDG_DATA_DIRS manually? Is this a bug in the KDE installation process or is it just a bug in the KDE 4 packages I installed?
> I have a file /usr/lib/kde4/share/mime/packages/kde.xml > which does have kig related entries. Not even: <mime-type type="application/x-kig"> <comment>Kig figure</comment> <glob pattern="*.kig"/> <glob pattern="*.kigz"/> </mime-type> ? if it does not, then it's a kubuntu problem, as that mimetype is there since months, way before any KDE 4 release. > $ env | grep XDG > XDG_DATA_DIRS=/usr/local/share/:/usr/share/:/usr/share/gdm/ This is exactly the problem. You (or something else) is explicitely setting that variable, so its value is taken as is (per specs). So, unless there is a sort of wrapper script or whatever that manually sets (or unsets) it, this looks like a kubuntu issue. As further test you can do the following, in a terminal: $ XDG_DATA_DIRS=$(kde4-config --prefix)/share:$XDG_DATA_DIRS $ export XDG_DATA_DIRS $ kbuildsycoca4 --noincremental here, verify that at the end of its output there's something like: kbuildsycoca4(23962) KMimeFileParser::parseGlobs: Now parsing "/usr/lib/kde4/share/mime/globs" $ kig [or kig-kde4, no idea how kubuntu called it] If kig started from this procedure works, then it's indeed a distro issue.
I do confirm this problem, in Kubuntu packages (I expect it's a distro issue although I'm not sure what). /usr/lib/kde4/share/mime/packages/kde.xml does contain application/x-kig kbuildsycoca4 does not say that it parses /usr/lib/kde4/share/mime/globs with XDG_DATA_DIRS unset or with it set.
I'm running KDE4 under Gnome, as part of Edubuntu. I completely confirm all af the above observed behaviour: unable to save or open, Konqueror not launching. Unfortunaltely "kde4-config" returns with "bash:command not found" so I couldn't test if the proposed workaround produced any results.
I have the same problem, using Ubuntu Hardy Heron (8.04 - updated). This page helped me to notice a few things : * /usr/lib/kde4/bin is not in the (default) PATH, which makes some binaries (as kig, kde4-config or kbuildsycoca4) difficult to find unless absolute path is given ; * once this solved, the problem persists even when using the method given by Pino in comment #6 - `kbuildsycoca4 --noincremental` lists a lot of lines with "... is not compliant with XDG standard (missing trailing semicolon).", but none containing "... Now parsing "/usr/lib/kde4/share/mime/globs" " !.. I'll try a few things (setting PATH and XDG_DATA_DIRS correctly and restarting a session or the computer, or modifying ~/.local/share/mime/globs to get the correct entry) and let you know how that works...
Well, I now have solved my problem, but I needed a turnaround : * PATH and XDG_DATA_DIRS are now set correctly, adding these few lines in /etc/bash.bashrc : if [[ $PATH != *"/usr/lib/kde4/bin"* ]]; then PATH=$PATH:/usr/lib/kde4/bin fi KDE4PREFIX=$(kde4-config --prefix) if [[ $XDG_DATA_DIRS != *"$KDE4PREFIX"* ]]; then XDG_DATA_DIRS=$KDE4PREFIX:$XDG_DATA_DIRS fi However, if the change of PATH allows to use kde4 binaires, the other change does not seem o have any effect : `kde4-config --path xdgdata-mime` does not give a correct value ("~/.local/share/mime/:/usr/local/share/mime/:/usr/share/mime/", which does not contain "/usr/lib/kde4/mime/")... As a consequence, `kbuildsycoca4 --noincremental` still does not work... * My turnaround is the following : I added a symbolic link from "/usr/local/share/mime/packages/kde.xml" to "/usr/lib/kde4/mime/packages/kde.xml" (`cd /usr/local/share/mime/packages ; sudo ln -s /usr/lib/kde4/mime/packages/kde.xml .`), updated the mime database (`sudo update-mime-database /usr/local/share/mime/`) and it works!.. If anybody knows how to solve correctly the problem, please write it here! Thanks in advance.
I no longer see this problem using Kig 1.0 under KDE 4.5