Hey guys!
I'm sorry, for being so stupid, but after Wolfi was to kind to help me out with my Debian problem, I had with Inkscape and that libgc1c2, I face the next problem -- again. I compiled the (almost) latest SVN and still don't have any icons. This problem was not solved in for me in the mean time, I just couldn't try to solve it anymore, because of the other problem...
What I get is:
** (inkscape:29395): CRITICAL **: Inkscape::XML::Document* sp_repr_read_file(con st gchar*, const gchar*): assertion `Inkscape::IO::file_test( filename, G_FILE_T EST_EXISTS )' failed
** (inkscape:29395): WARNING **: Unable to read keys file ${datarootdir}/inkscap e/keys/default.xml
** (inkscape:29395): WARNING **: failed to load icon 'file_import'
...
All the other icons to come after that.
I guess it's easy to fix, but how?
Thanks!
David
On Jun 10, 2006, at 2:46 PM, David Christian Berg wrote:
What I get is:
** (inkscape:29395): CRITICAL **: Inkscape::XML::Document* sp_repr_read_file(con st gchar*, const gchar*): assertion `Inkscape::IO::file_test( filename, G_FILE_T EST_EXISTS )' failed
** (inkscape:29395): WARNING **: Unable to read keys file ${datarootdir}/inkscap e/keys/default.xml
** (inkscape:29395): WARNING **: failed to load icon 'file_import'
...
All the other icons to come after that.
I guess it's easy to fix, but how?
The first thing would be to run in gdb with inkscape fed the --g- fatal-warnings option. That should get it to stop at that first critical warning, and let you see what the filename it's trying to open is.
Hi altogether!
On Sat, Jun 10, 2006 at 04:36:59PM -0700, Jon A. Cruz wrote:
On Jun 10, 2006, at 2:46 PM, David Christian Berg wrote:
What I get is:
** (inkscape:29395): CRITICAL **: Inkscape::XML::Document* sp_repr_read_file(con st gchar*, const gchar*): assertion `Inkscape::IO::file_test( filename, G_FILE_T EST_EXISTS )' failed
** (inkscape:29395): WARNING **: Unable to read keys file ${datarootdir}/inkscap e/keys/default.xml
** (inkscape:29395): WARNING **: failed to load icon 'file_import'
...
All the other icons to come after that.
I guess it's easy to fix, but how?
The first thing would be to run in gdb with inkscape fed the --g- fatal-warnings option. That should get it to stop at that first critical warning, and let you see what the filename it's trying to open is.
No need to. The problem here is that ${datarootdir} is not expanded by configure. I posted about this before. From some further investigation I guess it is the same problem as debian bug #368502 [1]. This is not really a bug however, but policy. It would be nice if someone could verify if this bug is really the reason for our experience, since I don't have knowlegde about the autotools. ATM this is not a very high priority to me as long as I can compile the tarballs for the debian package. I wanted to debug this after the release.
Thanks,
Wolfi
I solved the problem by copying the files from /usr/share/inkscape to my ~/.inkscape folder. The question would be: Why do I need to, it doesn't quite make sense to me. Well, I'm happy for now :)
David
On Sat, 2006-06-10 at 23:46 +0200, David Christian Berg wrote:
Hey guys!
I'm sorry, for being so stupid, but after Wolfi was to kind to help me out with my Debian problem, I had with Inkscape and that libgc1c2, I face the next problem -- again. I compiled the (almost) latest SVN and still don't have any icons. This problem was not solved in for me in the mean time, I just couldn't try to solve it anymore, because of the other problem...
What I get is:
** (inkscape:29395): CRITICAL **: Inkscape::XML::Document* sp_repr_read_file(con st gchar*, const gchar*): assertion `Inkscape::IO::file_test( filename, G_FILE_T EST_EXISTS )' failed
** (inkscape:29395): WARNING **: Unable to read keys file ${datarootdir}/inkscap e/keys/default.xml
** (inkscape:29395): WARNING **: failed to load icon 'file_import'
...
All the other icons to come after that.
I guess it's easy to fix, but how?
Thanks!
David
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Jun 11, 2006, at 3:01 AM, David Christian Berg wrote:
I solved the problem by copying the files from /usr/share/inkscape to my ~/.inkscape folder. The question would be: Why do I need to, it doesn't quite make sense to me.
I think the problem is that the compiled binary is looking in one shared location, while the installer is putting things in a different location. Breaking in the debugger should reveal what that former one is...
However, aside from the shared location, the compiled binary also looks in your individual location, thus can pick things up when they are copied over to there.
Well, I'm happy for now :)
Glad you're unstuck.
participants (3)
-
David Christian Berg -
Jon A. Cruz -
Wolfram Quester